AWS AmazonECS documentation change
Summary
Added a markdown link and updated FIPS endpoint configuration from account-level to capacity provider level for FedRAMP compliance
Security assessment
The change clarifies that FIPS endpoints can be configured at the capacity provider level rather than account-level, which improves security documentation but doesn't address a specific security vulnerability. This provides more granular control over FIPS compliance settings.
Diff
diff --git a/AmazonECS/latest/developerguide/ManagedInstances.md b/AmazonECS/latest/developerguide/ManagedInstances.md index d624e68ce..ccdac90fb 100644 --- a//AmazonECS/latest/developerguide/ManagedInstances.md +++ b//AmazonECS/latest/developerguide/ManagedInstances.md @@ -0,0 +1,2 @@ +[View a markdown version of this page](ManagedInstances.md) + @@ -146 +148 @@ Amazon ECS Managed Instances implements multiple layers of security to protect y -Amazon ECS Managed Instances support the same compliance programs as Amazon ECS, including PCI-DSS, HIPAA, and FedRAMP. In supported regions, Amazon ECS Managed Instances respects your account-level FIPS endpoint settings to help achieve FedRAMP compliance. +Amazon ECS Managed Instances support the same compliance programs as Amazon ECS, including PCI-DSS, HIPAA, and FedRAMP. In supported regions, you can configure FIPS endpoints at the capacity provider level to help achieve FedRAMP compliance.