AWS AmazonECS documentation change
Summary
Updated FIPS endpoint configuration documentation to clarify it's set at capacity provider level rather than account level for ECS Managed Instances
Security assessment
The change clarifies how to configure FIPS endpoints for compliance purposes. This is documentation about security features (FIPS compliance) but doesn't address a specific security issue or vulnerability. It's a clarification of existing functionality.
Diff
diff --git a/AmazonECS/latest/developerguide/managed-instances-security.md b/AmazonECS/latest/developerguide/managed-instances-security.md index 5cbe0e5fd..893961e96 100644 --- a//AmazonECS/latest/developerguide/managed-instances-security.md +++ b//AmazonECS/latest/developerguide/managed-instances-security.md @@ -0,0 +1,2 @@ +[View a markdown version of this page](managed-instances-security.md) + @@ -79 +81 @@ Amazon ECS Managed Instances maintains the same compliance posture as Amazon ECS - * **FIPS endpoints** \- Amazon ECS Managed Instances respects your account-level setting for using FIPS endpoints in the AWS Regions to help achieve FedRAMP compliance. + * **FIPS endpoints** \- Amazon ECS Managed Instances supports FIPS endpoint configuration at the capacity provider level. Unlike Fargate, which uses an account-level setting, Amazon ECS Managed Instances uses a per-capacity-provider setting because FIPS is a per-instance configuration. You configure FIPS when creating or updating a capacity provider.