From 06a34b0ee0ddc9ed707b5073dfe85a0730c85ec2 Mon Sep 17 00:00:00 2001
From: Matt Conway <matt@conwaysplace.com>
Date: Tue, 10 Sep 2019 16:26:05 -0400
Subject: [PATCH] running deploy as deployer user needs the deployer specific
 role to be specified

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c459b81..5a84aff 100644
--- a/README.md
+++ b/README.md
@@ -153,7 +153,7 @@ atmos -e dev container deploy -c services <service_name>
 The atmos aws scaffold also sets up a user named _deployer_, with restricted permissions sufficient to do the deploy.  Add the [key/secret](https://github.com/simplygenius/atmos-recipes/blob/master/aws/scaffold/recipes/atmos-permissions.tf#L159) to the environment for your CI to get your CI to auto-deploy on successful build.
 
 ```
-AWS_ACCESS_KEY_ID=<deployer_key> AWS_SECRET_ACCESS_KEY=<deployer_secret> atmos -e <env_based_on_branch> container deploy -c services <service_name>
+AWS_ACCESS_KEY_ID=<deployer_key> AWS_SECRET_ACCESS_KEY=<deployer_secret> atmos -e <env_based_on_branch> container deploy -r <env>-deployer -c services <service_name>
 ```
 
 To clean it all up: