Monitor AWS VPC Connectivity with Python

We recently have the need to cutover our AWS Direct Connects to a different vendor. In order to carry out the change, I was tasked to find a way to monitor Direct Connect connectivities to our on premise network from our hundreds of VPCs in AWS.

After some discussion with our network engineers and security team, the solution I end up using is to deploy a single EC2 instance into each those VPCs that has a connection to VGW. We then add those instance IPs into PRTG to monitor with Ping and Http sensors.

To allow the instance to be deployed into the targeted AWS accounts, we use CloudFormation StackSet to push out a role into each of those accounts first. The role then allows the "Master Account" to have permission to create and update necessary resources within the target accounts.

The instance uses a t3.nano tier alogn with Amazon hvm Linux2 AMI (Use our own hardened AMI in my case). A simple Nginx test page is installed on the instance to allow us to monitor TCP traffics. The total running cost of the solution depends on the number of instances/VPCs you have. For example, 100 instances cost around AU$500 a month.

Yes, Lambda potentially can be cheaper, but it does not allow us to have real time monitoring as it does not support ICMP traffic. The underlaying container images for Lambda does not support that. AWS recommended way to monitor VPC connectivities is to use Ping.

The script can be easily transformed into a Lambda function and deployed with Serverless Framwork.

The script can be found in my repo.
https://github.com/tomkingchen/DirectConnectMonitor




Comments

Popular posts from this blog

Install AWS CLI on WSL Ubuntu

On Premise Mailbox user missing in Exchange Online GAL

Receive error: Target mailbox doesn't have an SMTP proxy matching '.mail.onmicrosoft.com' when move mailbox to Office 365