This document addresses special considerations for creating AWS Cloud9 development environments in your team development AWS accounts. As long as a pre-requisite has been addressed by your Cloud Administration team, you as a builder can self-service create AWS Cloud9 environments in your team development AWS account.
If you do not see the AWS IAM role
AWSCloud9SSMAccessRole in your team development AWS account, then your Cloud Administration team has not yet established this IAM role in your environment. Contact the team and ask them to follow the instructions to Establish IAM Service Role for AWS Cloud9.
Management consoleassociated with the team development role.
||Select the instance type that will suit your needs.|
||If you would like to use an Amazon Linux platform, it’s recommended that you select
||The shared development VPC should be pre-selected. You can select any of the shared development private subnets.|
In your Cloud9 environment, the EC2 instance has an EC2 instance profile and IAM service role
AWSCloud9SSMAccessRole associated with it. Since the IAM service role is fixed, you as a builder do not have access to change it. Consequently, your Cloud9 environment might be constrained by the actions in can perform in your team development AWS account.
See the AWS Cloud9 User Guide for information on using Cloud9.
If you find that your bash terminal prompt is too long, you can set it to just the Linux user, IP address, and current directory. Either edit your
~/.bashrc file and replace the
PS1 setting or export the setting as follows:
export PS1="[\u@\h \W]\$ "
Although a version of the AWS CLI is preinstalled in your Cloud9 environment, you should consider installing version 2 of the AWS CLI. See Install the AWS CLI.