- Newest
- Most votes
- Most comments
I understand your frustration with the phone verification issue you're experiencing during your AWS account activation process. This is a known issue that can occur during the verification process, especially with international phone numbers like yours from Kenya.
Here are some steps you can try to resolve this issue:
-
Make sure you're entering your phone number correctly, including the country code and area code for Kenya.
-
Check that your phone has good reception and that international calls are enabled on your number.
-
Try clearing your browser's cache and cookies, then attempt the verification process again.
-
If possible, try using a different phone number for verification.
Since these steps haven't worked for you, I recommend requesting manual account activation through AWS Support:
- Go to the AWS Support console and choose "Create case"
- Select "Account and billing support"
- For Type, choose "Account", and for Category, select "Activation"
- In the Description section, clearly explain your issue with your Kenyan phone number
- Provide a specific date and time when you can be reached
- For Contact methods, select "Chat" for potentially faster response
AWS Support should be able to help you with manual account activation if the automated phone verification continues to fail. They may call you directly and ask you to confirm your AWS account ID.
You can create and manage support cases even if your account isn't fully activated yet, and AWS Support should be able to help you complete your account verification process so you can access the free tier benefits and credits you mentioned.
Sources
Account Activation Blocked - Phone Verification System Error - Multiple Support Cases Need Escalation | AWS re:Post
Can't Do the phone verifications for my new Account AWS | AWS re:Post
phone verification | AWS re:Post
Hello, I'm sorry to hear you're running into this issue with your AWS account activation. Hi there, I'm sorry to hear that the activation of your AWS account is giving you trouble. It sounds like a vicious cycle. It appears from the information you have given that there is a particular technical problem with the phone number verification procedure for your account in your area. The next step is to seek direct assistance from AWS Support since you have already attempted the common troubleshooting procedures and the automated response did not fix your issue. The following is a suggested course of action: "If you need assistance after working through the automated account activation process... respond to this support case," reads the automated email you received. You must do this. Directly reply to the email that AWS Support sent you. Give Specific Details Give a detailed explanation of what you've already shared in your response. Be succinct but comprehensive. Mention that you're from Nairobi, Kenya. Declare that the credit card and email verification processes were completed successfully. Indicate that you are experiencing a persistent "Sorry, there was an error processing your request" message during the last phone number verification step.Provide the precise error message. Keep in mind that despite your repeated attempts, the error still occurs.Make it clear that although your account is "open" and you are able to log in, the incomplete activation prevents you from using services like IAM. Make a Manual Review Request: Request a manual review of the activation status of your account. AWS Support's human agent can look into the problem on their end, avoiding the automated system that's causing it. Give a Different Way to Get in Touch If they need to try a different phone verification method, provide them with an alternate way to reach you, like a different phone number or a specific time window. Using this method will put your case in front of a real person who can diagnose the particular backend problem that is keeping your account from being fully activated. I wish you luck and hope you find a solution quickly!
answered 10 months ago
Relevant content
asked 4 months ago
- AWS OFFICIALUpdated 3 years ago
