AWS Cloud9 FAQs

You can sign in to the AWS Management Console, and select AWS Cloud9. The console will guide you through the options to select the Linux server that you want to connect with Cloud9. You can either launch a new Amazon EC2 instance (AWS Cloud9 EC2 environment) or connect your existing Linux server (AWS Cloud9 SSH environment) in a few simple steps. Once you’ve created a Cloud9 environment, you can access your IDE and write code in a fully configured development environment. For more information, see our documentation about setting up AWS Cloud9 and then complete a basic tutorial.

An AWS Cloud9 development environment is where the project code files are stored and the tools used to develop the application are run. Each environment has unique IDE settings stored with it. This enables you to easily create and switch between many different development environments, each one customized with the tools, runtimes, files, and IDE settings required for a specific project.

There are two types of AWS Cloud9 environments that you can use.

• AWS Cloud9 EC2 environment – Enables you to launch a new Amazon EC2 instance that Cloud9 connects to. By default, these instances stop 30 minutes after you close the IDE and start automatically when you open the IDE.
• AWS Cloud9 SSH environment – Enables you to connect an existing Linux server with Cloud9. There are certain dependencies that are required on the Linux server that you want to use with Cloud9 SSH environments. Please visit our documentation for more details.

Yes. You can use SSH environments to connect an existing Linux-based EC2 or Lightsail instance with AWS Cloud9.

The AWS Cloud9 IDE has an advanced code editor with features such as auto-completion, code folding, hinting, syntax highlighting, and line manipulation. The code editor enables you to choose from over 30 color schemes that control syntax highlighting and the UI. You can also fully customize the Cloud9 UI by editing your stylesheet.

AWS Cloud9 EC2 environments come preinstalled with commonly used development tools such as Git and Docker. They also include language runtimes and package managers for many popular programming languages such as Node.js and Python. To view the full list of tools and packages preinstalled on Cloud9 EC2 environments, please visit our documentation.

The AWS Cloud9 IDE has a run button in the toolbar and built-in runners for over 10 different languages that will automatically start your application with the latest code changes. For full control over how you run your software, you can also customize existing runners, create your own runners, or run your code from the terminal.

The AWS Cloud9 IDE has a built-in terminal window that can interactively run CLI commands. You also have full administrative privileges on the instance (sudo rights), allowing you to install any additional tools required for development or to host your application.

You can open the terminal window within the IDE and access your source control system using the same command line tools that you would use on your local machine. AWS Cloud9 EC2 environments come preinstalled with Git to enable easy access to your source code.

See Regional Products and Services for details.

Any data that you store in your AWS Cloud9 environment such as code files, packages, or dependencies is always stored in your resources. If you use an EC2 environment, your data is stored in the associated Amazon Elastic Block Store (EBS) volume that exists in your AWS account. If you use an SSH environment, your data is stored in local storage on your Linux server.

When you create an Amazon EC2 environment, AWS Cloud9 creates the required compute and storage resources in your AWS account. These resources include an Amazon EC2 instance, an 8-GB Amazon Elastic Block Store (EBS) volume, an Amazon EC2 security group, and an AWS CloudFormation stack. You have access to these resources through the individual AWS service consoles. When you delete your environment, Cloud9 automatically deletes these resources for you.

In addition to creating and deleting your AWS Cloud9 EC2 environment resources on your behalf, Cloud9 can also automatically start and stop the EC2 instances to reduce your costs. You are responsible for all other administrative tasks on these resources, such as installing software patches on your EC2 instances and performing backup of your EBS volumes.

No. AWS Cloud9 provides a default auto-hibernation setting of 30 minutes for your Amazon EC2 instances created through Cloud9. With this setting, your EC2 instances automatically stop 30 minutes after you close the IDE and restart only when you reopen the IDE. As a result, you typically only incur EC2 instance charges for when you are actively working. When your instance requires a restart, you lose any active terminal sessions in the IDE and can experience some wait time while opening your IDE. Depending on your use case, you can configure the auto-hibernation setting and even elect to keep your EC2 instance “always on”.

Yes. You can change the Amazon EC2 instance type that you initially selected with your AWS Cloud9 environment. To do this, you navigate to the instance in the EC2 console, locate your instance, and follow the instructions in Amazon EC2 documentation.

You can share your AWS Cloud9 environment by clicking the Share button in the top right of your IDE. You are prompted for the AWS Identity and Access Management (IAM) user name and the desired access levels for the person you want to collaborate with. Once you enter these details, the environment is available to both the participants for real-time collaboration on IDE features and command line sessions.

No. AWS Cloud9 environments can currently be shared only with the IAM users within the same AWS account. If you want to invite a new user that doesn’t have an IAM user access, you can follow the link to create a new IAM user in the Share dialog box.

AWS Cloud9 EC2 environments come preinstalled with the AWS CLI, which is authenticated with the permissions of the logged-in AWS user automatically. This enables you to run interactive CLI commands against AWS services from the built-in terminal window in Cloud9 without any additional configuration.

You can access the built-in tools for AWS Lambda from the AWS Resources panel in the IDE. You can use these tools to import existing or create new Lambda functions in Node.js and Python. You can easily run, preview, debug, and deploy these functions directly from the IDE. AWS Cloud9 also provides support for the AWS Serverless Application Model (AWS SAM) framework. This enables you to easily manage multiple Lambda functions and serverless resources in your application. If you provisioned your project using AWS CodeStar, any changes committed to the application will be built and deployed directly to Lambda on git push.

Yes. AWS Cloud9 can simulate the AWS Lambda execution environment for Node.js and Python to run your functions locally in the IDE. This enables you to test your serverless applications with step-through debugging without uploading your application changes to Lambda. Once tested, you can also deploy your application changes to Lambda directly from the IDE.

You can launch AWS Cloud9 environments directly from AWS CodeStar and immediately start editing and committing your CodeStar project code in the Cloud9 IDE. Any code changes that you commit to your project source repository from Cloud9 are automatically built and deployed using the tools provisioned by CodeStar. To learn more about using this integration, please visit the AWS CodeStar documentation.