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 .  

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.  

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.

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.

Signify’s low-blue recipe and downward optics should help keep northern Tenerife safe for stargazing.

One of the so-called “Big 3” players in the legacy lighting business will no longer sell end products after Osram finds a buyer for its Lighting Solutions luminaires business unit.

Amazon Redshift is now available on two different release cycles – Current Maintenance Track and Trailing Maintenance Track. With the Current Maintenance Track you will get the most up-to-date certified release version with the latest features, security updates, and performance enhancements. With the Trailing Maintenance Track you will be on the previous certified release. 

AWS Systems Manager Parameter Store now enables you to retrieve secrets managed in AWS Secrets Manager. With this launch, you can use a single set of APIs for retrieving your parameters managed in Parameter Store as well as secrets managed in Secrets Manager. For more details on retrieving Secrets Manager secrets using Parameter Store, visit our documentation here .

Amazon EC2 Fleet simplifies the provisioning of EC2 capacity across different instance types, Availability Zones (AZs) and across On-Demand, Reserved Instances (RIs) and Spot purchase models, optimizing scale, performance and cost. Allocation strategies lets you determine how EC2 Fleet should select from instances and AZs you have specified to fulfill the desired capacity. Until today, you had the option of selecting the single cheapest Instance Pool for Spot and On-Demand, or diversifying Spot Instances across multiple instance types and AZs in an EC2 Fleet.

Starting today, you can use Prioritized List to specifically determine the order in which EC2 Fleet attempts to fulfill your On-Demand capacity. EC2 Fleet will attempt to launch all capacity using the instance with the highest priority first, and if all your capacity cannot be fulfilled using your highest priority instance then EC2 Fleet will attempt launching capacity using the second priority instance type. You can define a priority for all instances you specify in your EC2 Fleet.

Starting today you can also balance desired cost and availability in the context of applications by directing EC2 Fleet to evenly deploy Spot capacity across the N lowest priced Instance Pools. For example if you are running batch processing, you may prefer to set N to just 2 to maximize savings while attempting to ensure your queue always has compute capacity. However, if you are running a web service you may set N to 10 to minimize the impact of any Spot Instance Pool becoming temporarily unavailable.

These new allocation strategies are also available in Spot Fleet. To learn more Prioritized List in EC2 Fleet visit this page, and to learn more about and Lowest*N strategy visit this page. Visit this blog to learn more about EC2 Fleet.