AWS Shapes Mapping Updated

Effective integration with public clouds is one of the key pillars of EPAM Cloud. We regularly review the tools used within the hybridization, and update them to be sure that they meet the latest performance, security, and cost recommendations.

EPAM Orchestrator supports referencing instance shapes/types with a set of aliases. One alias references similar capacities across different clouds. Thus, the user operates only with EPAM Cloud shape names, and Orchestrator automatically matches the selection to the respective instance type in the specified cloud provider.

We are glad to announce, that within the scope of regular review, the shapes/instance types mapping for AWS was updated on December 23. The new mapping reflects the latest updates in AWS instance type libraries, and matches the latest AWS recommendations.

The table below provides the details on the new mapping:

EPAM Cloud Shapes CPU RAM, GB AWS Instance Type by Regions
Zones Set 1 Zones Set 2
MICRO 1 0.5 t3.nano t3.nano
MINI 1 1 t3.micro t3.micro
SMALL 1 2 t3.small t3.small
MEDIUM 2 4 t3.medium t3.medium
LARGE 2 8 t3.large t3.large
XL 4 7.5 m5a.large m5.large
2XL 4 16 r5a.large r5.large
3XL 8 15 m5a.xlarge m5.xlarge
4XL 6 23 r5a.xlarge r5.xlarge
5XL 8 32 m5a.2xlarge m5.2xlarge
6XL 8 46 r5a.2xlarge r5.2xlarge
7XL 8 61 m5a.4xlarge m5.4xlarge
8XL 16 92 r5a.4xlarge r5.4xlarge
Zones Set 1 US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Asia Pacific (Singapore)
Zones Set 2 US West (N. California), Canada (Central), EU (Frankfurt), EU (London), EU (Paris), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Osaka-Local), Asia Pacific (Sydney), Asia Pacific (Mumbai), South America (São Paulo), EU (Stockholm)

Due to technical issues, independent of EPAM Orchestrator and AWS, CentOS 6 images are not available for launching the new instance types. However, you can still get it beyond EPAM Cloud Orchestrator by calling CentOs 6 on instance types of previous generations directly with AWS tools.