Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup Cumulus deploy configuration that includes ORCA #214

Closed
10 tasks done
krisstanton opened this issue Jul 14, 2023 · 4 comments
Closed
10 tasks done

Setup Cumulus deploy configuration that includes ORCA #214

krisstanton opened this issue Jul 14, 2023 · 4 comments
Assignees

Comments

@krisstanton
Copy link
Collaborator

krisstanton commented Jul 14, 2023

Setup Cumulus deploy configuration that includes ORCA

Note: Many of the Code Commits have been attached to ticket #213 due to the naming of the branch.

@krisstanton krisstanton changed the title Setup Cumulus deploy configuration that includes ORCA in UAT - CBA Setup Cumulus deploy configuration that includes ORCA Jul 14, 2023
@krisstanton
Copy link
Collaborator Author

A couple of details that are worth mentioning discovered during this configuration:

(1) The documentation says to create bucket policies so there can be cross account access. The documentation says to actually create and submit a ticket for these policies to be implemented. It turns out that we actually have enough permissions to make those policies ourselves.

(2) The documentation also says there are 2 required variables for accessing the buckets using keys. A better way to implement this is to use roles. Roles are currently not supported for ORCA, so we must use the keys. Also note, creating access keys also means the bucket access policies may not even be necessary.

In a future version, as soon as we can switch to Roles (or assumed roles), we should do so.

@krisstanton
Copy link
Collaborator Author

Commands to create brand new SSM parameter in (in this example, it is in UAT)

DOTENV=.env.cba.uat make bash
aws ssm put-parameter --type SecureString --name "/shared/cumulus/orca/dr/s3-access-key" --value "VALUE"
aws ssm put-parameter --type SecureString --name "/shared/cumulus/orca/dr/s3-secret-key" --value "VALUE"

Commands to overwrite existing SSM Parameters (we will need to know this when the keys expire)

DOTENV=.env.cba.uat make bash
aws ssm put-parameter --name "/shared/cumulus/orca/dr/s3-access-key" --overwrite --value "VALUE"
aws ssm put-parameter --name "/shared/cumulus/orca/dr/s3-secret-key" --overwrite --value "VALUE"

@krisstanton
Copy link
Collaborator Author

Note: Many of the Code Commits have been attached to ticket #213 due to the name of the branch.
#213

@krisstanton
Copy link
Collaborator Author

krisstanton commented Oct 10, 2023

WIP Update - Currently working on this issue.

Error: error putting S3 Bucket Inventory Configuration: AccessDenied: Access Denied
        status code: 403, request id: B67TJ7CCQC641FNQ, host id: jkGXmObxlMPev3r/HuQ3V2fLfgRkoU/3n1Xr3KzfS6Awhp2bMj6gedgrCgPeRQMzjGhwxKWmkeY=

  on .terraform/modules/orca/modules/lambdas_secondary/main.tf line 62, in resource "aws_s3_bucket_inventory" "inventory-report":

Edit: Update: This has been resolved. Detail can be reviewed here.
#248 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants