- Newest
- Most votes
- Most comments
For your CloudFront issue, you're encountering a common verification requirement that AWS implements as a security measure. When you see the "AccessDenied" error stating that your account must be verified before adding CloudFront resources, you need to go through a specific verification process:
- Log in to your AWS Management Console
- Navigate to the AWS Support Center
- Create a new support case under "Account and billing support" category
- Choose "Service Limit Increase" as the category and select "CloudFront" as the service
- In your description, include the exact error message you received
- Submit the case and wait for AWS Support to respond
This verification is required even if you've already been using other AWS services like EC2, S3, or Lambda, and even if you've paid previous bills. It's specifically for CloudFront resources.
Regarding your MediaConvert issue with the "SubscriptionRequiredException" error, simply clicking the "Get Started" button in the console might not be sufficient. Similar to CloudFront, you may need to:
- Open a support case specifically for MediaConvert access
- Select "Service Limit Increase" as the category
- Choose "MediaConvert" as the service
- Explain that you've already clicked "Get Started" but are still encountering the subscription exception
Support response times can vary, but for account verification issues, they typically respond within 24-48 hours. If it's been more than 24 hours since you submitted your cases, you might want to follow up on your existing cases rather than creating new ones.
These verification processes are one-time requirements. Once your account is verified for these services, you shouldn't encounter these specific issues again when creating new resources in the future.
Sources
CloudFront Verification | AWS re:Post
CloudFront verification & Open NextJS | AWS re:Post
Can not create Cloudfront distribution | AWS re:Post
Relevant content
asked 7 months ago
