Create project-specific AWS account

[tschaffter]

From @zaro0508 on May 27:

Dear AWS Sandbox account users:

As part of our effort to improve accounting and stability, Sage IT is deprecating the shared AWS Sandbox account in favor of other options such as individual sandbox accounts, team accounts and project accounts. Our plan is to disable all Sandbox account access on July 4th 2022. Please review the cloud computing decision tree to find the best option for your situation and contact IT if you require a new account. We recommend that all users migrate their content from Sandbox to your chosen option before the above date. We hope that by collaborating early we can avoid any interruption to your work as Sandbox is taken away. If you have further questions you can contact us via email or in the slack #sageit channel. Thank you.

Tasks

• [x] Read Computing with Amazon Web Services
• [x] Read Bootstrapping AWS Project Accounts
• [x] Review list of existing AWS accounts
• [x] Identify the AWS account to use to deploy the dev, staging and production instance of the challenge stack (challenge registry, challenge platform)
• [x] #274

[tschaffter]

Computing with Amazon Web Services

1. Is the need a basic AWS resource? No
2. Is the work for a specific, funded project? Yes, the challenge ecosystem is funded by the ITCR-DREAM grant and INDIRECT.
3. Can the stack be scripted and is AWS console access not required? No, access to the AWS console is required during the development of the challenge ecosystem.

Decision: We need a project-specific account according to the decision tree.

Request to create an AWS account is tracked in the Jira ticket IT-1702.

Tagging @chepyle, @jaeddy, @thomasyu888

[tschaffter]

Update

• I can login to the account as an Admin to the Cnb account

[tschaffter]

we now have the AWS account CnbAccount. For now there is no need to create another account to deploy the Challenge Registry stack.