- Newest
- Most votes
- Most comments
Hi there,
Sorry to hear about your account verification issue.
Send us your case ID and we'll check from our end that it's with the correct team.
- Reece W.
I understand you're experiencing a block when trying to create a CloudFront distribution due to an account verification requirement, and that your support case has not yet received a response beyond the expected timeframe. I'm sorry for the delay you're experiencing.
For account verification issues like this, the AWS Support Center is the correct channel, and it sounds like you've already opened a case in the right category (Account and Billing → Account Activation → Account Verification). Since this is an account-level verification matter, it does require review by the AWS Customer Service team, and these cases are handled through the support case system.
While I cannot directly route or escalate cases, I can offer a few suggestions:
-
Add a new correspondence to your existing support case through the AWS Support Center (https://console.aws.amazon.com/support/). This can help bring attention to the case and provide any additional context that might be helpful.
-
If you have a paid AWS Support plan (Developer, Business, or Enterprise), you may have access to faster response times and additional support channels like phone or chat support, which could help expedite resolution.
-
Ensure that all required information has been provided in your case, including the exact error message you're seeing (which you've mentioned you already included).
The support team will work through cases in their queue, and adding correspondence to your existing case is the best way to ensure it receives attention. The team handling account verification cases will be able to review your account and enable CloudFront resource creation once the verification is complete.
Relevant content
- AWS OFFICIALUpdated a year ago

Hi Reece, thank you. The correctly categorized Account and Billing → Account Activation → Account Verification case ID is 178850964400640. It was opened on September 4 and remains unassigned. Please check that it is with the correct team and reroute or escalate it if necessary.