{"push_id":794809714,"size":2,"distinct_size":2,"ref":"refs/heads/djcp-nat-instance-monitoring","head":"33f53c62ecd685a93d5527cb2a80b20b13af81d2","before":"a85ec7a0ab791326600e160e6765f92d331699ea","commits":[{"sha":"15cddb85e439c91acb6faf5032dc6684f0e9e243","author":{"email":"2591e5f46f28d303f9dc027d475a5c60d8dea17a@collispuro.net","name":"Dan Collis-Puro"},"message":"Cloudwatch status alarms for the NAT instance\n\nIncludes:\n\n* Create the SNS topic with the same name as the topic created by the\n  chef recipes\n* Hook an aggressive alarm onto the auto-created status checks to ensure\n  we know if a NAT instance becomes unavailable\n* Modify the VPC cfn template to accept an SNS topic name.","distinct":true,"url":"https://api.github.com/repos/harvard-dce/mh-opsworks/commits/15cddb85e439c91acb6faf5032dc6684f0e9e243"},{"sha":"33f53c62ecd685a93d5527cb2a80b20b13af81d2","author":{"email":"2591e5f46f28d303f9dc027d475a5c60d8dea17a@collispuro.net","name":"Dan Collis-Puro"},"message":"Ensure every layer gets the custom server security group.\n\nScope finding security groups only within the specific VPC.","distinct":true,"url":"https://api.github.com/repos/harvard-dce/mh-opsworks/commits/33f53c62ecd685a93d5527cb2a80b20b13af81d2"}]}