One of the most common reasons for system failures is changes to the underlying infrastructure. Amazon CloudTrail does a great job of recording when actions are taken but a lot of organizations don’t take advantage of it. FireHydrant now includes this data, giving you visibility into changes to your infrastructure while you’re investigating an incident.
Imagine experiencing an outage where all of the calls to a specific service are timing out in production but its health-checks are still passing. When you open an incident in FireHydrant for your production environment you’ll see that a security group was modified in the last hour, removing the rule allowing tcp/443 traffic. How about an incident where you notice that a number of instances are unexpectedly terminated? You’ll see EC2 TerminateInstance actions for each instance along with the Autoscaling group itself being scaled down by another engineer.
If you’re managing your infrastructure through code and have our GitHub integration enabled, you’ll also see that a Pull Request was merged modifying your Terraform configuration or CloudFormation templates.
FireHydrant gives you insight into what’s recently changed in your system, allowing you to mitigate and resolve incidents more quickly. Our CloudTrail integration is available today, reach out to firstname.lastname@example.org and we’ll work with you to integrate it in your incident response process.
You just got paged. Now What? Get started with FireHydrant