AWS ebs documentation change
Summary
Restructured documentation for AWS FIS integration with EBS, added latency injection experiment support, updated considerations, and removed step-by-step console instructions.
Security assessment
The changes focus on improving clarity, adding new fault injection capabilities (latency injection), and updating operational considerations. While fault injection testing can improve resilience, there is no evidence of addressing a specific security vulnerability or weakness. The documentation updates describe general testing methodologies rather than security-specific features.
Diff
diff --git a/ebs/latest/userguide/ebs-fis.md b/ebs/latest/userguide/ebs-fis.md index 12b6ea507..4b78ddb24 100644 --- a//ebs/latest/userguide/ebs-fis.md +++ b//ebs/latest/userguide/ebs-fis.md @@ -5,27 +5 @@ -# Fault testing on Amazon EBS - -Use AWS Fault Injection Service and the Pause I/O action to temporarily stop I/O between an Amazon EBS volume and the instances to which it is attached to test how your workloads handle I/O interruptions. With AWS FIS, you can use controlled experiments to test your architecture and monitoring, such as Amazon CloudWatch alarms and OS timeout configurations, and improve resiliency to storage faults. - -For more information about AWS FIS, see the [_AWS Fault Injection Service User Guide_](https://docs.aws.amazon.com/fis/latest/userguide/what-is.html). - -###### Considerations - -Keep in mind the following considerations for pausing volume I/O: - - * You can pause I/O for all Amazon EBS volume types that are attached to [ instances built on the Nitro System](https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html). - - * You can pause I/O for the root volume. - - * You can pause I/O for Multi-Attach enabled volumes. If you pause I/O for a Multi-Attach enabled volume, I/O is paused between the volume and all of the instances to which it is attached. - - * To test your OS timeout configuration, set the experiment duration equal to or greater than the value specified for `nvme_core.io_timeout`. For more information, see [NVMe I/O operation timeout for Amazon EBS volumes](./timeout-nvme-ebs-volumes.html). - - * If you drive I/O to a volume that has I/O paused, the following happens: - - * The volume's status transitions to `impaired` within 120 seconds. For more information, see [Amazon EBS volume status checks](./monitoring-volume-checks.html). - - * The CloudWatch metrics for queue length (`VolumeQueueLength`) will be non-zero. Any alarms or monitoring should monitor for a non-zero queue depth. For more information see [Metrics for Amazon EBS volumes](./using_cloudwatch_ebs.html#ebs-volume-metrics). - - * The CloudWatch metrics for `VolumeReadOps` or `VolumeWriteOps` will be `0`, which indicates that the volume is no longer processing I/O. - - +Supported experimentsConsiderations @@ -32,0 +7 @@ Keep in mind the following considerations for pausing volume I/O: +# Fault testing on Amazon EBS @@ -34 +9 @@ Keep in mind the following considerations for pausing volume I/O: -###### Limitations +AWS Fault Injection Service (AWS FIS) is a fully managed service that helps you perform fault injection experiments on your AWS workloads. With EBS actions in AWS FIS, you can test how your applications respond to storage faults that can result in I/O interruptions and degraded performance on your volumes. This controlled testing environment enables you to observe how your applications respond to disruptions so you can identify weaknesses in your architecture and improve the overall resilience of your applications. Using the pause I/O action and the latency injection action, you can test your monitoring and recovery mechanisms such as Amazon CloudWatch alarms and failover workflows, and improve the resiliency of your mission-critical applications to storage faults. For more information about AWS FIS, see the [AWS Fault Injection Service User Guide](https://docs.aws.amazon.com/fis/latest/userguide/what-is.html). @@ -36 +11 @@ Keep in mind the following considerations for pausing volume I/O: -Keep in mind the following limitations for pausing volume I/O: +## Supported experiments @@ -38 +13 @@ Keep in mind the following limitations for pausing volume I/O: - * Instance store volumes are not supported. +Amazon EBS currently supports two AWS FIS fault injections: @@ -40 +15 @@ Keep in mind the following limitations for pausing volume I/O: - * Xen-based instances types are not supported. + * [Pause I/O fault injection](./ebs-fis-pause-io.html) @@ -42 +17 @@ Keep in mind the following limitations for pausing volume I/O: - * You can't pause I/O for volumes created on an Outpost, in an AWS Wavelength Zone, or in a Local Zone. + * [Latency injection](./ebs-fis-latency-injection.html) @@ -47 +22 @@ Keep in mind the following limitations for pausing volume I/O: -You can perform a basic experiment from the Amazon EC2 console, or you can perform more advanced experiments using the AWS FIS console. For more information about performing advanced experiments using the AWS FIS console, see [ Tutorials for AWS FIS](https://docs.aws.amazon.com/fis/latest/userguide/fis-tutorials.html) in the _AWS Fault Injection Service User Guide_. +## Considerations @@ -49 +24 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo -###### To perform a basic experiment using the Amazon EC2 console +The following considerations apply: @@ -51 +26 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). + * All Amazon EBS volume types are supported. Both root volumes and data volumes are supported. Instance store volumes are not supported. @@ -53 +28 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo - 2. In the navigation pane, choose **Volumes.** + * Your volumes will resume their original I/O performance once the experiment completes based on the duration. You can also stop a running experiment before it completes. Alternatively, you can create a stop condition to stop the experiment if it reaches a threshold that you define in a CloudWatch alarm. @@ -55 +30 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo - 3. Select the volume for which to pause I/O and choose **Actions** , **Fault injection** , **Pause volume I/O**. + * You can use this action with any EBS volume type attached to a Nitro-based EC2 instance. It can be used for . @@ -57 +32 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo - 4. For **Duration** , enter the duration for which to pause I/O between the volume and the instances. The field next to the Duration dropdown list shows the duration in ISO 8601 format. + * You can use AWS FIS with Multi-Attach enabled volumes. All of the attached instances are impacted. You can't select a specific volume-instance attachment for experiments. @@ -59 +34 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo - 5. In the **Service access** section, select the IAM service role for AWS FIS to assume to perform the experiment. You can use either the default role, or an existing role that you created. For more information, see [Create an IAM role for AWS FIS experiments](https://docs.aws.amazon.com/fis/latest/userguide/getting-started-iam-service-role.html). + * FIS is currently not available in Local Zones, Outposts, or Wavelength Zones. @@ -61 +36 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo - 6. Choose **Pause volume I/O**. When prompted, enter `start` in the confirmation field and choose **Start experiment**. + * You can test up to 5 volumes in the same Availability Zone simultaneously when specifying volume ARNs in the console. @@ -63 +38 @@ You can perform a basic experiment from the Amazon EC2 console, or you can perfo - 7. Monitor the progress and impact of your experiment. For more information, see [Monitoring AWS FIS](https://docs.aws.amazon.com/fis/latest/userguide/monitoring-experiments.html) in the _AWS FIS User Guide_. + * You can't use AWS FIS with volumes created on an Outpost, in an AWS Wavelength Zone, or in a Local Zone. @@ -76 +51 @@ Auto-enable I/O -EBS snapshots +Pause I/O fault injection