I'm looking to perform load tests on my application that's deployed in AWS. I've already submitted a support ticket to notify them, but it's been sitting in 'unassigned' status for five days now. While I did receive some guidance from an AI bot about how to conduct the tests, I'm concerned that I might inadvertently get my account banned if I don't properly announce the testing. We plan to run these tests from a second account under the same organization and from local machines. I've got most of the setup ready, but I'm unsure about this notification part.
2 Answers
You actually don’t need a ticket for load testing unless you're doing something extreme like vulnerability scans or DDoS simulations. AWS is built to handle loads without interfering with others, so as long as you’re testing your own resources, you should be fine. Just make sure you aren't hammering shared services.
Yeah, I know someone who had their account banned after a load test last year. They did a JMeter setup that triggered some flags, so it's better to be cautious.
Five days of unassigned is pretty standard with AWS support, so don’t stress about it too much. They removed the load testing approval requirement in 2019, so you technically don’t need to ask for permission as long as you're not targeting shared services. Having the ticket is a good precaution though. I’d follow up on it and then start your tests gently—like ramping up to 50% first. If anything goes awry, you’ll have that support ticket just in case.
Thanks for the insight! Just bumped my ticket because we're aiming for 100 concurrent users. I expect some hiccups at 25 users without autoscaling. I'm sending calls straight to the API Gateway and should be good with no shared service hits.
That's true, AWS wants the load testing! More requests could mean more cash for them.