CloudShell "Unable to create the environment. Your account verification is in progress" but account verification not needed
Getting error trying to start CloudShell but not being given an option to do "Customer Verification".
I tried setting a Monthly Budget as suggested here with no success: https://repost.aws/questions/QUVUA7sbi9THS6cpkxwK8Jqg/unable-to-start-the-environment-you-must-verify-your-account-before-accessing-cloudshell-to-verify-your-account-contact-aws-support
- Newest
- Most votes
- Most comments
Greetings,
Given the nature of your inquiry, I strongly recommend engaging AWS Support directly for the most efficient resolution.
Please note:
- For newly created accounts, it is advised to wait 48 hours to allow for the completion of the verification process before contacting support.
- For established accounts, you may proceed with opening a support case immediately.
To initiate this process, please follow these steps:
- Open a support case under the "Account and billing" category. This ensures your inquiry is handled free of charge, allowing you to seek assistance without incurring additional costs.
- In your case description, include the specific error message you've encountered and any other pertinent details that may assist our support team in addressing your concern.
For comprehensive guidance on managing and creating support cases, please consult the official documentation:
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
answered 2 years ago
It looks like you’re facing an IAM permission issue when trying to use AWS CloudShell. Even if you’ve added yourself to an IAM role, CloudShell requires specific permissions to work properly.
Steps to Fix:
1.Check IAM Policies: Ensure your IAM role has the necessary policies attached, such as AWSCloudShellFullAccess. You can check this in the IAM Console--> Roles--> [Your Role]-->Permissions.
2.Verify Service Control Policies (SCPs): If you’re in an AWS Organization, SCPs might be blocking CloudShell access.
3.Look at AWS Config & Guardrails: Some AWS Config rules or Organizational Service Control Policies might be restricting CloudShell use.
4.Try Another Region: Some AWS services behave differently across regions. If possible, test CloudShell in a different region.
Regarding Deletion:
No, deleting CloudShell will NOT affect your EC2 instances or S3 buckets. CloudShell is a separate service and does not directly interact with running instances or storage.
However, any temporary files stored in the CloudShell environment will be lost.
If it still doesn’t work, try running this AWS CLI command to check your current permissions:
aws sts get-caller-identity
This will confirm the active IAM role and its permissions.
answered a year ago
