Quotas and limitations for AWS Fault Injection Service
Your AWS account has default quotas, formerly referred to as limits, for each AWS service. Unless otherwise noted, each quota is Region-specific. You can request increases for some quotas, but not for all quotas.
To view the quotas for AWS FIS, open the Service Quotas console
To request a quota increase, see Requesting a quota increase in the Service Quotas User Guide.
Your AWS account has the following quotas related to AWS FIS.
| Name | Default | Adjustable | Description |
|---|---|---|---|
| Action duration in hours | Each supported Region: 12 | No | The maximum number of hours allowed to run one action in this account in the current Region. |
| Actions per experiment template | Each supported Region: 20 | No | The maximum number of actions that you can create in an experiment template in this account in the current Region. |
| Active experiments | Each supported Region: 5 | No | The maximum number of active experiments that you can run simultaneously in this account in the current Region. |
| Completed experiment data retention in days | Each supported Region: 120 | No | The maximum number of days allowed for AWS FIS to retain data about completed experiments in this account in the current Region. |
| Experiment duration in hours | Each supported Region: 12 | No | The maximum number of hours allowed to run one experiment in this account in the current Region. |
| Experiment templates | Each supported Region: 500 | No | The maximum number of experiment templates that you can create in this account in the current Region. |
| Maximum number of Managed Prefix Lists in aws:network:route-table-disrupt-cross-region-connectivity | Each supported Region: 15 | No | The maximum number of Managed Prefix Lists that aws:network:route-table-disrupt-cross-region-connectivity will allow, per action. |
| Maximum number of Route Tables in aws:network:route-table-disrupt-cross-region-connectivity | Each supported Region: 10 | No | The maximum number of Route Tables that aws:network:route-table-disrupt-cross-region-connectivity will allow, per action. |
| Maximum number of routes in aws:network:route-table-disrupt-cross-region-connectivity | Each supported Region: 200 | No | The maximum number of routes that aws:network:route-table-disrupt-cross-region-connectivity will allow, per action. |
| Parallel actions per experiment | Each supported Region: 10 | No | The maximum number of actions that you can run in parallel in an experiment in this account in the current Region. |
| Stop conditions per experiment template | Each supported Region: 5 | No | The maximum number of stop conditions that you can add to an experiment template in this account in the current Region. |
| Target Auto Scaling groups for aws:ec2:asg-insufficient-instance-capacity-error | Each supported Region: 5 |
Yes |
The maximum number of Auto Scaling groups that aws:ec2:asg-insufficient-instance-capacity-error can target when you identify targets using tags, per experiment. |
| Target Buckets for aws:s3:bucket-pause-replication | Each supported Region: 20 |
Yes |
The maximum number of S3 Buckets that aws:s3:bucket-pause-replication can target when you identify targets using tags, per experiment. |
| Target Clusters for aws:ecs:drain-container-instances | Each supported Region: 5 |
Yes |
The maximum number of Clusters that aws:ecs:drain-container-instances can target when you identify targets using tags, per experiment. |
| Target Clusters for aws:rds:failover-db-cluster | Each supported Region: 5 |
Yes |
The maximum number of Clusters that aws:rds:failover-db-cluster can target when you identify targets using tags, per experiment. |
| Target DBInstances for aws:rds:reboot-db-instances | Each supported Region: 5 |
Yes |
The maximum number of DBInstances that aws:rds:reboot-db-instances can target when you identify targets using tags, per experiment. |
| Target Instances for aws:ec2:reboot-instances | Each supported Region: 5 |
Yes |
The maximum number of Instances that aws:ec2:reboot-instances can target when you identify targets using tags, per experiment. |
| Target Instances for aws:ec2:stop-instances | Each supported Region: 5 |
Yes |
The maximum number of Instances that aws:ec2:stop-instances can target when you identify targets using tags, per experiment. |
| Target Instances for aws:ec2:terminate-instances | Each supported Region: 5 |
Yes |
The maximum number of Instances that aws:ec2:terminate-instances can target when you identify targets using tags, per experiment. |
| Target Instances for aws:ssm:send-command | Each supported Region: 5 |
Yes |
The maximum number of Instances that aws:ssm:send-command can target when you identify targets using tags, per experiment. |
| Target Nodegroups for aws:eks:terminate-nodegroup-instances | Each supported Region: 5 |
Yes |
The maximum number of Nodegroups that aws:eks:terminate-nodegroup-instances can target when you identify targets using tags, per experiment. |
| Target Pods for aws:eks:pod-cpu-stress | Each supported Region: 50 |
Yes |
The maximum number of Pods that aws:eks:pod-cpu-stress can target when you identify targets using parameters, per experiment. |
| Target Pods for aws:eks:pod-delete | Each supported Region: 50 |
Yes |
The maximum number of Pods that aws:eks:pod-delete can target when you identify targets using parameters, per experiment. |
| Target Pods for aws:eks:pod-io-stress | Each supported Region: 50 |
Yes |
The maximum number of Pods that aws:eks:pod-io-stress can target when you identify targets using parameters, per experiment. |
| Target Pods for aws:eks:pod-memory-stress | Each supported Region: 50 |
Yes |
The maximum number of Pods that aws:eks:pod-memory-stress can target when you identify targets using parameters, per experiment. |
| Target Pods for aws:eks:pod-network-blackhole-port | Each supported Region: 50 |
Yes |
The maximum number of Pods that aws:eks:pod-network-blackhole-port can target when you identify targets using parameters, per experiment. |
| Target Pods for aws:eks:pod-network-latency | Each supported Region: 50 |
Yes |
The maximum number of Pods that aws:eks:pod-network-latency can target when you identify targets using parameters, per experiment. |
| Target Pods for aws:eks:pod-network-packet-loss | Each supported Region: 50 |
Yes |
The maximum number of Pods that aws:eks:pod-network-packet-loss can target when you identify targets using parameters, per experiment. |
| Target ReplicationGroups for aws:elasticache:interrupt-cluster-az-power | Each supported Region: 5 |
Yes |
The maximum number of ReplicationGroups that aws:elasticache:interrupt-cluster-az-power can target when you identify targets using tags/parameters, per experiment. |
| Target SpotInstances for aws:ec2:send-spot-instance-interruptions | Each supported Region: 5 |
Yes |
The maximum number of SpotInstances that aws:ec2:send-spot-instance-interruptions can target when you identify targets using tags, per experiment. |
| Target Subnets for aws:network:disrupt-connectivity | Each supported Region: 5 |
Yes |
The maximum number of Subnets that aws:network:disrupt-connectivity can target when you identify targets using tags, per experiment. Quotas above 5 apply only to parameter scope:all. If you require a higher quota for another scope type, contact customer support at https://console.aws.amazon.com/support/home#/. |
| Target Subnets for aws:network:route-table-disrupt-cross-region-connectivity | Each supported Region: 6 |
Yes |
The maximum number of Subnets that aws:network:route-table-disrupt-cross-region-connectivity can target when you identify targets using tags, per experiment. |
| Target Tasks for aws:ecs:stop-task | Each supported Region: 5 |
Yes |
The maximum number of Tasks that aws:ecs:stop-task can target when you identify targets using tags, per experiment. |
| Target Tasks for aws:ecs:task-cpu-stress | Each supported Region: 5 |
Yes |
The maximum number of Tasks that aws:ecs:task-cpu-stress can target when you identify targets using tags/parameters, per experiment. |
| Target Tasks for aws:ecs:task-io-stress | Each supported Region: 5 |
Yes |
The maximum number of Tasks that aws:ecs:task-io-stress can target when you identify targets using tags/parameters, per experiment. |
| Target Tasks for aws:ecs:task-kill-process | Each supported Region: 5 |
Yes |
The maximum number of Tasks that aws:ecs:task-kill-process can target when you identify targets using tags/parameters, per experiment. |
| Target Tasks for aws:ecs:task-network-blackhole-port | Each supported Region: 5 |
Yes |
The maximum number of Tasks that aws:ecs:task-network-blackhole-port can target when you identify targets using tags/parameters, per experiment. |
| Target Tasks for aws:ecs:task-network-latency | Each supported Region: 5 |
Yes |
The maximum number of Tasks that aws:ecs:task-network-latency can target when you identify targets using tags/parameters, per experiment. |
| Target Tasks for aws:ecs:task-network-packet-loss | Each supported Region: 5 |
Yes |
The maximum number of Tasks that aws:ecs:task-network-packet-loss can target when you identify targets using tags/parameters, per experiment. |
| Target TransitGateways for aws:network:transit-gateway-disrupt-cross-region-connectivity | Each supported Region: 5 |
Yes |
The maximum number of Transit Gateways that aws:network:transit-gateway-disrupt-cross-region-connectivity can target when you identify targets using tags, per experiment. |
| Target account configurations per experiment template | Each supported Region: 10 |
Yes |
The maximum number of target account configurations that you can create for an experiment template in this account in the current Region. |
| Target tables for aws:dynamodb:global-table-pause-replication action | Each supported Region: 5 |
Yes |
The maximum number of global tables that aws:dynamodb:global-table-pause-replication can target, per experiment. |
Your usage of AWS FIS is subject to the following additional limitations:
| Name | Limitation |
|---|---|
|
Targets for |
Limited to 10 |
