| ▲ | CjHuber 14 hours ago |
| Does Amazon refund you for mistakes, or do you have to land on HN frontpage for that to happen? |
|
| ▲ | Dunedan 14 hours ago | parent | next [-] |
| Depends on various factors and of course the amount of money in question. I've had AWS approve a refund for a rather large sum a few years ago, but that took quite a bit of back and forth with them. Crucial for the approval was that we had cost alerts already enabled before it happened and were able to show that this didn't help at all, because they triggered way too late. We also had to explain in detail what measures we implemented to ensure that such a situation doesn't happen again. |
| |
| ▲ | pyrale 11 hours ago | parent | next [-] | | Nothing says market power like being able to demand that your paying customers provide proof that they have solutions for the shortcomings of your platform. | |
| ▲ | rwmj 13 hours ago | parent | prev [-] | | Wait, what measures you implemented? How about AWS implements a hard cap, like everyone has been asking for forever? | | |
| ▲ | maccard 11 hours ago | parent | next [-] | | What does a hard cap look like for EBS volumes? Or S3? RDS? Do you just delete when the limit is hit? | | |
| ▲ | __s 11 hours ago | parent | next [-] | | It's a system people opt into, you can do something like ingress/egress blocked, & user has to pay a service charge (like overdraft) before access opened up again. If account is locked in overdraft state for over X amount of days then yes, delete data | | |
| ▲ | maccard 10 hours ago | parent [-] | | I can see the "AWS is holding me ransom" posts on the front page of HN already. |
| |
| ▲ | timando 4 hours ago | parent | prev | next [-] | | 2 caps: 1 for things that are charged for existing (e.g. S3 storage, RDS, EBS, EC2 instances) and 1 for things that are charged when you use them (e.g. bandwidth, lambda, S3 requests). Fail to create new things (e.g. S3 uploads) when the first cap is met. | |
| ▲ | wat10000 10 hours ago | parent | prev | next [-] | | A cap is much less important for fixed costs. Block transfers, block the ability to add any new data, but keep all existing data. | |
| ▲ | umanwizard 10 hours ago | parent | prev [-] | | Yes, delete things in reverse order of their creation time until the cap is satisfied (the cap should be a rate, not a total) | | |
| ▲ | maccard 10 hours ago | parent [-] | | I would put $100 that within 6 months of that, we'll get a post on here saying that their startup is gone under because AWS deleted their account because they didn't pay their bill and didn't realise their data would be deleted. > (the cap should be a rate, not a total) this is _way_ more complicated than there being a single cap. | | |
| ▲ | umanwizard 9 hours ago | parent [-] | | > I would put $100 that within 6 months of that, we'll get a post on here saying that their startup is gone under because AWS deleted their account because they didn't pay their bill and didn't realise their data would be deleted. The cap can be opt-in. | | |
| ▲ | maccard 8 hours ago | parent [-] | | > The cap can be opt-in. People will opt into this cap, and then still be surprised when their site gets shut down. |
|
|
|
| |
| ▲ | monerozcash 9 hours ago | parent | prev | next [-] | | >How about AWS implements a hard cap, like everyone has been asking for forever? s/everyone has/a bunch of very small customers have/ | |
| ▲ | Dunedan 13 hours ago | parent | prev [-] | | The measures were related to the specific cause of the unintended charges, not to never incur any unintended charges again. I agree AWS needs to provide better tooling to enable its customers to avoid such situations. |
|
|
|
| ▲ | throwawayffffas 2 hours ago | parent | prev | next [-] |
| I do not know. But in this case they probably should. They probably incurred no cost themselves. A bunch of data went down the "wrong" pipe, but in reality most likely all the data never left their networks. |
|
| ▲ | thecodemonkey 14 hours ago | parent | prev | next [-] |
| Hahaha. I'll update the post once I hear back from them. One could hope that they might consider an account credit. |
|
| ▲ | nijave 6 hours ago | parent | prev | next [-] |
| I've gotten a few refunds from them before. Not always and usually they come with stipulations to mitigate the risk of the mistake happening again |
|
| ▲ | Aeolun 14 hours ago | parent | prev | next [-] |
| I presume it depends on your ability to pay for your mistakes. A $20/month client is probably not going to pony up $1000, a $3000/month client will not care as much. |
|
| ▲ | viraptor 14 hours ago | parent | prev | next [-] |
| They do sometimes if you ask. Probably depends on each case though. |
|
| ▲ | stef25 13 hours ago | parent | prev [-] |
| > Does Amazon refund you for mistakes Hard no. Had to pay I think 100$ for premium support to find that out. |
