AWS Cloud9 | AWS Cloud9 Associated Resources Flashcards
Where does AWS Cloud9 store my code?
AWS Cloud9 Associated Resources
AWS Cloud9 | Developer Tools
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.
What are the resources created by AWS Cloud9 for Amazon EC2 environments?
AWS Cloud9 Associated Resources
AWS Cloud9 | Developer Tools
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.
Does AWS Cloud9 manage resources created in AWS Cloud9 for Amazon EC2 environments?
AWS Cloud9 Associated Resources
AWS Cloud9 | Developer Tools
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.
Are my Amazon EC2 instances in AWS Cloud9 environments always running?
AWS Cloud9 Associated Resources
AWS Cloud9 | Developer Tools
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”.
