AWS AmazonECS documentation change
Summary
Fixed URL formatting in blog link reference
Security assessment
The change only corrects a URL path (added double slash in blog URL). No security content modification or vulnerability addressed.
Diff
diff --git a/AmazonECS/latest/developerguide/secrets-envvar-secrets-manager.md b/AmazonECS/latest/developerguide/secrets-envvar-secrets-manager.md index abb9352a5..cbe67ca6b 100644 --- a//AmazonECS/latest/developerguide/secrets-envvar-secrets-manager.md +++ b//AmazonECS/latest/developerguide/secrets-envvar-secrets-manager.md @@ -29 +29 @@ To inject the full contents of a secret as an environment variable or to inject - * Use interface VPC endpoints to enhance security controls and connect to Secrets Manager through a private subnet. You must create the interface VPC endpoints for Secrets Manager. For information about the VPC endpoint, see [Create VPC endpoints](https://docs.aws.amazon.com/secretsmanager/latest/userguide/setup-create-vpc.html) in the _AWS Secrets Manager User Guide_. For more information about using Secrets Manager and Amazon VPC, see [How to connect to Secrets Manager service within a Amazon VPC](https://aws.amazon.com/blogs/security/how-to-connect-to-aws-secrets-manager-service-within-a-virtual-private-cloud/). + * Use interface VPC endpoints to enhance security controls and connect to Secrets Manager through a private subnet. You must create the interface VPC endpoints for Secrets Manager. For information about the VPC endpoint, see [Create VPC endpoints](https://docs.aws.amazon.com/secretsmanager/latest/userguide/setup-create-vpc.html) in the _AWS Secrets Manager User Guide_. For more information about using Secrets Manager and Amazon VPC, see [How to connect to Secrets Manager service within a Amazon VPC](https://aws.amazon.com/blogs//security/how-to-connect-to-aws-secrets-manager-service-within-a-virtual-private-cloud/).