Now, you can allow easy authentication for your users by enabling YubiKey security key as your users’ MFA device. You can enable a single YubiKey security key (manufactured by Yubico , a third party provider) for multiple IAM and root users across AWS accounts making it easier to manage your MFA devices for access to multiple users. You can also use your existing YubiKey, which you use to authenticate to other third-party applications such as GitHub or Dropbox, to sign in to the AWS Management Console . 

AWS Elastic Beanstalk now supports T3 instance . This is supported on all latest platform configurations and available in all corresponding regions. To learn more about T3 instance benefits and features, see Amazon EC2 T3 instance type .

The Vital Vio-based continuous disinfection technology licensed by Visa Lighting is said by the parties to not infringe on IP originating with the University of Strathclyde and licensed in the US by Kenall Manufacturing.

The Dallas automobile garage made famous in the Discovery Channel Fast N’ Loud TV series now features an SSL installation from Dialight to highlight the show cars turned out by Richard Rawlings and his crew.

Alexa for Business now allows organizations to connect select Echo devices managed by Alexa for Business to their corporate WPA2 Enterprise Wi-Fi network. Though Echo devices don’t need direct access to services on enterprise networks, many organizations prefer to have all devices on their WPA2 enterprise protected network to simplify network and device management. This new feature, available in beta, lets you connect the Echo devices to your existing WPA2 wireless network without having to create a guest or WPA2 personal network.  

Amazon Aurora (both MySQL and PostgreSQL compatible editions) now allow you to stop and start database clusters. This makes it easy and affordable to use database clusters for development and test purposes where the database is not required to be running all of the time.

Stopping and starting a database cluster requires just a few clicks in the AWS Management Console, or a single call using the AWS API or AWS Command Line Interface, and takes just a few minutes. Stopping a database cluster stops the primary instance and any Aurora Replicas. While your database cluster is stopped, you are charged for cluster storage, manual snapshots and automated backup storage within your specified retention window, but not for database instance hours.

While a database cluster is stopped, you can do a point-in-time restore to any point within your specified automated backup retention window. Starting a database cluster restores it to the same configuration as it had when stopped, including its endpoint, replica instances, parameter groups, VPC security groups, and option group settings.

You can stop a database cluster for up to 7 days at a time. After 7 days, it will be automatically started. For more details on stopping and starting a database cluster, please refer to Stopping and Starting a DB Cluster in the Amazon RDS User Guide.

Amazon Aurora combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. It provides up to three times better performance than the typical PostgreSQL database, and five times better than the typical MySQL database, together with increased scalability, durability, and security. See the AWS Region Table for complete regional availability.

You can now retrieve snapshot of a CloudWatch graph to display on your websites, wikis, and custom dashboards outside of the AWS console for improved monitoring visibility.

Starting today, Amazon EC2 R5 instances are available in the Asia Pacific (Seoul, Sydney, Tokyo), Europe (Frankfurt, London), US West (N. California), Canada (Central), and GovCloud (US-West) AWS regions. This is in addition to the US East (N. Virginia), US East (Ohio), US West (Oregon), and Europe (Ireland) AWS regions where R5 instances were already available since July 25th, 2018.

Amazon EC2 Spot Console now supports scheduled scaling for Application Auto Scaling, enabling you to plan scaling activities based on predictable workload patterns. Using the Spot Console, now you can create scheduled actions for your Spot Fleet request to scale the capacity up and down at specified times.

When you create a scheduled action, you can specify when the scaling activity should occur, the minimum capacity, and the maximum capacity. At the specified time, Auto Scaling scales your Fleet based on the new capacity values. You can create scheduled actions that scale one time only, or that scale on a recurring basis.

Support for scheduled scaling in the EC2 Spot Console is now available in all public AWS regions. You can learn more about this feature by reading the documentation page and learn about Spot Instances here .