AWS mistakes to avoid

Re:AWS mistakes to avoid by flyt on Sunday December 27, 2015 @01:43AM (#10796670)

This is categorically false. If you have large capacity needs talk to your TAMs/Account Manager and they can make it happen.

[ Parent | on HN ]

Re:AWS mistakes to avoid by late2part on Sunday December 27, 2015 @02:02AM (#10796711)

It's been true five times in the last three years for me. The elasticity isn't always there and service limits are not always granted when needed.

I don't know what an AWS TAM is but the SAs have tried and failed.

Make a new account and try to run 1000 c4.4xl in parallel for 1 hour. It won't happen.

That's not what happened the five times, but it's illustrative.

And who defines what is a need and what is a want?

[ Parent | on HN ]

Re:AWS mistakes to avoid by slaman on Tuesday December 29, 2015 @05:18PM (#10809443)

That's because of a history of bitcoin mining abuse. People post their API keys on github every day and Amazon refunds almost all of the lost compute time.

[ Parent | on HN ]

Re:AWS mistakes to avoid by _delirium on Sunday December 27, 2015 @01:13PM (#10798216)

I've asked and got basically a "no". I can believe that if you have a history of spending big $$$ on AWS they get increasingly flexible with raising the limits. But if you don't, they aren't going to let you spin up 500 instances, even if you ask nicely and have a reasonable justification.

[ Parent | on HN ]