Update README.md

README.md

@@ -14,21 +14,6 @@ you! Our custom files, as well as 1Strategy LLC's, are licensed under the Apache
 
 ![ServiceArchitecture.svg](Diagrams%2FServiceArchitecture.svg)
 
-# Configure
-
-To set up the AWS access keys for your GitHub Actions workflow, you need to follow these steps:
-
-1. Create IAM User: Log in to your AWS Management Console, go to the IAM service, and create a new IAM user or use an
-   existing one. Make sure the user has the necessary permissions to deploy resources to your AWS environment.
-    - AWSCloudFormationFullAccess
-    - AmazonVPCFullAccess
-    -
-2. Generate Access Keys: After creating the IAM user, generate access keys for the user. You'll get an Access Key ID and
-   a Secret Access Key.
-3. Store Access Keys in GitHub Secrets: Go to your GitHub repository, navigate to "Settings" > "Secrets", and add the
-   Access Key ID and Secret Access Key as secrets. For example, you can name them NONPROD_AWS_ACCESS_KEY_ID and
-   NONPROD_AWS_SECRET_ACCESS_KEY.
-
 ## Actions Workflow Breakdown
 
 1. Workflow Inputs: The workflow requires various inputs, including account information, regions, instance capacities,
@@ -43,7 +28,7 @@ To set up the AWS access keys for your GitHub Actions workflow, you need to foll
     - MAGE-BUILDER: Builds and manages Amazon Machine Images (AMI) using AWS Image Builder.
     - DEPLOY: Deploys the application stack and manages auto-scaling groups.
 
-### GitHub Actions OIDC
+### GitHub Actions OIDC (actions aws setup)
 
 Create the OIDC role for the GitHub Actions workflow to assume.
 You can use the following command from the root of this repository to create the role, note that the parameters are