As Cloud9 is being deprecated, we suggest you use this instruction to set your environment up instead.
If you still wish to use Cloud9, you can go back.
Download the tagging-workload.yaml CloudFormation template to your local machine.
Navigate to the CloudFormation console and choose Create Stack > With new resources (standard).
For Prepare template select Template is ready, and select Upload a template file under Template source.
Choose Choose File to select the template file that you want to upload. Choose the CloudFormation template that you downloaded at the beginning of this section and choose Next.
Enter tagging-workload
for the Stack name.
Choose Next till you get to the Review page and choose Submit. Wait for the stack creation to reach CREATE_COMPLETE once completed move on to the workshop labs.
Repeat steps 1-6 with the VSCode Server stack code-server-stack.yaml. Enter vscodeserver
for the Stack name.
Navigate to the CloudFormation console.
Choose the VSCode IDE Server stack and then choose the Outputs tab.
The Output key will be VSCodeServerCloudFrontDomainName
Open the URL Value in a new browser tab, this will open up the VSCode Server environment to be used in the following labs.
You will now see the created VSCode Server environment in a new tab.
For the AWS Config labs you will need a configuration recorder enabled in your account. If AWS Config is setup in your account already, you can move onto the labs. If AWS Config is not setup in your account already, complete the following instructions, or, skip the config labs if you do not wish to enable AWS Config in your own account.
mkdir ~/environment
cd ~/environment
mkdir config
cd config
curl 'https://static.us-east-1.prod.workshops.aws/public/bc005028-76d7-42ac-9cb2-fed686ce81e0/static/templates/config.yaml' --output config.yaml
aws cloudformation create-stack --stack-name config-deployment --template-body file://config.yaml --capabilities CAPABILITY_NAMED_IAM
At the end of the CloudFormation role out, you should see the configuration recorder is now enabled.
Navigate to the AWS Config console.
Choose Settings in the navigation pane.
Under Recorder view that Recording is on.