add IAM blog on the README (#25)

* add IAM blog on the README

* Update preview.yml

* Update preview.yml

* Update integration-test.yml

* Update cdk.yml

* Update integration-test.yml

* Update cdk.yml

* Update integration-test.yml

* Update preview.yml

* Update preview.yml

* Update preview.yml

Author: HarshCasper

.github/workflows/cdk.yml

@@ -33,7 +33,7 @@ jobs:
           cdklocal --version
 
       - name: Start LocalStack
-        uses: LocalStack/setup-localstack@v0.2.3
+        uses: LocalStack/setup-localstack@main
         with:
           image-tag: 'latest'
           use-pro: 'true'
@@ -88,7 +88,7 @@ jobs:
 
       - name: Upload the Diagnostic Report
         if: failure()
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: diagnose.json.gz
           path: ./diagnose.json.gz

.github/workflows/integration-test.yml

@@ -99,7 +99,7 @@ jobs:
 
       - name: Upload the Diagnostic Report
         if: failure()
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: diagnose.json.gz
           path: ./diagnose.json.gz

.github/workflows/preview.yml

@@ -17,7 +17,7 @@ jobs:
         with:
           node-version: 20
       - name: LocalStack Preview
-        uses: LocalStack/setup-localstack@v0.2.3
+        uses: LocalStack/setup-localstack@debug-action
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           state-backend: ephemeral
@@ -31,4 +31,4 @@ jobs:
             distributionId=$(awslocal cloudfront list-distributions | jq -r '.DistributionList.Items[0].Id');
             echo LS_PREVIEW_URL=$AWS_ENDPOINT_URL/cloudfront/$distributionId/ >> $GITHUB_ENV;
         env:
-          LOCALSTACK_API_KEY: ${{ secrets.LOCALSTACK_API_KEY }}
+          LOCALSTACK_AUTH_TOKEN: ${{ secrets.LOCALSTACK_AUTH_TOKEN }}

README.md

@@ -172,7 +172,9 @@ Toggle **Enforce IAM Policies** to enable strict IAM enforcement. For demo purpo
 
 Engage with the application or run tests to generate a policy stream for various services. During this process, you may notice some **IAM Violations**. These are intentionally included to demonstrate how the IAM Policy Stream can be used to test policies in a secure developer setting, helping to identify and resolve missing policies to ensure everything works in production environments.
 
-Find the missing policy statements and fix the IAM Policy on the [IAM Resource Browser](https://app.localstack.cloud/inst/default/resources/iam/roles) (for `SubmitQuizRole`) or patch it locally and update the policy using AWS CLI.
+Find the missing policy statements and fix the IAM Policy on the [IAM Resource Browser](https://app.localstack.cloud/inst/default/resources/iam/roles) (for `SubmitQuizRole`) or patch it locally and update the policy using AWS CLI. 
+
+Here is a [tutorial](https://blog.localstack.cloud/generating-testing-iam-policies-locally-with-localstack/) showcasing how you can do the above!
 
 ## Chaos Engineering