Metadata is mostly for organizing and presenting Parameters in a better way when using CloudFormation in the AWS Web UI.
These are the input parameters for this template. All of these parameters must be supplied for this template to be deployed.
The S3 bucket name where the Lambda functions live. This is used to create an IAM access policy to permit the application EC2 instances access to the S3 bucket.
S3 path to the zip file containing the code.
These are all of the resources deployed by this stack.
This function will tag any EC2 instances created via OpsWorks with Tag data from the custom JSON on the parent OpsWorks stack.
Be sure to update the handler with the correct file name and function name!
This 'resource' calls a Lambda function to simply sleep for 30 seconds. This ensures that the LambdaExecutionRole has finished fully being created so that we can then create the lambda function itself.
Create a CloudWatch Log Group for this Lambda function to log to. This allows us to set the retention timeframe.
This is the IAM role that will be used by Lambda when trying to execute this function. Anything the lambda function needs to do with AWS needs to be allowed in here.
Let this Lambda fn create a log group if needed
Let this Lambda fn write logs to its own group
Let this Lambda fn update route53 entries
Let this Lambda fn read EC2 Tags
This creates a CloudWatch Event Rule to listen for ec2:RunInstance events and then invoke our lambda function.
This allows SNS to invoke this lambda function
Output values that can be viewed from the AWS CloudFormation console.
Lambda Function CloudFormation Deployment
This CloudFormation template will deploy a Lambda functions to enrich CloudWatch Alarms.