W-Systems COVID-19 Business Continuity Read More

Amazon EC2 March 2020 Update

Released on March 23rd, 2020

AWS Adds the Ability for Customers to Enable AWS Local Zones Themselves

Starting today, customers can easily enable AWS Local Zones themselves from the new “Settings” section of the EC2 Console or ModifyAvailabilityZoneGroup API. Once enabled, customers can create and manage resources in Local Zones using the same APIs and Management Console they use for Availability Zones in AWS Regions today.

AWS Local Zones are a type of AWS infrastructure deployment that places compute, storage, and other select services closer to customers, giving them the ability to run applications on AWS that require single-digit millisecond latencies to their end-users or on-premise installations. The first AWS Local Zone is generally available in Los Angeles, California.

To learn more, please refer to the user guide or visit AWS Local Zones product website.

Amazon ECS Supports in Preview Updating Placement Strategy and Constraints for Existing ECS Services

Amazon Elastic Container Service (ECS) now supports updating Placement Strategy and Constraints for existing ECS services (in Preview). ECS customers can now update the placement strategies and constraints for their ECS services without having to recreate a service with the desired changes. This flexibility and control in managing the placement of service tasks helps customers save cost and reduce potential service downtime. 

Customers use task placement strategy and constraints as a tool to manage the cost, resource utilization and availability of their application by defining the task’s placement logic. Previously, a change to the task placement parameters required the user to recreate the service. Now, customers can use the UpdateService API to change the placement logic for an existing service by updating the service with the desired placement strategy and constraints. ECS will enforce these changes at the time of the next service deployment. This enables customers to iterate on their task placement logic to get more out of their ECS clusters and reduce the DevOps effort required. 

ECS Support for Updating Placement Strategies and Constraints is now available across all AWS Regions with ECS. To get started, please see the ECS documentation and API reference Documentation

Amazon EC2 Hibernation now Lets you Pause and Resume Your Workloads on T2 Instance Types

Amazon EC2 can now hibernate EBS-backed Amazon EC2 T2 instances. You can now hibernate your newly launched instances running on T2 instance types. Hibernation provides you the convenience of pausing and resuming your workloads. Hibernation is just like closing and opening your laptop lid, your application will start right where it left off.

Hibernation saves effort in setting up the environment or applications all over again, and saves time by reducing the long startup time taken by applications. Using hibernate, you can maintain a fleet of pre-warmed instances that can get to a productive state faster without modifying your existing applications.

Hibernation is available for On-Demand and Reserved Instances running on M3, M4, M5, C3, C4, C5, R3, R4, R5, and T2 instances running Amazon Linux, Amazon Linux 2, Ubuntu 16.04 and 18.04 LTS and Windows Server 2012, 2012R2, 2016 and 2019. For Windows, Hibernation is supported for instances up to 16 GB of RAM. For other operating systems, Hibernation is supported for instances with less than 150 GB of RAM.

This feature is available through AWS CloudFormationAWS Management Console, or through the AWS SDKsAWS Tools for Powershell or the AWS Command Line Interface (CLI). To learn more about hibernation, visit this blog. For information about enabling hibernation for your EC2 instances, visit FAQs or technical documentation.

Use Amazon VPC Endpoint Policies for Granular Control of Amazon EC2 APIs

Amazon Elastic Compute Cloud (EC2) now lets you attach IAM resource policies to your VPC endpoints. VPC Endpoint policies can help you meet compliance and regulatory requirements by granularly controlling access to Amazon EC2 APIs.

You can use a VPC endpoint policy to define the Amazon EC2 actions (RunInstances, CreateVolume, etc) that may be performed, the principal that may perform the actions, and the resources on which the actions may be performed. The list of resource types supported for each EC2 action can be found in the Amazon EC2 IAM policy documentation.

VPC endpoint policies for Amazon EC2 are available in all public AWS regions. You can get started with endpoint policies by creating a VPC endpoint for Amazon EC2, or by adding a policy to an existing VPC endpoint. For more information about using VPC endpoint policies, see the Amazon EC2 documentation.

« Back to Releases