From 88095576d745ec258376ed074c663a7f63229e3d Mon Sep 17 00:00:00 2001 From: Nicolas De Loof Date: Mon, 18 Jan 2021 09:57:16 +0100 Subject: [PATCH] Fix `docker secret` command documentation on ECS context Signed-off-by: Nicolas De Loof --- cloud/ecs-integration.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/cloud/ecs-integration.md b/cloud/ecs-integration.md index 2b4696b754..1bb9f320cf 100644 --- a/cloud/ecs-integration.md +++ b/cloud/ecs-integration.md @@ -196,8 +196,19 @@ The Docker Compose CLI automatically configures authorization so you can pull pr For your convenience, the Docker Compose CLI offers the `docker secret` command, so you can manage secrets created on AWS SMS without having to install the AWS CLI. +First, create `token.json` file to define your DockerHub username and access token. +See [this document](https://docs.docker.com/docker-hub/access-tokens/) on generating managing access tokens: +```json +{ + "username":"DockerHubUserName", + "password":"DockerHubAccessToken" +} +``` + +The you can create a secret from this file using `docker secret`: + ```console -docker secret create dockerhubAccessToken --username --password +docker secret create dockerhubAccessToken token.json arn:aws:secretsmanager:eu-west-3:12345:secret:DockerHubAccessToken ```