AWS AmazonECS documentation change
Summary
Added KMS encryption configuration for Fargate ephemeral storage
Security assessment
Documents encryption configuration using KMS for storage security, enhancing security documentation without addressing a specific vulnerability
Diff
diff --git a/AmazonECS/latest/developerguide/create-ec2-cluster-console-v2.md b/AmazonECS/latest/developerguide/create-ec2-cluster-console-v2.md index 7266f95ed..d56f0b353 100644 --- a//AmazonECS/latest/developerguide/create-ec2-cluster-console-v2.md +++ b//AmazonECS/latest/developerguide/create-ec2-cluster-console-v2.md @@ -25 +25 @@ You can modify the following default options: -A namespace allows services that you create in the cluster can connect to the other services in the namespace without additional configuration. The default namespace is the same as the cluster name. For more information, see [Interconnect Amazon ECS services](./interconnecting-services.html). +A namespace allows services that you create in the cluster can connect to the other services in the namespace without additional configuration. For more information, see [Interconnect Amazon ECS services](./interconnecting-services.html). @@ -36,0 +37,2 @@ We recommend that you use Container Insights with enhanced observability instead + * Assign a AWS KMS key for your Fargate ephemeral storage. For information about how to create a key, see [Create a KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html) in the _AWS Key Management Service User Guide_. +