From f47d54d7b7ec88f922dbca1084076d2b5fb2dfd3 Mon Sep 17 00:00:00 2001 From: Sunny Date: Wed, 16 Sep 2020 00:57:33 +0900 Subject: [PATCH] Update ecs-integration.md change 'x-asw-keys' to 'x-aws-keys' --- engine/context/ecs-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/engine/context/ecs-integration.md b/engine/context/ecs-integration.md index b4d9d2941b..e6ae56c162 100644 --- a/engine/context/ecs-integration.md +++ b/engine/context/ecs-integration.md @@ -147,7 +147,7 @@ Secrets will be available at runtime for your service as a plain text file `/run The AWS Secrets Manager allows you to store sensitive data either as a plain text (like Docker secret does), or as a hierarchical JSON document. You can -use the latter with ECS integration by using custom field `x-asw-keys` to +use the latter with ECS integration by using custom field `x-aws-keys` to define which entries in the JSON document to bind as a secret in your service container.