VMBot

AWS Lambda function to perform various automated tasks in response to EC2 lifecycle events.

This is useful in automation scenarios such as EC2 state changes in response to Auto-Scale Group events or any scenario where EC2 state changes may happen independent of any explicit infrastructure configuration changes.

⭐ I appreciate your star, it helps me decide to which OSS projects I should allocate my spare time.

Intro

VMBot is a Lambda function that should be deployed to an AWS environment and configured to respond to EC2 lifecycle events using CloudWatch Events Rules.

EC2 Lifecycle Events

VMBot understands the following three lifecycle event states:

• running - whenever an EC2 instance enters the running state and is ready to operate
• stopping - whenever an EC2 instance is about to stop or hibernate
• shutting-down - whwnever an EC2 instance is shutting down in preparation for termination

When VMBot receives an event for one of these EC2 state transitions, it will read the Tags for that EC2 instance and if it finds any matching Trigger Tags, it will perform actions as prescribed by the corresponding Tag value.

Deploy VMBot Using Terraform

To help simplify the deployment and configuration of VMBot into your own environment, a Terraform Module is provided here which you is parameterized to suit most common deployment scenarios or you can further customize to suit your own needs.

Trigger Tags and Actions

For this first release, VMBot supports Route 53-related Trigger Tags and Actions.

• vmbot:r53 - dynamically create Route 53 records for the associated EC2 instance (details)
• vmbot:r53-routing - supplement the vmbot:r53 Trigger with Route53 Routing policies
• vmbot:r53-health - create Route 53 Health Checks
• vmbot:eip - dynamically assign an EIP to the target EC2 instance from a pool of existing EIPs

More details and documentation on how to use the Tags can be found here.