An unexpectedly high AWS bill is a problem for both engineers and finance. Both are looking for answers as to where the new expenses came from. Which ones should be kept vs. reduced? Who is responsible for the bill? How can you get ahead of these spend increases before the bill arrives?
In this session, join Corey Quinn, Charity Majors, and Ben Hartshorne as they go through the checklist for AWS costs savings:
Tracking changes that affect costs in your environment
Setting up your architecture for proactive cost monitoring
Using Honeycomb to control for unexpected costs