You enter your details, add a card, and wait. Then the email arrives: verification could not be completed. If this has happened to you, you are not alone — it is one of the most common complaints from developers trying to get onto AWS, and it is rarely your fault.
Here is what is actually going on, and what your options are.
The four things that usually break
1. Card authorisation fails
AWS places a small temporary authorisation on your card to confirm it is real. This fails constantly for reasons that have nothing to do with your balance: prepaid and virtual cards are frequently rejected, some banks block international authorisations by default, and cards issued in certain countries face additional scrutiny. The charge disappears, the signup does not proceed, and you get no useful explanation.
2. Identity verification loops
Document checks can fail on image quality, on a mismatch between the name on your document and the name on your card, or simply because the automated reviewer is not confident. Many people end up resubmitting the same document three or four times with no change in outcome.
3. Phone verification errors
The automated call or SMS does not always arrive, particularly on VoIP numbers or certain mobile carriers. Some numbers are silently rejected as ineligible.
4. You get in — and the quotas are useless
This one is the cruellest, because it happens after you think you have succeeded. A brand-new account typically starts with a very small vCPU quota. You cannot launch the instance type you need, so you file a quota increase request, and then you wait — sometimes days, sometimes longer, sometimes only to be declined.
What actually helps
- Use a real credit card, not a prepaid or virtual one. This resolves a large share of failures on its own.
- Make the names match exactly across your ID document, your card, and the account details you enter.
- Call your bank first and ask them to allow international authorisations before you try again.
- Use a mobile number, not VoIP, for phone verification.
- Do not hammer the retry button. Repeated failed attempts in a short window can get an account flagged, which makes everything harder.
- Request quota increases early, before you actually need the capacity, so the wait overlaps with your build time rather than blocking it.
When none of that works
Sometimes you do everything correctly and still get nowhere. Verification systems are automated, opaque, and not built to explain themselves. If you have exhausted the fixes above and you have a deadline, a pre-verified account is a legitimate shortcut: the identity and billing checks are already complete, the quotas are already raised, and you can start deploying immediately instead of arguing with a form.
That is precisely the problem we set out to solve. Our accounts arrive verified and quota-ready, usually within ten minutes. If you are stuck and want a second opinion before spending anything, just ask us — sometimes the fix really is as simple as switching cards.
Leave a Reply