Amazon Redshift automatically takes incremental snapshots (backups) of your data every 8 hours or 5 GB per node of data change. You now get more information and control over a snapshot including the ability to control the automatic snapshot’s schedule.

The Amplify CLI, part of the Amplify Framework, now includes support for configuring OAuth 2.0 Authorization Flows and enabling the Amazon Cognito Hosted UI. This enables you to setup federation between social identity providers such as Amazon, Facebook, and Google with Amazon Cognito User Pools. The federation is achieved using OAuth 2.0 flows, which can be performed through Hosted UI or your application code (using the endpoints directly). Previously, developers had to go to the Amazon Cognito console to set this up and construct the proper application configurations manually in their web or mobile applications.

In addition, new commands in the Amplify CLI make it easier to configure Augmented Reality (AR) and Virtual Reality (VR) scenes from Amazon Sumerian for your mobile and web applications. The commands enable you to add authorization for your scenes using Amazon Cognito and IAM.

This release also adds options to the Storage and API categories for setting up fine-grained CRUD style permissions on Amazon S3 and Amazon API Gateway, respectively. This functionality supports both authenticated and unauthenticated application workflows. Previously, developers could add only read/write permissions for these categories.

 

Amazon Comprehend is a natural language processing (NLP) service that uses machine learning to discover insights and relationships in text. Starting today, you can assign tags to custom classifier and entity type resources. This enables you to allocate costs and get detailed billing reports across your custom models.

Each tag is a simple label consisting of a customer-defined key and an optional value that can make it easier to manage, search for, and filter resources. You can allocate costs by creating tagged Billing Groups and mapping individual “Things” to those groups.

All usage and cost for a model will inherit the tags of the Billing Group to which it belongs. IAM policies also support tag-based conditions, enabling you to constrain IAM permissions based on specific tags or tag values (when leveraging tag-based conditions for access control, make sure to also define and restrict who can modify those tags).

These features are provided at no additional cost. Click here to learn more about how to create and use tags in Amazon Comprehend . See AWS Tagging Strategies for general best practices for using tags with AWS resources.

Amazon Connect now supports claiming phone numbers in Puerto Rico. This enables you to provide local telephony support to end-customers in Puerto Rico. Additionally, outbound dialing rates to Puerto Rico have been reduced by 59% in the US East (N. Virginia) and US West (Oregon) regions.

Today AWS Elemental MediaLive adds the option to create “Single-pipeline” channels, a lower cost alternative to “Standard” channels. MediaLive Single-pipeline channels have one input and a single encoding pipeline delivering a single channel output, rather than the redundant dual Availability Zone (AZ) pipelines that MediaLive provides with a Standard channel. The rates for inputs, outputs, and add-on functionality used for Single-pipeline channels are significantly lower than the rates for Standard channels.

AWS Elastic Beanstalk adds tagging and tag-based access control for four Elastic Beanstalk resources: applications, application versions, saved configurations, and custom platform versions.

AWS Elemental MediaPackage and AWS Elemental MediaTailor now support a broad range of variant DASH outputs and features. This added functionality enables support for live streams on more devices. It also continues to allow personalized, dynamic ad insertion to monetize live streams.

You can now specify a worker type for Apache Spark jobs in AWS Glue for memory intensive workloads.

AWS Backup is now available in the AWS Asia Pacific (Sydney) and EU (Frankfurt) Regions.

Amazon Virtual Private Cloud Flow Logs (VPC Flow Logs) can now be delivered directly to Amazon Simple Storage Service (S3) using the AWS Command Line Interface (CLI) or through your Amazon EC2 or VPC console in AWS GovCloud (US) Regions. You can now deliver VPC Flow Logs to both S3 and CloudWatch Logs.