AWS Account on Hold: Response Required [Solution Needed]

creditwala

BANNED - Failed to resolve a dispute
Joined
Dec 29, 2024
Messages
122
Reaction score
57
Hey guys,


I’ve been running into a weird and frustrating issue with AWS.


Whenever I create a new AWS account, I make sure to:


  • Use a clean proxy (residential / rotating, tested – not flagged)
  • Run through AdsPower anti-detect browser
  • Set up the account with realistic details
  • Add a working card and let the account warm up for 1 month
  • Even pay a small bill (like EC2 usage or S3 storage)
  • No shady activity at all

Then when I apply for AWS Activate Credits, a few days later the account gets suspended without any detailed reason.


This has happened multiple times, even with all precautions in place. I’ve seen others getting the credits smoothly – so I’m wondering:


Has anyone else faced this?​

  • Is AWS flagging accounts based on some deeper fingerprinting or history?
  • Could it be something in AdsPower config, or maybe my billing profile?
  • Any tips for passing the manual checks or making the account look more "legit" in AWS's eyes?

Any advice or experience would really help. I’ve already lost a few good credit approvals because of this.
 
Try warming it with some legit usage before applying for Activate, timing matters fr.
 
Try warming it with some legit usage before applying for Activate, timing matters fr.
Using EC2, Lightsail and some other service, also paying the bill and than applying,
 
maybe you can try another antidetect browser
 
It could be that your IP is rotating a few times while using the account which could be a red flag to amazon
 
AWS may be flagging hidden fingerprints like browser configs or billing patterns. Try a new anti-detect browser and stick to one stable IP after setup.
 
I encountered the same problem recently. Maybe AWS has strengthened its risk control. Have you found a solution?
 
Back
Top