DRHCOPS05-BP02 Understand monitoring requirements in your Outposts

Focus on similar observability and alerting as in an Availability Zone. In addition, add alerts for added responsibility such as security, networking, and capacity.

Desired outcome: Implement comprehensive monitoring for AWS Outposts workloads that aligns with the Availability Zone structure and accounts for the shared responsibility model.

Benefits of establishing this best practice: Enables end-to-end visibility, accurate issue detection, and targeted troubleshooting across cloud and on-premises components, improving operational efficiency.

Level of risk exposed if this best practice is not established: High

Implementation guidance

Outposts have an updated shared responsibility model, as the hardware is not within an AWS-owned facility. As a result of this model, customers take on additional ownership of network, capacity, and security management, and they work with AWS in collaboration for any hardware maintenance. Set up specific metrics for Outposts at infrastructure and application layers, and provide visibility into AWS Health events.

Outposts shared responsibility model

Set up CloudWatch metrics, and enable cross-account observability where possible. Set up metrics to understand your connected status to the Region and traffic in and out. Implement capacity monitoring and follow N+1 capacity guidance which means you provision additional capacity for each instance family for redundant hardware. to follow N+1 guidance. Consider VPC Flow Logs and ELB access logs. If further detail is required, AWS X-Ray is an additional option for a complete view of requests across your applications.

Resources