리전으로 버스트: AWS Outposts 워크로드를 Amazon EC2로 오버플로우

AWS Outposts brings AWS infrastructure into your data center, giving on-premises workloads the low latency and data locality they need. But unlike the AWS Region, an Outposts rack has a fixed amount of compute. When your workload needs more instances than the rack can provide, you have two options: drop requests, or overflow them somewhere with room to grow. This post shows you how to automate the second option.

You build a Burst to Region pattern that detects capacity constraints on your Outpost, launches Amazon Elastic Compute Cloud (Amazon EC2) instances in the parent Region, gradually shifts traffic to them, and returns traffic to local instances once capacity recovers. To implement this pattern you configure Amazon CloudWatch , Amazon Simple Notification Service (Amazon SNS), AWS Lambda , Amazon EC2 Auto Scaling , Elastic Load Balancing ( Application Load Balancer ), and Amazon EventBridge . You trade a moderate latency increase for continued availability during capacity events.

This pattern assumes your Outposts workload scales out through Amazon EC2 Auto Scaling. Burst to Region reacts to instance-capacity exhaustion on the rack. It engages when your workload tries to launch more instances than the available Outpost capacity supports. If your fleet is fixed size and degrades under load without scaling out, the capacity alarm never fires and overflow never triggers. For those workloads, monitor per-instance saturation (CPU, latency) separately. Good candidates prefer local capacity but can tolerate Region latency under pressure.

If your application runs on Outposts for proximity yet degrades gracefully when some traffic takes the longer path to the Region, it fits this pattern. Examples include: Poor candidates cannot absorb any added latency or must stay on the Outpost. Avoid this pattern for: The core tradeoff is explicit. During capacity events, you accept moderately higher latency to maintain availability. If your workload cannot tolerate any latency increase, keep it pinned to Outposts and reserve capacity through other means, such as Capacity Reservations .