Deep dive on hybrid cloud use cases with Outposts
summary
Shows how AWS Outposts ships a managed rack or 1U/2U server into a customer data center, with typical lead time six to eight weeks and capacity commitments of 1‑, 3‑ or 5‑year terms. Covers anchoring an Outpost to a single AZ, using a local gateway and service link (keep <150 ms control latency), network options 1/10/40 G, ACE racks every ~4th rack and scale to ~96 racks. Explains EBS boot persistence on racks versus ephemeral instance store on servers, S3 Outposts access limits, encryption and the Nitro key destroy mechanism.
AI-written summary · about
chapters (24)
- 0:00Introduction to Outposts
- 3:02What is AWS Outposts
- 4:33Use cases for Outposts
- 6:03Shared responsibility model
- 7:27Potential failure scenarios
- 9:21Outpost resilience and redundancy
- 11:54Multi-region Outpost design
- 13:01Outposts and VPC integration
- 15:16EC2 instance storage on Outposts
- 17:48Ordering and configuring Outposts
- 20:16Local services on Outposts
- 21:41Lead time and hardware setup
- 22:46Outpost management and support
- 23:49Outpost billing and ROI
- 26:44Data transfer and connectivity
- 28:09Backup solutions for Outposts
- 28:51Windows AMI updates on Outposts
- 30:54Direct Connect and service link
- 31:20Multiple Outposts in AZs
- 34:22Outpost failure impact
- 35:50Architecting for failure
- 36:10Running RDS on Outposts
- 37:13Bandwidth requirements
- 38:20Q&A and closing remarks
related talks
49mAWS secure hybrid edge services with AWS Outposts
21mAWS On Air ft. Outposts 1U & 2U Server
29mReinventing hybrid: Extending AWS to where customers need it
39mHow SBB brings cloud to on-prem & runs critical apps on AWS Outpost
29mAccelerate Innovation with Hybrid Capabilities and Infrastructures
53mKeep Calm & Run on AWS: Compliance While Keeping Your Stack
32mReinventing hybrid services: In-depth customer profiles
58mTransform your business with the VMware & AWS hybrid cloud