A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.aws.amazon.com/fis/latest/userguide/fis-actions-reference.html below:

AWS FIS Actions reference - AWS Fault Injection Service

AWS FIS Actions reference

An action is the fault injection activity that you run on a target using AWS Fault Injection Service (AWS FIS). AWS FIS provides preconfigured actions for specific types of targets across AWS services. You add actions to an experiment template, which you then use to run experiments.

This reference describes the common actions in AWS FIS, including information about the action parameters and the required IAM permissions. You can also list the supported AWS FIS actions using the AWS FIS console or the list-actions command from the AWS Command Line Interface (AWS CLI). Once you have the name of a specific action, you can view detailed information about the action by using the get-action command. For more information on using AWS FIS commands with the AWS CLI, see the AWS Command Line Interface User Guide and fis in the AWS CLI Command Reference.

For more information on how AWS FIS actions work, see Actions for AWS FIS and How AWS Fault Injection Service works with IAM.

Fault injection actions

AWS FIS supports the following fault injection actions.

aws:fis:inject-api-internal-error

Injects Internal Errors into requests made by the the target IAM role. The specific response depends on each service and API. For more information, please review the SDK and API documentation of your service.

Resource type Parameters Permissions aws:fis:inject-api-throttle-error

Injects throttling errors into requests made by the target IAM role. The specific response depends on each service and API. For more information, please review the SDK and API documentation of your service.

Resource type Parameters Permissions aws:fis:inject-api-unavailable-error

Injects Unavailable errors into requests made by the target IAM role. The specific response depends on each service and API. For more information, please review the SDK and API documentation of your service.

Resource type Parameters Permissions Recovery action

Recovery actions are performed to mitigate risk or protect applications after impairment.

AWS FIS supports the following recovery actions.

aws:arc:start-zonal-autoshift

Automatically shifts traffic for supported resources away from a potentially impaired Availability Zone (AZ) and reroutes them to healthy AZs in the same AWS Region. This allows for experiencing zonal autoshift through FIS. Zonal autoshift is a capability in Amazon Application Recovery Controller (ARC) that allows AWS to shift traffic for a resource away from an AZ, on your behalf, when AWS determines that there is an impairment that could potentially affect customers in the AZ.

When you run the aws:arc:start-zonal-autoshift action, AWS FIS manages the zonal shift using the StartZonalShift, UpdateZonalShift, and CancelZonalShift APIs with the expiresIn field for these requests set to 1 minute as a safety mechanism. This enables AWS FIS to quickly rollback the zonal shift in the case of any unexpected events such as network outages or system issues. In the ARC console, the expiration time field will display AWS FIS-managed, and the actual expected expiration is determined by the duration specified in the zonal shift action.

Resource type Parameters Permissions Wait action

AWS FIS supports the following wait action.

aws:fis:wait

Runs the AWS FIS wait action.

Parameters Amazon CloudWatch actions

AWS FIS supports the following Amazon CloudWatch action.

aws:cloudwatch:assert-alarm-state

Verifies that the specified alarms are in one of the specified alarm states.

Parameters Permissions Amazon DynamoDB actions

AWS FIS supports the following Amazon DynamoDB action.

aws:dynamodb:global-table-pause-replication

Pauses Amazon DynamoDB multi-Region eventually consistent (MREC) global table replication to any replica table. Tables may continue to be replicated for up to 5 minutes after action begins.

This action does not support multi-Region strongly consistent (MRSC) global tables. For more information see Consistency modes, in the Amazon DynamoDB developer guide.

The following statement will be dynamically appended to the policy for the target DynamoDB MREC global table:

{
   "Statement":[
      {
         "Sid": "DoNotModifyFisDynamoDbPauseReplicationEXPxxxxxxxxxxxxxxx",
         "Effect":"Deny",
         "Principal":{
            "AWS":"arn:aws:iam::123456789012:role/aws-service-role/replication.dynamodb.amazonaws.com/AWSServiceRoleForDynamoDBReplication"
         },
         "Action":[
            "dynamodb:GetItem",
            "dynamodb:PutItem",
            "dynamodb:UpdateItem",
            "dynamodb:DeleteItem",
            "dynamodb:DescribeTable",
            "dynamodb:UpdateTable",
            "dynamodb:Scan",
            "dynamodb:DescribeTimeToLive",
            "dynamodb:UpdateTimeToLive"
         ],
         "Resource":"arn:aws:dynamodb:us-east-1:123456789012:table/ExampleGlobalTable",
         "Condition": {
            "DateLessThan": {
            "aws:CurrentTime": "2024-04-10T09:51:41.511Z"
         }
       }
      }
   ]
}

The following statement will be dynamically appended to the stream policy for the target DynamoDB MREC global table:

{
   "Statement":[
      {
         "Sid": "DoNotModifyFisDynamoDbPauseReplicationEXPxxxxxxxxxxxxxxx",
         "Effect":"Deny",
         "Principal":{
            "AWS":"arn:aws:iam::123456789012:role/aws-service-role/replication.dynamodb.amazonaws.com/AWSServiceRoleForDynamoDBReplication"
         },
         "Action":[
            "dynamodb:GetRecords",
            "dynamodb:DescribeStream",
            "dynamodb:GetShardIterator"
         ],
         "Resource":"arn:aws:dynamodb:us-east-1:123456789012:table/ExampleGlobalTable/stream/2023-08-31T09:50:24.025",
         "Condition": {
            "DateLessThan": {
            "aws:CurrentTime": "2024-04-10T09:51:41.511Z"
         }
      }
   ]
}

If a target table or stream does not have any attached resource polices, a resource policy is created for the duration of the experiment, and automatically deleted when the experiment ends. Otherwise, the fault statement is inserted into an existing policy, without any additional modifications to the existing policy statements. The fault statement is then removed from the policy at the end of the experiment.

Resource type Parameters Permissions Amazon EBS actions

AWS FIS supports the following Amazon EBS action.

aws:ebs:pause-volume-io

Pauses I/O operations on target EBS volumes. The target volumes must be in the same Availability Zone and must be attached to instances built on the Nitro System. The volumes can't be attached to instances on an Outpost.

To initiate the experiment using the Amazon EC2 console, see Fault testing on Amazon EBS in the Amazon EC2 User Guide.

Resource type Parameters Permissions Amazon EC2 actions

AWS FIS supports the following Amazon EC2 actions.

AWS FIS also supports fault injection actions through the AWS Systems Manager SSM Agent. Systems Manager uses an SSM document that defines actions to perform on EC2 instances. You can use your own document to inject custom faults, or you can use pre-configured SSM documents. For more information, see Use Systems Manager SSM documents with AWS FIS.

aws:ec2:api-insufficient-instance-capacity-error

Injects InsufficientInstanceCapacity error responses on requests made by the target IAM roles. Supported operations are RunInstances, CreateCapacityReservation, StartInstances, CreateFleet calls. Requests that include capacity asks in multiple Availability Zones are not supported. This action doesn't support defining targets using resource tags, filters, or parameters.

Resource type Parameters Permissions

For an example policy, see Example: Use condition keys for ec2:InjectApiError.

aws:ec2:asg-insufficient-instance-capacity-error

Injects InsufficientInstanceCapacity error responses on requests made by the target Auto Scaling groups. This action only supports Auto Scaling groups using launch templates. To learn more about insufficient instance capacity errors, see the Amazon EC2 user guide.

Resource type Parameters Permissions

For an example policy, see Example: Use condition keys for ec2:InjectApiError.

aws:ec2:reboot-instances

Runs the Amazon EC2 API action RebootInstances on the target EC2 instances.

Resource type Permissions aws:ec2:send-spot-instance-interruptions

Interrupts the target Spot Instances. Sends a Spot Instance interruption notice to target Spot Instances two minutes before interrupting them. The interruption time is determined by the specified durationBeforeInterruption parameter. Two minutes after the interruption time, the Spot Instances are terminated or stopped, depending on their interruption behavior. A Spot Instance that was stopped by AWS FIS remains stopped until you restart it.

Immediately after the action is initiated, the target instance receives an EC2 instance rebalance recommendation. If you specified durationBeforeInterruption, there could be a delay between the rebalance recommendation and the interruption notice.

For more information, see Tutorial: Test Spot Instance interruptions using AWS FIS. Alternatively, to initiate the experiment by using the Amazon EC2 console, see Initiate a Spot Instance interruption in the Amazon EC2 User Guide.

Resource type Parameters Permissions aws:ec2:stop-instances

Runs the Amazon EC2 API action StopInstances on the target EC2 instances.

Resource type Parameters Permissions aws:ec2:terminate-instances

Runs the Amazon EC2 API action TerminateInstances on the target EC2 instances.

Resource type Permissions Amazon ECS actions

AWS FIS supports the following Amazon ECS actions.

aws:ecs:drain-container-instances

Runs the Amazon ECS API action UpdateContainerInstancesState to drain the specified percentage of underlying Amazon EC2 instances on the target clusters.

Resource type Parameters Permissions aws:ecs:stop-task

Runs the Amazon ECS API action StopTask to stop the target task.

Resource type Permissions aws:ecs:task-cpu-stress

Runs CPU stress on the target tasks. Uses the AWSFIS-Run-CPU-Stress SSM document. The tasks must be managed by AWS Systems Manager. For more information, see ECS task actions.

Resource type Parameters Permissions aws:ecs:task-io-stress

Runs I/O stress on the target tasks. Uses the AWSFIS-Run-IO-Stress SSM document. The tasks must be managed by AWS Systems Manager. For more information, see ECS task actions.

Resource type Parameters Permissions aws:ecs:task-kill-process

Stops the specified process in the tasks, using the killall command. Uses the AWSFIS-Run-Kill-Process SSM document. The task definition must have pidMode set to task. The tasks must be managed by AWS Systems Manager. For more information, see ECS task actions.

Resource type Parameters Permissions aws:ecs:task-network-blackhole-port

Drops inbound or outbound traffic for the specified protocol and port, using the Amazon ECS Fault Injection endpoints. Uses the AWSFIS-Run-Network-Blackhole-Port-ECS SSM document. The task definition must have pidMode set to task. The tasks must be managed by AWS Systems Manager. You can't set networkMode to bridge in the task definition. For more information, see ECS task actions.

When useEcsFaultInjectionEndpoints is set to false, the fault uses the iptables tool, and uses the AWSFIS-Run-Network-Blackhole-Port SSM document.

Resource type Parameters Permissions aws:ecs:task-network-latency

Adds latency and jitter to the network interface for egress traffic to specific sources, using the Amazon ECS Fault Injection endpoints . Uses the AWSFIS-Run-Network-Latency-ECS SSM document. The task definition must have pidMode set to task. The tasks must be managed by AWS Systems Manager. You can't set networkMode to bridge in the task definition. For more information, see ECS task actions.

When useEcsFaultInjectionEndpoints is set to false, the fault uses the tc tool, and uses the AWSFIS-Run-Network-Latency-Sources SSM document.

Resource type Parameters Permissions aws:ecs:task-network-packet-loss

Adds packet loss to the network interface for egress traffic to specific sources, using the Amazon ECS Fault Injection endpoints. Uses the AWSFIS-Run-Network-Packet-Loss-ECS SSM document. The task definition must have pidMode set to task. The tasks must be managed by AWS Systems Manager. You can't set networkMode to bridge in the task definition. For more information, see ECS task actions.

When useEcsFaultInjectionEndpoints is set to false, the fault uses the tc tool, and uses the AWSFIS-Run-Network-Packet-Loss-Sources SSM document.

Resource type Parameters Permissions Amazon EKS actions

AWS FIS supports the following Amazon EKS actions.

aws:eks:inject-kubernetes-custom-resource

Runs a ChaosMesh or Litmus experiment on a single target cluster. You must install ChaosMesh or Litmus on the target cluster.

When you create an experiment template and define a target of type aws:eks:cluster, you must target this action to a single Amazon Resource Name (ARN). This action doesn't support defining targets using resource tags, filters, or parameters.

When you install ChaosMesh, you must specify the appropriate container runtime. Starting with Amazon EKS version 1.23, the default runtime changed from Docker to containerd. Starting with version 1.24, Docker was removed.

Resource type Parameters Permissions

No AWS Identity and Access Management (IAM) permissions are required for this action. The permissions required to use this action are controlled by Kubernetes using RBAC authorization. For more information, see Using RBAC Authorization in the official Kubernetes documentation. For more information about Chaos Mesh, see the official Chaos Mesh documentation. For more information about Litmus, see the official Litmus documentation.

aws:eks:pod-cpu-stress

Runs CPU stress on the target pods. For more information, see EKS Pod actions.

Resource type Parameters Permissions aws:eks:pod-delete

Deletes the target pods. For more information, see EKS Pod actions.

Resource type Parameters Permissions aws:eks:pod-io-stress

Runs I/O stress on the target pods. For more information, see EKS Pod actions.

Resource type Parameters Permissions aws:eks:pod-memory-stress

Runs memory stress on the target pods. For more information, see EKS Pod actions.

Resource type Parameters Permissions aws:eks:pod-network-blackhole-port

Drops inbound or outbound traffic for the specified protocol and port. Only compatible with the Kubernetes Security Standards privilegedpolicy. For more information, see EKS Pod actions.

Resource type Parameters Permissions aws:eks:pod-network-latency

Adds latency and jitter to the network interface using the tc tool for traffic to or from specific sources. Only compatible with the Kubernetes Security Standards privilegedpolicy. For more information, see EKS Pod actions.

Resource type Parameters Permissions aws:eks:pod-network-packet-loss

Adds packet loss to the network interface using the tc tool. Only compatible with the Kubernetes Security Standards privilegedpolicy. For more information, see EKS Pod actions.

Resource type Parameters Permissions aws:eks:terminate-nodegroup-instances

Runs the Amazon EC2 API action TerminateInstances on the target node group. Only compatible with Amazon EKS managed node groups. Self-managed node groups are not supported. For more information, see EKS manage compute.

Resource type Parameters Permissions Amazon ElastiCache actions

AWS FIS supports the following ElastiCache action.

aws:elasticache:replicationgroup-interrupt-az-power

Interrupts power to nodes in the specified Availability Zone for target ElastiCache replication groups with Multi-AZ enabled. Only one Availability Zone per replication group can be impacted at a time. When a primary node is targeted, the corresponding read replica with the least replication lag is promoted to primary. Read replica replacements in the specified Availability Zone are blocked for the duration of this action, which means that target Replication Groups operate with reduced capacity. The target for this action supports both Redis and Valkey engines. The action does not support the "serverless" deployment option.

Resource type Parameters Permissions

Note

The ElastiCache interrupt AZ power action now supports all replication group types, including Valkey and Redis. To better represent this functionality, the action has been renamed. If you are currently using aws:elasticache:interrupt-cluster-az-power, we recommend that you migrate to the new action aws:elasticache:replicationgroup-interrupt-az-power to take advantage of the latest features.

AWS Lambda actions

AWS Lambda supports the following Lambda actions

aws:lambda:invocation-add-delay

Delays starting a function for a number of milliseconds that you specify. The effect of this action is similar to Lambda cold starts, but the additional time is spent as part of the billed duration and is applied to all execution environments rather than only affecting new execution environments. This means that you may experience both a Lambda cold start and this delay. By setting a latency value higher than the timeout configured on the Lambda function, this action will also provide access to a high fidelity timeout event.

Resource type Parameters Permissions aws:lambda:invocation-error

Marks Lambda function invocations as failed. This action is useful for testing error handling mechanisms, such as alarms and retry configurations. While using this action, you select whether or not to run the function code before returning an error.

Resource type Parameters Permissions aws:lambda:invocation-http-integration-response

Modifies the behavior of the function. You select a content type and HTTP response code to support integrations with ALB, API-GW and VPC Lattice. To enable selectively impacting upstream or downstream integrations, you can choose whether to directly return the modified response or whether to run the function and replace the response after the function finishes execution.

Resource type Parameters Permissions Amazon MemoryDB action

AWS FIS supports the following MemoryDB action.

aws:memorydb:multi-region-cluster-pause-replication

Pauses the replication between one regional cluster and all other regional clusters within the multi-Region cluster. The regional cluster targeted is the cluster in the Region where the FIS experiment is running. While the replication is paused, the multi-Region cluster cannot be updated. Once the action completes, it may take a few minutes for the multi-Region cluster to return to an available state. To learn more about Amazon MemoryDB Multi-Region, see the Amazon MemoryDB Multi-Region Developer Guide. For Region availability, see MemoryDB Multi-Region Prerequisites and limitations.

Resource type Parameters Permissions Network actions

AWS FIS supports the following network actions.

aws:network:disrupt-connectivity

Denies the specified traffic to the target subnets by temporarily cloning the original network access control list (network ACL) associated with the targeted subnet. FIS adds deny rules to the cloned network ACL, which has a tag managedbyFIS=true, and associates it with the subnet for the duration of the action. At action completion, FIS deletes the cloned network ACL and restores the original network ACL association.

Resource type Parameters Permissions aws:network:route-table-disrupt-cross-region-connectivity

Blocks traffic that originates in the target subnets and is destined for the specified Region. Creates route tables that include all routes for the Region to isolate. To allow FIS to create these route tables, raise the Amazon VPC quota for routes per route table to 250 plus the number of routes in your existing route tables.

Resource type Parameters Permissions

† Scoped using the tag managedByFIS=true. You do not need to manage this tag. AWS FIS adds and removes this tag during the experiment.

aws:network:transit-gateway-disrupt-cross-region-connectivity

Blocks traffic from the target transit gateway peering attachments that is destined for the specified Region.

Resource type Parameters Permissions Amazon RDS actions

AWS FIS supports the following Amazon RDS actions.

aws:rds:failover-db-cluster

Runs the Amazon RDS API action FailoverDBCluster on the target Aurora DB cluster.

Resource type Permissions aws:rds:reboot-db-instances

Runs the Amazon RDS API action RebootDBInstance on the target DB instance.

Parameters Permissions Amazon S3 actions

AWS FIS supports the following Amazon S3 action.

aws:s3:bucket-pause-replication

Pauses replication from target source buckets to destination buckets. Destination buckets can be in different AWS Regions or within the same Region as the source bucket. Existing objects may continue to be replicated for up to one hour after action begins. This action only supports targeting by tags. To learn more about Amazon S3 Replication, see the Amazon S3 user guide.

Resource type Parameters Permissions

For an example policy, see Example: Use condition keys for aws:s3:bucket-pause-replication.

Systems Manager actions

AWS FIS supports the following Systems Manager actions.

aws:ssm:send-command

Runs the Systems Manager API action SendCommand on the target EC2 instances. The Systems Manager document (SSM document) defines the actions that Systems Manager performs on your instances. For more information, see Use the aws:ssm:send-command action.

Resource type Parameters Permissions aws:ssm:start-automation-execution

Runs the Systems Manager API action StartAutomationExecution.

Parameters Permissions

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4