AWS outpost is a fully managed service that extends AWS infrastructure, services, interfaces & tools to the customer premises. This enables customers to build applications using local storage & compute instances and tools, interfaces & services available in AWS region. AWS outpost will be primarily used where there are low latency requirements or local data processing needs.
Instances in the outpost subnet communicate with other instances in the AWS region using private IP addresses all within the same VPC.
Resources on outpost include EC2 instances, EBs volumes, ECS clusters, EKS nodes, EMR clusters, RDS DB instances, App Mesh Envoy Proxy.
Fully integrated & fully managed AWS infrastructure on-premises
Built on the security, performance & power of Nitro systems (EC2 instances)
Offers the same APIs & functionality as available in public AWS regions
Automatically monitored, updated & patched as part of AWS regions
It is composed of modular units to enable fast & easy maintenance (upgrade/replacements)
Requires single point of support (as AWS)
Network connection from Outposts to AWS region
AWS Direct Connect
VPN
Local Gateway: Enables communication between your Outpost (i.e. AWS service) & your on-premise network
Customer owned IP address pool: During installation AWS creates customer owned IP address pool as per your network info provided (CIDR block must be a minimum of /26)
Routing: By default, Outpost inherits VPC route table, however you can customize it for Outpost subnet
No comments:
Post a Comment