AWS Security ChangesHomeSearch

AWS AmazonECS documentation change

Service: AmazonECS · 2025-03-26 · Documentation low

File: AmazonECS/latest/developerguide/fault-injection.md

Summary

Updated phrasing from third-person to second-person and fixed 'thenew' typo

Security assessment

Grammatical improvements and typo fixes in existing fault injection documentation. No security context added or modified.

Diff

diff --git a/AmazonECS/latest/developerguide/fault-injection.md b/AmazonECS/latest/developerguide/fault-injection.md
index 1a260062b..75588a4c1 100644
--- a/AmazonECS/latest/developerguide/fault-injection.md
+++ b/AmazonECS/latest/developerguide/fault-injection.md
@@ -9 +9 @@ Customers can utilize fault injection with Amazon ECS on both Amazon EC2 and Far
-When fault injection is enabled, the Amazon ECS container agent allows tasks access to new fault injection endpoints. Customers must opt-in in order to use fault injection by adding the optional `enableFaultInjection` parameter to their task definition and setting the value to `true`. The default value is `false`. 
+When fault injection is enabled, the Amazon ECS container agent allows tasks access to new fault injection endpoints. You need to opt-in in order to use fault injection by setting the `enableFaultInjection` task definition parameter value to `true`. The default value is `false`. 
@@ -29 +29 @@ You'll need to enable the feature for testing in the AWS Fault Injection Service
-Customers who aren't using the new Amazon ECS optimized AMIs or are using custom AMIs need to have the following dependencies installed to use the fault injection feature:
+If you don't use thenew Amazon ECS optimized AMIs, or have a custom AMI, install the following dependencies: