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|
|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.