AWS Step Functions now supports AWS PrivateLink allowing you to access AWS Step Functions from VPC-enabled AWS Lambda functions and other AWS services without traversing the public internet. By using AWS PrivateLink, you can access Step Functions while keeping your network traffic within the Amazon network using interface VPC endpoints. Your network architecture is significantly simplified as you no longer need to use an Internet Gateway, Network Address Translation (NAT) devices, or firewall proxies to connect to AWS Step Functions.

The AWS Deep Learning Containers are available today with Tensorflow 2.0. This latest version provides significant updates to the existing API, simplifies eager execution, offers a new dataset manager, and more. You can launch the new versions of Deep Learning Container on Amazon SageMaker, Amazon Elastic Kubernetes Service (Amazon EKS), self-managed Kubernetes on Amazon EC2, and Amazon Elastic Container Service (Amazon ECS). For a complete list of frameworks and versions supported by the AWS Deep Learning Containers, see release notes .

The Amazon FSx for Lustre CSI driver has reached beta status and is now supported by Amazon Elastic Kubernetes Service (EKS). The CSI driver makes it simple to configure and use FSx for Lustre high performance file systems with containers on EKS and self-managed Kubernetes clusters running on AWS. 

Amazon FSx for Lustre, a high performance file system optimized for workloads such as machine learning, high performance computing, video processing, financial modeling, electronic design automation, and analytics, has added functionality that makes it easier to synchronize file data and file permissions between Amazon FSx and Amazon S3. Additionally, Amazon FSx has quadrupled the speed of launching FSx file systems that are linked to S3 buckets.

AWS IoT Device Tester for Amazon FreeRTOS now supports Amazon FreeRTOS 201912.00 .  The latest version of device tester includes optional tests for OTA (Over-the-air) over https to qualify your Amazon FreeRTOS development boards.

Automation, a feature of Systems Manager, now supports adding tags to your Automation executions, making it easy to sort and filter executions in different ways, such as by resource, purpose, owner, or environment. For example, you can run an Automation that is a remediation for your RDS instance by adding multiple tags (‘Remediation’ and ‘RDS’). This enables you to query for workflow-based tags and resource-based tags. Similarly, you can have different tags for environments, such as prod or test. For example, for patching your prod fleet, you can add ‘Patch’ and ‘Prod’ tags. Similarly, for patching your test fleet, you can add ‘Patch’ and ‘Test’ tags. 

Automation, a feature of Systems Manager, now supports running an Automation execution that targets all instances in the account and Region. This support makes it easier to maintain consistency in your fleet when you make configuration changes or run a specific set of commands.  

Amazon Lex now supports the ability to store chat history. Starting today, you can configure logging of audio input to an S3 bucket and text input to CloudWatch Logs.  

Amazon MQ is now available in a total of 16 regions, with the addition of the Europe (Stockholm) and South America (São Paulo) regions.

You can use Systems Manager Automation to run a single task across multiple accounts and multiple Regions. With this launch, you can target a single remote resource instead of starting workflows for multiple remote resources using tags or resource groups. For example, you can centrally trigger Amazon Inspector runs across all your accounts in all Regions to discover potential security issues on your AWS resources.