- Newest
- Most votes
- Most comments
This is a common situation where certain AWS services require additional verification steps beyond the standard account verification, even when your account appears fully verified and other services are working normally.
For CloudFront specifically, AWS implements additional security measures and verification requirements before allowing distribution creation. This is because CloudFront is a global content delivery service that can potentially be used for high-volume traffic distribution, so AWS takes extra precautions to prevent abuse.
Similarly, AWS CloudShell may have additional verification requirements as it provides direct CLI access to your AWS resources.
Here are some steps you can take:
-
Check your payment method: Ensure your payment method is valid and up-to-date, even on the free tier. Some services require a verified payment method before they can be activated.
-
Wait for the support case response: Since you've already created a support case, this is the right approach. Support cases can sometimes take 12-24 hours for an initial response, depending on your support plan.
-
Check for any pending verification emails: Look through your email (including spam folders) for any verification requests from AWS that you might have missed.
-
Review account limits: New accounts sometimes have service-specific restrictions that are lifted after the account has been active for a certain period or after verification.
Since you've already opened a support case, AWS Support is the best resource to resolve this issue as they can review your specific account status and expedite any necessary verification steps. They have access to your account details and can identify exactly what verification is needed.
Relevant content
- asked a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
