I’ll introduce the application process for load testing of API / Web services built on AWS.

Premise: In most cases, application for load testing to AWS is unnecessary

Testing conducted by customers usually does not fall under this policy.

Source: テストポリシー - Amazon EC2 | AWS

Cases where application for load testing to AWS is required/not required

Cases where application is required

• Generating traffic exceeding 1Gbps (bits per second) continuously for more than 1 minute
• Generating traffic exceeding 1Gpps (packets per second)
• Generating traffic that appears malicious or annoying
• Generating traffic that potentially affects entities other than the expected targets (routing or shared service infrastructure)

Cases where application is not required

• Traffic of 1Gbps or less
• Production, commercial, or equivalent traffic
• Load testing equivalent to production workloads (when network load testing is not the main purpose)

Source: Amazon EC2 インスタンスに構築した環境への負荷テストを実施するには申請が必要でしょうか？ | DevelopersIO

Other considerations

• AWS サービスクォータ - AWS 全般のリファレンス
• [AWS] Application Load Balancerの暖機が必要なラインについて探る[リベンジ] | 個人利用で始めるAWS学習記

That’s all from the Gemba about investigating whether application is required or not for load testing API / Web services built on AWS.

Reference information

• [AWS]結局AWSの負荷テストに申請がいるのかいらないのか - Qiita