Resilience in AWS Outposts - AWS Outposts

Resilience in AWS Outposts

AWS Outposts is designed to be highly available. Outpost racks are designed with redundant power and networking equipment. For additional resilience, we recommend that you provide dual power sources and redundant network connectivity for your Outpost.

With high availability mode, AWS manages redundant capacity on the Outpost. There is capacity for each instance family held in reserve. If an unhealthy instance must be retired, the redundant capacity is brought online and added to the pool of available capacity. After the unhealthy instance returns to a healthy state, the redundant capacity is removed from the pool of available capacity and is held in reserve again. Capacity configurations that are designed for production environments operate in high availability mode by default. Capacity configurations that are designed for development and test environments might not offer high availability mode. We recommend that you use a capacity configuration that is designed for your environment.

When you create an Outpost, you select an Availability Zone from an AWS Region. This Availability Zone supports control plane operations such as responding to API calls, monitoring the Outpost, and updating the Outpost. To benefit from the resiliency provided by AWS Availability Zones, you can deploy applications on multiple Outposts, each attached to a different Availability Zone. This enables you to build additional application resilience and avoid a dependence on a single Availability Zone. For more information about AWS Regions and Availability Zones, see AWS Global Infrastructure.