Hybrid cloud components selection - How AWS Pricing Works

Hybrid cloud components selection

Customers can choose from a range of pre-validated Outposts configurations (Figure 1) offering a mix of EC2 and EBS capacity designed to meet a variety of application needs. AWS can also work with customer to create a customized configuration designed for their unique application needs.

To consider correct configuration, make sure to verify deployment and operational parameters of the selected physical location for AWS Outpost rack installation. The following example represents a set of parameters highlighting facility, networking and power requirements needed for location validation (selected parameter: example value):

Purchase Option: All Upfront

Term: 3 Years

Max on premises power capacity: 20kVA

Max weight: 2,500lb

Networking uplink speed: 100Gbps

Number of Racks: 1

Average Power Draw per Rack: 9.34

Constraint (power draw/weight): Power Draw

Total Outpost vCPU: 480

Total Outpost Memory: 2,496GiB

In addition to minimum parameters, you should make deployment assumptions prior to any order to minimize performance and security impact on existing infrastructure landscape, deeply affecting existing cost of on-premises infrastructure (selected question: example assumption).

What is the speed of the uplink ports from your Outposts Network Devices (OND): 40 or 100Gbps

How many uplinks per Outpost Networking Device (OND) will you use to connect the AWS Outpost to your network: 4 uplinks

How will the Outpost service link (the Outpost control plane) access AWS services: Service link will access AWS over a Direct Connect public VIF

Is there a firewall between Outposts and the Internet: Yes

These assumptions together with selected components will further lead to an architecture with higher granularity of details influencing overall cost of a hybrid cloud architecture deployment (Figure 4).

Figure 5 : Hybrid cloud architecture deployment example