From 83874f0633d93259fe391248c05836b41b1f1fc6 Mon Sep 17 00:00:00 2001
From: ashishgo-aws <82972059+ashishgo-aws@users.noreply.github.com>
Date: Wed, 14 Aug 2024 10:41:32 -0700
Subject: [PATCH] =?UTF-8?q?Adding=20minor=20details=20to=20the=20build=20a?=
 =?UTF-8?q?nd=20run=20step=20within=20the=20README=20inst=E2=80=A6=20(#128?=
 =?UTF-8?q?)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

*Description of changes:*

Adding a couple of additional details to the build and run step. The
run.sh file require a few changes before it is ready to be executed and
these steps are not present in the README file.

By submitting this pull request, I confirm that you can use, modify,
copy, and redistribute this contribution, under the terms of your
choice.
---
 README.md | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index dc010ed..898e327 100644
--- a/README.md
+++ b/README.md
@@ -26,12 +26,19 @@ To experiment with the image using a vanilla Docker setup, follow these steps:
 python3 create_venvs.py
 ```
 
-3. Build the Airflow v2.9.2 Docker image using:
-
-```
-cd <amazon-mwaa-docker-images path>/images/airflow/2.9.2
-./run.sh
-```
+3. Build the Airflow v2.9.2 Docker image
+   - `cd <amazon-mwaa-docker-images path>/images/airflow/2.9.2`
+   - Update `run.sh` file with your account ID, environment name and account credentials. The permissions associated
+   with the provided credentials will be assigned to the Airflow components that would be started with the next step. 
+   So, if you receive any error message indicating lack of permissions, then try providing the permissions to the 
+   identity whose credentials were used.
+   - Create the required log groups in the dev account with the names:
+     - `{ENV_NAME}-DAGProcessing`
+     - `{ENV_NAME}-Scheduler`
+     - `{ENV_NAME}-Worker`
+     - `{ENV_NAME}-Task`
+     - `{ENV_NAME}-WebServer`
+   - `./run.sh` This will build and run all the necessary containers.
 
 Airflow should be up and running now. You can access the web server on your localhost on port 8080.