Make sure there are no Service Control Policies blocking the account from using CloudShell. The policy simulator may help narrow down what is blocking if it is a permissions issue. https://policysim.aws.amazon.com/
Policy simulator shows I should have access to CloudShell but I don't have.
The two regions you mentioned are supported refer to AWS CloudShell endpoints and quotas. If this was a permission error I would expect to see a different error. To be sure check that your current permissions includes necessary permissions, for example, AWSCloudShellFullAccess.
This could be browser related. CloudShell supports below so check that your browser meets these requirements
- Google Chrome
- Latest three major versions
- Mozilla Firefox
- Latest three major versions
- Microsoft Edge
- Latest three major versions
- Apple Safari for macOS
- Latest two major versions
So i was able to resolve this issue with the help of AWS repost user @Maulik_Makadiya. Few things to try to create CloudShell environment:
-
Time Synchronization: Make sure Your machine time is accurate. It means its correct based on world time. did you try from another machine to see if its working there? may be any time sync related issue?
-
Check in different regions..
-
check AWSCloudShellFullAccess policy to ensure it has below JSON data.
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"cloudshell:*"
],
"Effect": "Allow",
"Resource": "*"
}
]
}
-
Check in different browser to see if it works in different browser or not. https://docs.aws.amazon.com/cloudshell/latest/userguide/troubleshooting.html
-
Did you deleted cloudshell home directory or something? Try after resetting home directory. But it can DELETE all your data exists in home directory. https://docs.aws.amazon.com/cloudshell/latest/userguide/vm-specs.html#deleting-home-directory
-
check if any DENY policy created for it. remove that.
-
It is possible your account is not 100% verified. Try this: Create a CloudFront distribution if you get the below error it confirms your account is unverified or if you can create 2 distributions and can't create the 3rd one.
Your account must be verified before you can add new CloudFront resources. To verify your account, please contact AWS Support (https://console.aws.amazon.com/support/home#/ ) and include this error message.
Click the support link
- Navigate to:
Support / New case / Service limit increase
- Limit type:
CloudFront Distributions
- In Requests select:
Limit: Web Distributions per Account New limit value: <TYPE_YOUR_NEW_VALUE_HERE>
MY CASE: In my case, I had 2 distributions, wanted to create 3rd, but couldn't. So I have put as <TYPE_YOUR_NEW_VALUE_HERE> a number 10.
Note: If nothing works choose last option as your last resort to confirm your account is verified.
hope it helps.
I'm having the same issue even though I'm using Root User and I don't think it's a browser problem because another root user can be used normally. I tried to simulate and the permission column said allowed both CloudShell Create & StartEnvironment. How should I do?
Thank you very much.
Relevant questions
Start lightsail leads to a 403 error, even logging in with root
asked 2 months agoCan not start CloudShell
asked 22 days agoCloudshell wont start
asked a year agoUnable to start the environment. To retry, refresh the browser or restart by selecting Actions, Restart AWS CloudShell.
asked 7 months agounable to start cloudshell
asked 7 months agoUnable to restart apache
asked a year agoError when launching AWS CloudShell: "Unable to start the environment"
asked 8 months agoAWS cloudshell fails to start!Unable to start the environment. To retry, refresh the browser or restart by selecting Actions, Restart AWS CloudShell.
asked 7 months agoUnable to start the environment. To retry, refresh the browser or restart by selecting Actions, Restart AWS CloudShell
asked 4 months agocloudshell not working
asked 6 months ago
I have the same problem.
Another thread already running with the same problem https://repost.aws/questions/QUufc-elFvSvqYlbJw95RI6Q/unable-to-start-the-environment-to-retry-refresh-the-browser-or-restart-by-selecting-actions-restart-aws-cloud-shell