Update readme.MD

Author: mobri2a

README.md

@@ -16,13 +16,13 @@ chmod +x ./deployment/run-unit-tests.sh
 ## Building the customized solution
 * Configure the solution name, version number and bucket name of your target Amazon S3 distribution bucket 
 ``` 
-export DIST_OUTPUT_BUCKET_PREFIX=my-source-code-bucket-name_prefix # Prefix for the S3 bucket where customized code will reside 
-export TEMPLATE_OUTPUT_BUCKET=my-template-bucket-name # Name for the S3 bucket where the template will be located
-export SOLUTION_NAME=customizations-for-aws-control-tower # name of the solution 
-export VERSION=my-version # version number for the customized code  
+export DIST_OUTPUT_BUCKET_PREFIX=my-bucket-prefix # Prefix for the S3 bucket where customized code will be stored 
+export TEMPLATE_OUTPUT_BUCKET=my-bucket-name # Name for the S3 bucket where the template will be stored
+export SOLUTION_NAME= my-solution-name # name of the solution (e.g. customizations-for-aws-control-tower)
+export VERSION=my-version # version number for the customized code  (e.g. 2.1.0)
 export REGION=aws-region-code # the AWS region to test the solution (e.g. us-east-1)
 ``` 
-_Note:_ You would need to create one global bucket and one regional bucket. The global bucket TEMPLATE_OUTPUT_BUCKET, for example "my-bucket-name", is used to store the AWS CloudFormation template. The regional bucket <DIST_OUTPUT_BUCKET_PREFIX>-<REGION>, for example "my-bucket-name-us-east-1", is used to store your customized source code zip packages (lambda code). The solution's CloudFormation template will expect the source code to be located in a bucket matching that name. Also, the assets in bucket should be publicly accessible.
+_Note:_ You would need to create one global bucket and one regional bucket. The global bucket TEMPLATE_OUTPUT_BUCKET, for example "my-bucket-name", is used to store the AWS CloudFormation template. The regional bucket $DIST_OUTPUT_BUCKET_PREFIX-$REGION, for example "my-bucket-name-us-east-1", is used to store your customized source code zip packages (lambda code). The solution's CloudFormation template will expect the source code to be located in a bucket matching that name. Also, the assets in bucket should be publicly accessible.
 
 * Now build the distributable
 ``` 
@@ -39,7 +39,7 @@ chmod +x ./build-s3-dist.sh
 
   * Upload the customized source code zip packages to your regional bucket in the following pattern
     ``` 
-    s3://my-bucket-name-<REGION>/$SOLUTION_NAME/$VERSION/
+    s3://my-bucket-name-$REGION/$SOLUTION_NAME/$VERSION/
     ``` 
 
 ## Deploying the customized solution
@@ -52,18 +52,26 @@ The  File structure of the Customizations for AWS Control Tower solution consist
 ```
 customizations-for-aws-control-tower
 ├── deployment
-│   ├── build-s3-dist.sh                            [ shell script for packaging distribution assets ]
+│   ├── build-s3-dist.sh                            [ shell script for packaging distribution assets ]
 │   ├── run-unit-tests.sh                           [ shell script for executing unit tests ]
 │   ├── custom-control-tower-initiation.template    [ solution CloudFormation deployment template ]
-│   └── custom_control_tower_configuration          [ custom configuration examples ]
-│       └── example-configuration
+│   └── custom_control_tower_configuration          [ custom configuration examples ]
+│       └── example-configuration
 └── source  
+    ├── aws                                         [ AWS services APIs and other utils used in the solution]
     ├── bin                                         
-    │   ├── build_scripts                           [ python scripts for packaging the source code ]
-    │   └── codebuild_scripts                       [ shell and python scripts for codebuild project ]
-    ├── lib                                         [ dependencies used in the solution ]
+    │   ├── build_scripts                           [ python scripts for packaging the source code ]
+    │   └── codebuild_scripts                       [ shell and python scripts for codebuild project ]
+    ├── manifest                                    [ python code for processing manifest file]
+    ├── metrics                                     [ python code for sending anonymous solution operatioal metrics]
     ├── tests                                       [ unit tests ]
-    └── validation                                  [ shell and python scripts for validating manifest schema and cfn template]
+    ├── utils                                       [ dependencies used in the solution ]
+    ├── validation                                  [ shell and python scripts for validating manifest schema and cfn template]
+    ├── config_deployer.py                          [ Python code used by lambda to deploy configurations at solution deployment]
+    ├── lifecycle_event_handler.py                  [ Python code used by lambda to process AWS Control Tower lifecycle event]
+    ├── state_machine_handler.py                    [ Python code used by state machine to deploy SCPs and StackSets]
+    ├── state_machine_router.py                     [ Python code used by lambda to invoke state machine functions]
+    └── state_machine_trigger.py                    [ Python code used by CodePipeline to trigger state machine]
 ```
 
 Below shows the file structure of a custom configuration package which can be found in the github source code. Note that this is an example, therefore file path, folder and file names can be modified by customers to match what is defined in the manifest file.
@@ -75,7 +83,7 @@ custom_control_tower_configuration
 │   ├── create-ssm-parameter-keys-1.json   [ json file one containing input parameters used in the template file, if any. Optional ]
 │   └── create-ssm-parameter-keys-2.json   [ json file two containing input parameters used in the template file, if any. Optional ]
 ├── policies
-│   └── preventive-guardrails.json             [ json file containing service control policies (preventive guardrails). required for SCPs ] 
+│   └── preventive-guardrails.json             [ json file containing service control policies (preventive guardrails). required for SCPs ] 
 └── templates
     ├── create-ssm-parameter-keys-1.template  [ CloudFormation template one for creating ssm parameter resources. required for StackSet ] 
     └── create-ssm-parameter-keys-2.template  [ CloudFormation template two for creating ssm parameter resources. required for StackSet ] 
@@ -88,4 +96,4 @@ This solution collects anonymous operational metrics to help AWS improve the qua
 
 ## License
 
-See license [here](https://github.com/aws-solutions/aws-control-tower-customizations/blob/main/LICENSE.txt) 
+See license [here](https://github.com/aws-solutions/aws-control-tower-customizations/blob/main/LICENSE.txt)