Starting today, web developers can use the Amazon Chime SDK React Component Library to simplify implementation of common user experiences, for example device selection and local video preview, in their real-time voice, video, and screen sharing web applications. By building with higher-level components, developers can focus on customizing their application while reducing investments in complex client implementations requiring careful configuration of audio and video parameters. 

Amazon WorkSpaces now allows you to use a fully qualified domain name (FQDN) as your Amazon WorkSpaces registration code. When your end users log in to WorkSpaces, you can then redirect them across Amazon WorkSpaces Regions based on your Domain Name System (DNS) policies for the FQDN. Amazon WorkSpaces cross-Region redirection works with both public domain names and domain names in private DNS zones. The new feature is designed for customers who deploy WorkSpaces in multiple Regions to achieve regional resiliency and high availability. 

AWS Single Sign-On (SSO) adds new account assignment APIs and AWS CloudFormation support to automate access across AWS Organizations accounts. You can also use the APIs to retrieve permissions programmatically for audit and governance purposes. The new release enables you to automate control of the AWS SSO central permissions, making it easier to manage access at scale across all your AWS accounts.

We are excited to introduce Paginators in the latest release of AWS SDK for .NET v3.5 . Many AWS operations return paginated results when the response object is too large to return in a single response. Using Paginators will help you navigate through paginated responses from services. If you are using .NET Core, you can now take advantage of IAsyncEnumerable interface that was introduced to .NET with .NET Core 3.1 to make it easy to navigate through responses asynchronously.  

Amazon Elastic Kubernetes Service (EKS) customers can now leverage EC2 security groups to secure applications with varying network security requirements on shared cluster compute resources.

Amazon Relational Database Service (RDS) now supports AWS Graviton2-based database instances in Asia Pacific (Mumbai, Singapore, Sydney) regions in preview. Graviton2 M6g and R6g database instances deliver better price performance over comparable current generation x86-based database instances. You can launch these database instances in preview when using Amazon RDS for MySQL and Amazon RDS for PostgreSQL. For more details including database engine versions supported, refer to the documentation .

AWS Service Catalog now supports the use of administrator-provided names for product discovery, provisioning, and searches on running products. With this new feature, administrators can define their taxonomy for product naming and versioning, and this taxonomy is accessible to builders and administrators for use within their code and scripts. Referencing by name helps builders innovate faster, and provides a consistent product discovery and provisioning experience across accounts and regions.  

You can now initiate on-demand scanning for patch compliance in accordance with your patch rules, remediate when patches are out of compliance within seconds using AWS Systems Managers Patch Manager, and track the progress in real time. You can patch your instances using pre-defined concurrency and error threshold configurations offered by Patch Manager. This new feature enables you to update your patch compliance on-demand without waiting for the next maintenance window by initiating patching with 2 clicks.

Amazon Managed Streaming for Apache Kafka (Amazon MSK) now offers MSK version 2.4.1.1, a bug fix release of Apache Kafka version 2.4.1, addressing a critical bug (KAFKA-9752 ) that causes consumer groups to perpetually rebalance. MSK recommends that all customers who use or plan to use Apache Kafka version 2.4.1 instead use or upgrade their clusters to MSK version 2.4.1.1. After September 23, 2020, Apache Kafka version 2.4.1 will no longer be offered for new MSK clusters.

In addition to the previously supported OIDC/OAuth2 authorization option, customers can now secure Amazon API Gateway HTTP APIs using two new authorization options: Lambda authorizers and IAM authorizers. These new options enable customers to make flexible authorization decisions by providing an AWS Lambda function, or leveraging AWS IAM policies to control access to their APIs without writing any code.