fix: use the aws iam role created for specific configs

Author: zimeg

examples/aws_lambda/aws_lambda_config.yaml

@@ -4,7 +4,7 @@ function_name: bolt_py_function
 handler: aws_lambda.handler
 description: My first lambda function
 runtime: python3.8
-# role: lambda_basic_execution
+role: bolt_python_lambda_invocation
 
 # S3 upload requires appropriate role with s3:PutObject permission
 # (ex. basic_s3_upload), a destination bucket, and the key prefix

examples/aws_lambda/aws_lambda_oauth_config.yaml

@@ -4,7 +4,6 @@ function_name: bolt_py_oauth_function
 handler: aws_lambda_oauth.handler
 description: My first lambda function
 runtime: python3.8
-# role: lambda_basic_execution
 role: bolt_python_s3_storage
 
 # S3 upload requires appropriate role with s3:PutObject permission

examples/aws_lambda/lazy_aws_lambda_config.yaml

@@ -4,9 +4,7 @@ function_name: bolt_py_function
 handler: lazy_aws_lambda.handler
 description: My first lambda function
 runtime: python3.8
-# role: lambda_basic_execution
-# Have lambda:InvokeFunction & lambda:GetFunction in the allowed actions
-role: bolt_python_lambda_invocation 
+role: bolt_python_lambda_invocation
 
 # S3 upload requires appropriate role with s3:PutObject permission
 # (ex. basic_s3_upload), a destination bucket, and the key prefix