Add README.md and tutorial walkthrough for script-only tutorials

mwunderl · mwunderl · commit c82bb16b6510 · 2026-04-21T05:38:00.000Z
diff --git a/tuts/172-lambda-concurrency/README.md b/tuts/172-lambda-concurrency/README.md
@@ -0,0 +1,40 @@
+# Lambda Concurrency
+
+An AWS CLI tutorial that demonstrates Iam operations.
+
+## Running
+
+```bash
+bash lambda-concurrency.sh
+```
+
+To auto-run with cleanup:
+
+```bash
+echo 'y' | bash lambda-concurrency.sh
+```
+
+## What it does
+
+1. Getting account concurrency limits
+2. Setting reserved concurrency
+3. Getting function concurrency
+4. Removing reserved concurrency
+
+## Resources created
+
+- Function
+- Role
+- Function Concurrency
+
+The script prompts you to clean up resources when it finishes.
+
+## Cost
+
+Free tier eligible for most operations. Clean up resources after use to avoid charges.
+
+## Related docs
+
+- [AWS CLI iam reference](https://docs.aws.amazon.com/cli/latest/reference/iam/index.html)
+- [AWS CLI lambda reference](https://docs.aws.amazon.com/cli/latest/reference/lambda/index.html)
+
diff --git a/tuts/172-lambda-concurrency/lambda-concurrency.md b/tuts/172-lambda-concurrency/lambda-concurrency.md
@@ -0,0 +1,27 @@
+# Lambda Concurrency
+
+## Prerequisites
+
+1. AWS CLI installed and configured (`aws configure`)
+2. Appropriate IAM permissions for the AWS services used
+
+## Step 1: Getting account concurrency limits
+
+The script handles this step automatically. See `lambda-concurrency.sh` for the exact CLI commands.
+
+## Step 2: Setting reserved concurrency
+
+The script handles this step automatically. See `lambda-concurrency.sh` for the exact CLI commands.
+
+## Step 3: Getting function concurrency
+
+The script handles this step automatically. See `lambda-concurrency.sh` for the exact CLI commands.
+
+## Step 4: Removing reserved concurrency
+
+The script handles this step automatically. See `lambda-concurrency.sh` for the exact CLI commands.
+
+## Cleanup
+
+The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
+
diff --git a/tuts/175-ec2-tags/README.md b/tuts/175-ec2-tags/README.md
@@ -0,0 +1,38 @@
+# Ec2 Tags
+
+An AWS CLI tutorial that demonstrates Ec2 operations.
+
+## Running
+
+```bash
+bash ec2-tags.sh
+```
+
+To auto-run with cleanup:
+
+```bash
+echo 'y' | bash ec2-tags.sh
+```
+
+## What it does
+
+1. Adding tags
+2. Describing tags
+3. Finding resources by tag
+4. Removing a tag
+
+## Resources created
+
+- Security Group
+- Tags
+
+The script prompts you to clean up resources when it finishes.
+
+## Cost
+
+Free tier eligible for most operations. Clean up resources after use to avoid charges.
+
+## Related docs
+
+- [AWS CLI ec2 reference](https://docs.aws.amazon.com/cli/latest/reference/ec2/index.html)
+
diff --git a/tuts/175-ec2-tags/ec2-tags.md b/tuts/175-ec2-tags/ec2-tags.md
@@ -0,0 +1,27 @@
+# Ec2 Tags
+
+## Prerequisites
+
+1. AWS CLI installed and configured (`aws configure`)
+2. Appropriate IAM permissions for the AWS services used
+
+## Step 1: Adding tags
+
+The script handles this step automatically. See `ec2-tags.sh` for the exact CLI commands.
+
+## Step 2: Describing tags
+
+The script handles this step automatically. See `ec2-tags.sh` for the exact CLI commands.
+
+## Step 3: Finding resources by tag
+
+The script handles this step automatically. See `ec2-tags.sh` for the exact CLI commands.
+
+## Step 4: Removing a tag
+
+The script handles this step automatically. See `ec2-tags.sh` for the exact CLI commands.
+
+## Cleanup
+
+The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
+
diff --git a/tuts/177-lambda-destinations/README.md b/tuts/177-lambda-destinations/README.md
@@ -0,0 +1,39 @@
+# Lambda Destinations
+
+An AWS CLI tutorial that demonstrates Iam operations.
+
+## Running
+
+```bash
+bash lambda-destinations.sh
+```
+
+To auto-run with cleanup:
+
+```bash
+echo 'y' | bash lambda-destinations.sh
+```
+
+## What it does
+
+1. Creating roles and functions"; RID=$(cat /dev/urandom | tr -dc 'a-z0-9' | fold -w 8 | head -n 1); R="dest-role-$RID"; Q="dest-queue-$RID"; F="dest-func-$RID"; ROLE_ARN=$(aws iam create-role --role-name "$R" --assume-role-policy-document '{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Principal":{"Service":"lambda.amazonaws.com"},"Action":"sts:AssumeRole"}]}' --query Role.Arn --output text); aws iam attach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole; aws iam attach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/AmazonSQSFullAccess; sleep 10; QU=$(aws sqs create-queue --queue-name "$Q" --query QueueUrl --output text); QA=$(aws sqs get-queue-attributes --queue-url "$QU" --attribute-names QueueArn --query Attributes.QueueArn --output text); D=$(mktemp -d); echo "def handler(e,c): return {\"result\":\"success\"}" > "$D/i.py"; (cd "$D" && zip f.zip i.py > /dev/null); aws lambda create-function --function-name "$F" --zip-file "fileb://$D/f.zip" --handler i.handler --runtime python3.12 --role "$ROLE_ARN" --architectures x86_64 > /dev/null; aws lambda wait function-active-v2 --function-name "$F"; echo "Step 2: Configuring on-success destination"; aws lambda put-function-event-invoke-config --function-name "$F" --destination-config "{\"OnSuccess\":{\"Destination\":\"$QA\"}}" > /dev/null; echo "  On-success -> SQS queue"; echo "Step 3: Invoking async"; aws lambda invoke --function-name "$F" --invocation-type Event --cli-binary-format raw-in-base64-out --payload '{}' "$D/out.json" > /dev/null; echo "  Invoked async"; sleep 10; echo "Step 4: Checking SQS for result"; aws sqs receive-message --queue-url "$QU" --max-number-of-messages 1 --wait-time-seconds 5 --query "Messages[0].Body" --output text 2>/dev/null | python3 -c "import sys,json;d=json.loads(sys.stdin.read());print(f\"  Result: {d.get('requestPayload',{})}\n  Response: {d.get('responsePayload',{})}\")" 2>/dev/null || echo "  No message yet"; echo "Do you want to clean up? (y/n): "; read -r C; [[ "$C" =~ ^[Yy]$ ]] && { aws lambda delete-function --function-name "$F" 2>/dev/null; aws sqs delete-queue --queue-url "$QU" 2>/dev/null; aws iam detach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole 2>/dev/null; aws iam detach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/AmazonSQSFullAccess 2>/dev/null; aws iam delete-role --role-name "$R" 2>/dev/null; rm -rf "$D
+
+## Resources created
+
+- Function
+- Queue
+- Role
+- Function Event Invoke Config
+
+The script prompts you to clean up resources when it finishes.
+
+## Cost
+
+Free tier eligible for most operations. Clean up resources after use to avoid charges.
+
+## Related docs
+
+- [AWS CLI iam reference](https://docs.aws.amazon.com/cli/latest/reference/iam/index.html)
+- [AWS CLI lambda reference](https://docs.aws.amazon.com/cli/latest/reference/lambda/index.html)
+- [AWS CLI sqs reference](https://docs.aws.amazon.com/cli/latest/reference/sqs/index.html)
+
diff --git a/tuts/177-lambda-destinations/lambda-destinations.md b/tuts/177-lambda-destinations/lambda-destinations.md
@@ -0,0 +1,15 @@
+# Lambda Destinations
+
+## Prerequisites
+
+1. AWS CLI installed and configured (`aws configure`)
+2. Appropriate IAM permissions for the AWS services used
+
+## Step 1: Creating roles and functions"; RID=$(cat /dev/urandom | tr -dc 'a-z0-9' | fold -w 8 | head -n 1); R="dest-role-$RID"; Q="dest-queue-$RID"; F="dest-func-$RID"; ROLE_ARN=$(aws iam create-role --role-name "$R" --assume-role-policy-document '{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Principal":{"Service":"lambda.amazonaws.com"},"Action":"sts:AssumeRole"}]}' --query Role.Arn --output text); aws iam attach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole; aws iam attach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/AmazonSQSFullAccess; sleep 10; QU=$(aws sqs create-queue --queue-name "$Q" --query QueueUrl --output text); QA=$(aws sqs get-queue-attributes --queue-url "$QU" --attribute-names QueueArn --query Attributes.QueueArn --output text); D=$(mktemp -d); echo "def handler(e,c): return {\"result\":\"success\"}" > "$D/i.py"; (cd "$D" && zip f.zip i.py > /dev/null); aws lambda create-function --function-name "$F" --zip-file "fileb://$D/f.zip" --handler i.handler --runtime python3.12 --role "$ROLE_ARN" --architectures x86_64 > /dev/null; aws lambda wait function-active-v2 --function-name "$F"; echo "Step 2: Configuring on-success destination"; aws lambda put-function-event-invoke-config --function-name "$F" --destination-config "{\"OnSuccess\":{\"Destination\":\"$QA\"}}" > /dev/null; echo "  On-success -> SQS queue"; echo "Step 3: Invoking async"; aws lambda invoke --function-name "$F" --invocation-type Event --cli-binary-format raw-in-base64-out --payload '{}' "$D/out.json" > /dev/null; echo "  Invoked async"; sleep 10; echo "Step 4: Checking SQS for result"; aws sqs receive-message --queue-url "$QU" --max-number-of-messages 1 --wait-time-seconds 5 --query "Messages[0].Body" --output text 2>/dev/null | python3 -c "import sys,json;d=json.loads(sys.stdin.read());print(f\"  Result: {d.get('requestPayload',{})}\n  Response: {d.get('responsePayload',{})}\")" 2>/dev/null || echo "  No message yet"; echo "Do you want to clean up? (y/n): "; read -r C; [[ "$C" =~ ^[Yy]$ ]] && { aws lambda delete-function --function-name "$F" 2>/dev/null; aws sqs delete-queue --queue-url "$QU" 2>/dev/null; aws iam detach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole 2>/dev/null; aws iam detach-role-policy --role-name "$R" --policy-arn arn:aws:iam::aws:policy/AmazonSQSFullAccess 2>/dev/null; aws iam delete-role --role-name "$R" 2>/dev/null; rm -rf "$D
+
+The script handles this step automatically. See `lambda-destinations.sh` for the exact CLI commands.
+
+## Cleanup
+
+The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
+
diff --git a/tuts/178-ec2-amis/README.md b/tuts/178-ec2-amis/README.md
@@ -0,0 +1,29 @@
+# Ec2 Amis
+
+A read-only script that queries Ec2 resources and displays information.
+
+## Running
+
+```bash
+bash ec2-amis.sh
+```
+
+## What it does
+
+1. Listing Amazon Linux 2023 AMIs
+2. Listing Ubuntu AMIs
+3. Describing a specific AMI
+4. Listing your own AMIs
+
+## Resources created
+
+None — this script is read-only.
+
+## Cost
+
+No cost. This script only reads existing resources.
+
+## Related docs
+
+- [AWS CLI ec2 reference](https://docs.aws.amazon.com/cli/latest/reference/ec2/index.html)
+
diff --git a/tuts/178-ec2-amis/ec2-amis.md b/tuts/178-ec2-amis/ec2-amis.md
@@ -0,0 +1,23 @@
+# Ec2 Amis
+
+## Prerequisites
+
+1. AWS CLI installed and configured (`aws configure`)
+2. Appropriate IAM permissions for the AWS services used
+
+## Step 1: Listing Amazon Linux 2023 AMIs
+
+The script handles this step automatically. See `ec2-amis.sh` for the exact CLI commands.
+
+## Step 2: Listing Ubuntu AMIs
+
+The script handles this step automatically. See `ec2-amis.sh` for the exact CLI commands.
+
+## Step 3: Describing a specific AMI
+
+The script handles this step automatically. See `ec2-amis.sh` for the exact CLI commands.
+
+## Step 4: Listing your own AMIs
+
+The script handles this step automatically. See `ec2-amis.sh` for the exact CLI commands.
+
diff --git a/tuts/183-ec2-placement-groups/README.md b/tuts/183-ec2-placement-groups/README.md
@@ -0,0 +1,36 @@
+# Ec2 Placement Groups
+
+An AWS CLI tutorial that demonstrates Ec2 operations.
+
+## Running
+
+```bash
+bash ec2-placement-groups.sh
+```
+
+To auto-run with cleanup:
+
+```bash
+echo 'y' | bash ec2-placement-groups.sh
+```
+
+## What it does
+
+1. Creating cluster placement group
+2. Creating spread placement group
+3. Describing placement groups
+
+## Resources created
+
+- Placement Group
+
+The script prompts you to clean up resources when it finishes.
+
+## Cost
+
+Free tier eligible for most operations. Clean up resources after use to avoid charges.
+
+## Related docs
+
+- [AWS CLI ec2 reference](https://docs.aws.amazon.com/cli/latest/reference/ec2/index.html)
+
diff --git a/tuts/183-ec2-placement-groups/ec2-placement-groups.md b/tuts/183-ec2-placement-groups/ec2-placement-groups.md
@@ -0,0 +1,23 @@
+# Ec2 Placement Groups
+
+## Prerequisites
+
+1. AWS CLI installed and configured (`aws configure`)
+2. Appropriate IAM permissions for the AWS services used
+
+## Step 1: Creating cluster placement group
+
+The script handles this step automatically. See `ec2-placement-groups.sh` for the exact CLI commands.
+
+## Step 2: Creating spread placement group
+
+The script handles this step automatically. See `ec2-placement-groups.sh` for the exact CLI commands.
+
+## Step 3: Describing placement groups
+
+The script handles this step automatically. See `ec2-placement-groups.sh` for the exact CLI commands.
+
+## Cleanup
+
+The script prompts you to clean up all created resources. If you need to clean up manually, check the script log for the resource names that were created.
+
