It is good that Amazon is protecting user accounts. But the way it was handled in my case is scary - writing just that my "account is closed", it "cannot be reopened" and it's the end, when I have a few sites running on AWS managed to frighten me ;) Maybe they would try to contact me before by phone if I didn't live in Eastern Europe, who knows?
Fortunately, an hour ago I received an email from Amazon saying that my account has been reinstated, so these few times I've contacted them about this problem have an effect.
Since this is the way Amazon treats its customers, Amazon can go fuck itself. I don't plan to ever buy anything from them again and I strongly urge people to think of the ramifications of this happening to a business run on AWS. I'm currently working on moving our company's infrastructure off their system and writing a blog post about it.
---
Hello,
We have noticed that you have returned a large number of your orders. While we expect occasional problems with orders, such large numbers of returns can suggest that customers are unaware of our return policies.
We want to call your attention to our returns policies because repeated misuse can result in the closure of your Amazon account. To learn more about our policies, search “About Our Returns Policies” in the Help section of Amazon.com.
If there is something we can do to help solve any recurring problems you are having with your orders, please reply to this email to reach an Account Specialist.
Sincerely,
Account Specialist
So for less than $100, I cannot imagine why they'd take this action. Is it a lot of returns on inexpensive things (e.g. 20 $5 items).
This scares me and makes me want to diversify my shopping with other retailers. :(
I didn't get any satisfactory answers, but this is exactly the kind of scenario I was afraid of.
A business that relies on AWS can be wiped out by an automated script in a different department. There is no mitigation since Amazon will also close "linked accounts", so having separate business and personal Amazon accounts isn't enough. It's super scary.
I tried tweeting @jeffbarr and posting in the AWS forums about these risks, but got no response from Amazon.
1: https://news.ycombinator.com/item?id=10248690