-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
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. |
Commands to create brand new SSM parameter in (in this example, it is in UAT)
Commands to overwrite existing SSM Parameters (we will need to know this when the keys expire)
|
WIP Update - Currently working on this issue.
Edit: Update: This has been resolved. Detail can be reviewed here. |
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.
The text was updated successfully, but these errors were encountered: