Reliability of your offerings is non-negotiable to users, and too often is siloed to the various elements of your applications and infrastructure. Achieving a customer-centric view of reliability - going beyond incident management and identifying day-to-day issues affecting the user experience - requires a holistic approach. Implementing Service Level Objectives (SLOs) and error budgeting allows you to monitor your application as a singular entity, prioritizing issues that affect the user and identifying the invisible mini-incidents that cause product abandonment and switching.
In this workshop, we will walk you through how to set up Service Level Objectives (SLOs) on your AWS infrastructure and applications to provide a hands-on experience using AWS services and Nobl9’s SLO-based reliability platform to build reliability and observability into your AWS-hosted product.
SREs, DevOps, Developers, Cloud and Migration Architects
The examples and sample code provided in this workshop are intended to be consumed as instructional content. These will help you understand how various AWS services can be architected to build a solution while demonstrating best practices along the way. These examples are not intended for use in production environments.