06Jan 2016

AWS is excited to announce immediate availability of the new AWS Asia Pacific (Seoul) Region. Seoul joins Singapore, Tokyo, Sydney, and Beijing as the fifth AWS Region in Asia Pacific and as the twelfth region worldwide, bringing the total number of AWS Availability Zones to 32 worldwide.

03Jan 2016

We are excited to announce that Amazon WorkMail is now available to all customers. Amazon WorkMail is a secure, managed business email and calendar service with support for existing desktop and mobile clients. Amazon WorkMail gives users the ability to seamlessly access their email, contacts, and calendars using Microsoft Outlook, Apple Mail, their web browser, or their native iOS and Android email applications.

27Dec 2015

You can now configure Amazon CloudFront to add custom headers, or override the value of existing headers, to requests forwarded to your origin. You can use these headers to help validate that requests made to your origin were sent from CloudFront; you can even configure your origin to only allow requests that contain the custom header values you specify. Additionally, if you use multiple CloudFront distributions with the same origin, you can use custom headers to distinguish origin request made by each different distribution. Finally, custom headers can be used to help determine the right CORS headers returned for your requests. You can configure custom headers via the CloudFront API and the AWS Management Console. There are no additional charges for this feature. For more details on how to set your custom headers, you can read more here.

21Dec 2015

You can now use additional Amazon CloudWatch metrics published by Amazon ECS for monitoring the reserved amount of CPU and memory resources used by running tasks in your clusters. You can create a CloudWatch alarm using these metrics that will add more Amazon EC2 instances to the Auto Scaling group when a cluster’s available capacity drops below a threshold you define. For more information on how to scale using CloudWatch alarms and Auto Scaling groups, see the documentation.

21Dec 2015

You can now create Amazon EMR clusters in private subnets in your Amazon Virtual Private Cloud (VPC). Previously, Amazon EMR only supported creating clusters in public subnets, which required an attached Internet gateway. With Amazon EMR release 4.2.0 and later, you can now also launch your clusters in a private subnet with no public IP addresses or attached Internet gateway. You can create an endpoint for Amazon S3 in your VPC to give your Amazon EMR cluster direct access to data in Amazon S3, and optionally create a Network Address Translation (NAT) instance for your cluster to interact with other AWS services that do not currently support endpoints in VPC.