Enabling high availability of Amazon EC2 instances on AWS Outposts servers (Part 3)
Compute Blog
This article (Part 3) demonstrates automating EC2 instance recovery on AWS Outposts servers using third-party storage for persistent data.
- CloudWatch monitors EC2 StatusCheckFailed_Instance metric and triggers SNS notifications
- Lambda function automatically relaunches failed instances on secondary Outposts server
- Instances connect to existing boot/data volumes on third-party storage (Dell, HPE, NetApp, Pure)
- Achieves zero RPO and RTO equal to instance launch time
- Requires two colocated Outposts servers with <5ms network latency
- Launch wizard configures iSCSI connections and generates CloudFormation templates
- Supports active-active or active-passive resilient configurations
- Enables N+1 fault tolerance for stateful workloads on-premises
This solution provides automated high availability for Outposts servers using infrastructure-as-code and third-party storage integration, reducing application downtime during hardware failures.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Aug 8
2024
2024
Enabling high availability of Amazon EC2 instances on AWS Outposts servers (Part 2)
Aug 8
2024
2024
Enabling high availability of Amazon EC2 instances on AWS Outposts servers (Part 1)
Nov 22
2024
2024
Announcing static stability for Amazon EC2 instances backed by EC2 instance store on AWS Outposts
Apr 28
2025
2025
Maintaining spare capacity during host failures on AWS Outposts with dynamic monitoring
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.