unordered list bullets and trailing whitespace

Author: mwunderl

tuts/001-lightsail-gs/README.md

@@ -8,8 +8,8 @@ You can either run the automated script `lightsail-gs.sh` to execute all operati
 
 The script creates the following AWS resources in order:
 
-• Lightsail instance (nano_3_0 bundle with Amazon Linux 2023)
-• Lightsail disk (8 GB block storage disk)
-• Lightsail instance snapshot (backup of the instance)
+- Lightsail instance (nano_3_0 bundle with Amazon Linux 2023)
+- Lightsail disk (8 GB block storage disk)
+- Lightsail instance snapshot (backup of the instance)
 
 The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.

tuts/002-vpc-gs/README.md

@@ -8,21 +8,21 @@ You can either run the automated script `vpc-gs.sh` to execute all operations au
 
 The script creates the following AWS resources in order:
 
-• EC2 VPC (10.0.0.0/16 CIDR block with DNS support and hostnames enabled)
-• EC2 subnet (public subnet in AZ1 - 10.0.0.0/24)
-• EC2 subnet (public subnet in AZ2 - 10.0.1.0/24)
-• EC2 subnet (private subnet in AZ1 - 10.0.2.0/24)
-• EC2 subnet (private subnet in AZ2 - 10.0.3.0/24)
-• EC2 internet gateway (for public internet access)
-• EC2 route table (public route table with internet gateway route)
-• EC2 route table association (public subnet AZ1 to public route table)
-• EC2 route table association (public subnet AZ2 to public route table)
-• EC2 route table (private route table)
-• EC2 route table association (private subnet AZ1 to private route table)
-• EC2 route table association (private subnet AZ2 to private route table)
-• EC2 elastic IP (for NAT gateway)
-• EC2 NAT gateway (in public subnet AZ1 for private subnet internet access)
-• EC2 security group (web server security group allowing HTTP/HTTPS)
-• EC2 security group (database security group allowing MySQL from web servers)
+- EC2 VPC (10.0.0.0/16 CIDR block with DNS support and hostnames enabled)
+- EC2 subnet (public subnet in AZ1 - 10.0.0.0/24)
+- EC2 subnet (public subnet in AZ2 - 10.0.1.0/24)
+- EC2 subnet (private subnet in AZ1 - 10.0.2.0/24)
+- EC2 subnet (private subnet in AZ2 - 10.0.3.0/24)
+- EC2 internet gateway (for public internet access)
+- EC2 route table (public route table with internet gateway route)
+- EC2 route table association (public subnet AZ1 to public route table)
+- EC2 route table association (public subnet AZ2 to public route table)
+- EC2 route table (private route table)
+- EC2 route table association (private subnet AZ1 to private route table)
+- EC2 route table association (private subnet AZ2 to private route table)
+- EC2 elastic IP (for NAT gateway)
+- EC2 NAT gateway (in public subnet AZ1 for private subnet internet access)
+- EC2 security group (web server security group allowing HTTP/HTTPS)
+- EC2 security group (database security group allowing MySQL from web servers)
 
 The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.

tuts/003-s3-gettingstarted/README.md

@@ -8,14 +8,14 @@ You can either run the automated script `s3-gettingstarted.sh` to execute all op
 
 The script creates the following AWS resources in order:
 
-• S3 bucket (primary bucket for tutorial)
-• S3 bucket (secondary bucket for cross-region replication)
-• S3 public access block configuration
-• S3 bucket versioning configuration
-• S3 bucket encryption configuration
-• S3 object (sample text file)
-• S3 object (sample image file)
-• S3 object (sample document file)
-• S3 bucket tagging configuration
+- S3 bucket (primary bucket for tutorial)
+- S3 bucket (secondary bucket for cross-region replication)
+- S3 public access block configuration
+- S3 bucket versioning configuration
+- S3 bucket encryption configuration
+- S3 object (sample text file)
+- S3 object (sample image file)
+- S3 object (sample document file)
+- S3 bucket tagging configuration
 
 The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.

tuts/004-cloudmap-custom-attributes/README.md

@@ -8,22 +8,22 @@ You can either run the automated script `cloudmap-custom-attributes.sh` to execu
 
 The script creates the following AWS resources in order:
 
-• Service Discovery http namespace
-• Service Discovery http namespace (b)
-• DynamoDB table
-• Service Discovery service
-• Service Discovery instance
-• Service Discovery instance (b)
-• IAM role
-• IAM policy
-• IAM role policy
-• IAM role policy (b)
-• Service Discovery service (b)
-• Lambda function
-• Service Discovery instance (c)
-• Service Discovery instance (d)
-• Lambda function (b)
-• Service Discovery instance (e)
-• Service Discovery instance (f)
+- Service Discovery http namespace
+- Service Discovery http namespace (b)
+- DynamoDB table
+- Service Discovery service
+- Service Discovery instance
+- Service Discovery instance (b)
+- IAM role
+- IAM policy
+- IAM role policy
+- IAM role policy (b)
+- Service Discovery service (b)
+- Lambda function
+- Service Discovery instance (c)
+- Service Discovery instance (d)
+- Lambda function (b)
+- Service Discovery instance (e)
+- Service Discovery instance (f)
 
 The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.

tuts/004-cloudmap-custom-attributes/cloudmap-custom-attributes.md

@@ -203,38 +203,38 @@ import random
 def lambda_handler(event, context):
     try:
         serviceclient = boto3.client('servicediscovery')
-        
+
         response = serviceclient.discover_instances(
             NamespaceName='cloudmap-tutorial',
             ServiceName='data-service')
-        
+
         if not response.get("Instances"):
             return {
                 'statusCode': 500,
                 'body': json.dumps({"error": "No instances found"})
             }
-            
+
         tablename = response["Instances"][0]["Attributes"].get("tablename")
         if not tablename:
             return {
                 'statusCode': 500,
                 'body': json.dumps({"error": "Table name attribute not found"})
             }
-           
+
         dynamodbclient = boto3.resource('dynamodb')
-           
+
         table = dynamodbclient.Table(tablename)
-        
+
         # Validate input
         if not isinstance(event, str):
             return {
                 'statusCode': 400,
                 'body': json.dumps({"error": "Input must be a string"})
             }
-           
+
         response = table.put_item(
             Item={ 'id': str(random.randint(1,100)), 'todo': event })
-           
+
         return {
             'statusCode': 200,
             'body': json.dumps(response)
@@ -318,32 +318,32 @@ def lambda_handler(event, context):
         serviceclient = boto3.client('servicediscovery')
 
         response = serviceclient.discover_instances(
-            NamespaceName='cloudmap-tutorial', 
+            NamespaceName='cloudmap-tutorial',
             ServiceName='data-service')
-        
+
         if not response.get("Instances"):
             return {
                 'statusCode': 500,
                 'body': json.dumps({"error": "No instances found"})
             }
-            
+
         tablename = response["Instances"][0]["Attributes"].get("tablename")
         if not tablename:
             return {
                 'statusCode': 500,
                 'body': json.dumps({"error": "Table name attribute not found"})
             }
-           
+
         dynamodbclient = boto3.resource('dynamodb')
-           
+
         table = dynamodbclient.Table(tablename)
-        
+
         # Use pagination for larger tables
         response = table.scan(
             Select='ALL_ATTRIBUTES',
             Limit=50  # Limit results for demonstration purposes
         )
-        
+
         # For production, you would implement pagination like this:
         # items = []
         # while 'LastEvaluatedKey' in response:
@@ -417,33 +417,33 @@ try:
 
     print("Discovering write function...")
     response = serviceclient.discover_instances(
-        NamespaceName='cloudmap-tutorial', 
-        ServiceName='app-service', 
+        NamespaceName='cloudmap-tutorial',
+        ServiceName='app-service',
         QueryParameters={ 'action': 'write' }
     )
 
     if not response.get("Instances"):
         print("Error: No instances found")
         exit(1)
-        
+
     functionname = response["Instances"][0]["Attributes"].get("functionname")
     if not functionname:
         print("Error: Function name attribute not found")
         exit(1)
-        
+
     print(f"Found function: {functionname}")
 
     lambdaclient = boto3.client('lambda')
 
     print("Invoking Lambda function...")
     resp = lambdaclient.invoke(
-        FunctionName=functionname, 
+        FunctionName=functionname,
         Payload='"This is a test data"'
     )
 
     payload = resp["Payload"].read()
     print(f"Response: {payload.decode('utf-8')}")
-    
+
 except Exception as e:
     print(f"Error: {str(e)}")
 EOF
@@ -463,33 +463,33 @@ try:
 
     print("Discovering read function...")
     response = serviceclient.discover_instances(
-        NamespaceName='cloudmap-tutorial', 
-        ServiceName='app-service', 
+        NamespaceName='cloudmap-tutorial',
+        ServiceName='app-service',
         QueryParameters={ 'action': 'read' }
     )
 
     if not response.get("Instances"):
         print("Error: No instances found")
         exit(1)
-        
+
     functionname = response["Instances"][0]["Attributes"].get("functionname")
     if not functionname:
         print("Error: Function name attribute not found")
         exit(1)
-        
+
     print(f"Found function: {functionname}")
 
     lambdaclient = boto3.client('lambda')
 
     print("Invoking Lambda function...")
     resp = lambdaclient.invoke(
-        FunctionName=functionname, 
+        FunctionName=functionname,
         InvocationType='RequestResponse'
     )
 
     payload = resp["Payload"].read()
     print(f"Response: {payload.decode('utf-8')}")
-    
+
 except Exception as e:
     print(f"Error: {str(e)}")
 EOF

tuts/005-cloudfront-gettingstarted/README.md

@@ -8,8 +8,8 @@ You can either run the automated script `cloudfront-gettingstarted.sh` to execut
 
 The script creates the following AWS resources in order:
 
-• CloudFront origin access control
-• CloudFront distribution
-• S3 bucket policy
+- CloudFront origin access control
+- CloudFront distribution
+- S3 bucket policy
 
 The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.

tuts/005-cloudfront-gettingstarted/cloudfront-gettingstarted.md

@@ -4,14 +4,14 @@ This tutorial shows you how to use the AWS CLI to set up a basic CloudFront dist
 
 ## Topics
 
-* [Prerequisites](#prerequisites)
-* [Create an Amazon S3 bucket](#create-an-amazon-s3-bucket)
-* [Upload content to the bucket](#upload-content-to-the-bucket)
-* [Create a CloudFront distribution with OAC](#create-a-cloudfront-distribution-with-oac)
-* [Access your content through CloudFront](#access-your-content-through-cloudfront)
-* [Clean up resources](#clean-up-resources)
-* [Going to production](#going-to-production)
-* [Next steps](#next-steps)
+- [Prerequisites](#prerequisites)
+- [Create an Amazon S3 bucket](#create-an-amazon-s3-bucket)
+- [Upload content to the bucket](#upload-content-to-the-bucket)
+- [Create a CloudFront distribution with OAC](#create-a-cloudfront-distribution-with-oac)
+- [Access your content through CloudFront](#access-your-content-through-cloudfront)
+- [Clean up resources](#clean-up-resources)
+- [Going to production](#going-to-production)
+- [Next steps](#next-steps)
 
 ## Prerequisites
 

tuts/007-chimesdk-routingcalls/README.md

@@ -8,12 +8,12 @@ You can either run the automated script `chimesdk-routingcalls.sh` to execute al
 
 The script creates the following AWS resources in order:
 
-• IAM role
-• IAM role policy
-• Lambda function
-• Lambda function (b)
-• Chime SDK Voice sip media application
-• Chime SDK Voice sip media application (b)
-• Chime SDK Voice sip rule
+- IAM role
+- IAM role policy
+- Lambda function
+- Lambda function (b)
+- Chime SDK Voice sip media application
+- Chime SDK Voice sip media application (b)
+- Chime SDK Voice sip rule
 
 The script prompts you to clean up resources when you run it, including if there's an error part way through. If you need to clean up resources later, you can use the script log as a reference point for which resources were created.

tuts/007-chimesdk-routingcalls/chimesdk-routingcalls.md

@@ -136,7 +136,7 @@ mkdir -p lambda
 cat > lambda/index.js << EOF
 exports.handler = async (event) => {
   console.log('Received event:', JSON.stringify(event, null, 2));
-  
+
   // Simple call handling logic
   const response = {
     SchemaVersion: '1.0',
@@ -157,7 +157,7 @@ exports.handler = async (event) => {
       }
     ]
   };
-  
+
   return response;
 };
 EOF
@@ -289,7 +289,7 @@ First, create a backup Lambda function in the same region.
 cat > lambda/backup-index.js << EOF
 exports.handler = async (event) => {
   console.log('Received event in backup handler:', JSON.stringify(event, null, 2));
-  
+
   // Simple call handling logic for backup
   const response = {
     SchemaVersion: '1.0',
@@ -310,7 +310,7 @@ exports.handler = async (event) => {
       }
     ]
   };
-  
+
   return response;
 };
 EOF