Amazon EC2 C5/C5d and M5/M5d instances are built on the Nitro system, a collection of AWS-built hardware and software components that enable high performance, high availability, high security, and bare metal capabilities to eliminate virtualization overhead. With the latest set of enhancements to the Nitro system, we have increased the maximum EBS-optimized instance bandwidth to 14Gbps, up from 9Gbps and 10Gbps for C5/C5d and M5/M5d respectively. We have also increased the maximum EBS-optimized instance IOPS for Nitro systems to 80,000 IOPS, up from 64,000 IOPS and 65,000 IOPS for C5/C5d and M5/M5d respectively. In addition we have increased the EBS-optimized instance burst performance on the large, xlarge and 2xlarge C5/C5d and M5/M5d instances to 3.5Gbps, up from 2.25 Gbps and 2.12 Gbps respectively.

The AWS IoT Rules Engine can now trigger workflows built with AWS Step Functions using Step Functions action. With the addition of Step Functions action, the Rules Engine now supports 15 action types .

Amazon Chime now lets you choose Okta for configuring single-sign on (SSO). This means you can add and remove users, and change Chime permissions using your Okta directory. Changes made in Okta will be pushed to Chime automatically, which simplifies the administration of your Chime users. With Okta, your users can log into any of the Amazon Chime client apps using their corporate credentials, and you can apply your existing password policies for use with Chime.

AWS Greengrass is now available to customers in EU (Ireland) region. 

AWS Greengrass is software that lets you run local compute, messaging, data caching, sync, and ML inference capabilities for connected devices in a secure way. With AWS Greengrass, connected devices can run AWS Lambda functions, keep device data in sync, and communicate with other devices securely – even when not connected to the Internet. Using AWS Lambda, Greengrass ensures your IoT devices can respond quickly to local events, use Lambda functions running on Greengrass Core to interact with local resources, operate with intermittent connections, stay updated with over the air updates, and minimize the cost of transmitting IoT data to the cloud. Learn more about AWS Greengrass here. See the AWS Region Table for complete regional availability.

You can now get a detailed view of your Amazon Redshift cluster performance with the Workload Execution Breakdown graph on the console Database Performance page or the QueryRuntimeBreakdown metric via Cloudwatch. You can use these new metrics to optimize cluster performance to provide higher throughput and faster results. 

Starting today, you can add Amazon Lex bots from any region where Amazon Lex is available to any Amazon Connect instance. This means you can use Amazon Lex bots with your Amazon Connect instances in the EU (Frankfurt) and Asia Pacific (Sydney) AWS regions. Previously, you could only use Amazon Lex bots created in the same region as your Amazon Connect instance.

AWS CloudHSM now allows you to copy backups of your CloudHSM Cluster from one region to another for disaster recovery purposes. You can use the copied backup to create a clone of the original cluster in the new region. This simplifies the development of globally distributed or cross-region redundant workloads.

AWS CloudHSM is a cloud-based hardware security module (HSM) that enables you to easily generate and use your own encryption keys on the AWS Cloud. It is a fully-managed service that automates time-consuming administrative tasks for you, such as hardware provisioning, software patching, high-availability, and backups. CloudHSM also enables you to scale quickly by adding and removing HSM capacity on-demand, with no up-front costs.

AWS CloudHSM backups can only be copied across commercial regions. Users in the AWS GovCloud (US) region cannot copy backups into or out of the region. There is no cost for copying your backup across regions, or for creating a cluster from the copy in the new region. HSM instances are billed on an hourly basis. You can learn more about copying CloudHSM backups across regions here . You can learn how to synchronize keys between cloned clusters here .  

Data streaming applications can now utilize AWS PrivateLink and Amazon Kinesis Data Streams in US West (N. California), Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), EU (Frankfurt), EU (London), and South America (Sao Paulo) AWS Regions.

You can now monitor and troubleshoot your Amazon MQ message brokers in near-real time by publishing logs from your Amazon MQ brokers to Amazon CloudWatch Logs.  

Amazon Elasticsearch Service now lets you enable Elasticsearch error logs, providing you valuable information for troubleshooting your search and indexing operations quickly and easily. These logs are published to the Amazon CloudWatch Logs service and can be turned on or off at will. You only need to pay for the CloudWatch charges that you incur based on your usage. No additional Amazon Elasticsearch Service fees apply.