- Newest
- Most votes
- Most comments
Hi iBehr,
Thank you for responding. Is there a way to do that under the free tier?
I realized that the ec2 instance shuts down after some time because that is the way I'd originally configured Cloud9 - if there was no activity in the environment after a half hour, it would shut down. So that makes sense.
But I still don't understand why I can't get into the Cloud9 environment anymore.
Would it be worth the effort to delete the ec2 container? Would that allow me to then create a new Cloud9 environment?
Funny thing - I'm experiencing this issue as a root user. When I log in as an IAM user with appropriate privileges, I'm able to create a new Cloud9 environment with no issue.
Using root is not recommended. I would proceed with using the environment as an IAM User.
See here: https://docs.aws.amazon.com/cloud9/latest/user-guide/share-environment.html#share-environment-best-practicesDon't use your AWS account root user to create and share environments. Use IAM users in the account instead. For more information, see First-Time Access Only: Your Root User Credentials and IAM users in the IAM User Guide.
Hi
Is it a new AWS account? Since yesterday, some new AWS accounts have been unable to access the Cloud9 console with the same error. Existing AWS accounts can access without problems.
Relatively new. I created it in May.
I'm getting the exact same error when trying to run the EKS workshop.
This account has existed for many years but just reviving it for some hacking.
I'm able to connect to it now. I guess there was an issue on AWS' end.
It’s not an error, it’s policy. See
Relevant content
- asked a year ago
- asked 3 years ago
Using root is not recommended. I would proceed with using the environment as an IAM User.
See here: https://docs.aws.amazon.com/cloud9/latest/user-guide/share-environment.html#share-environment-best-practices