Account Health Alert

Lambda Functions to manage AWS Health Alerts

How To Setup a CodePipeline

Input Parameter Values

CloudformationLambdaExecutionRoleArn:

Enter ARN of IAM Role for Cloudformation to create changesets and target stack. If you already created one or more CodePipeline that uses Cloudformation, this role should have been created already, so you can use the same role, 'cloudformation-lambda-execution-role'. If not, please create a role with the same name with Trust Relationships and Policy Document defined here.
CodePipelineServiceRoleArn:

Enter ARN of IAM Role for CodePipeline to be executed. If you already created one or more CodePipeline, this role should have been created already, so you can use the same role, 'AWS-CodePipeline-Service'. If not, please create a role with the same name with Trust Relationships and Policy Document defined here.
CustomAuthorizerIAMRoleName:
CustomAuthorizerLambdaName:
EncryptionLambdaName:
GitHubPersonalAccessToken:

Access Token for CodeBuild to access to the this Github repository. (See here to find how to generate the access token).
GitHubSourceRepositoryBranch: master
GitHubSourceRepositoryName: aws-services-health
GitHubSourceRepositoryOwner: SungardAS
ParameterOverrides: { "HealthLogGroupName": "/SungardAS/Alerts/Health", "SubscriptionFilterDestinationArn": "arn:aws:logs:<region>:<account>:destination:<destination_name>" }
ProjectImage: aws/codebuild/nodejs:4.3.2

After populating the const variables in test.js, run below command

$ node tests/test.js

This project is maintained by the Labs group at Sungard Availability Services