Amazon OpenSearch Service now provides new Auto-Tune metrics and improved Auto-Tune events that give you better visibility into the cluster performance optimizations made by Auto-Tune.
Amazon RDS Custom for SQL Server now supports changing the server-level collation
Amazon RDS Custom for SQL Server now supports changing the server-level collation when creating a new DB Instance. If the collation is not specified the default server-level collation will continue to be SQL_Latin1_General_CP1_CI_AS. To learn more about which collations are supported please visit the RDS Custom for SQL Server User Guide .
Amazon MQ now supports RabbitMQ version 3.11.20
Amazon MQ now provides support for RabbitMQ version 3.11.20, which includes several fixes and improvements to the previous versions of RabbitMQ supported by Amazon MQ – 3.11.16. If you are running earlier versions of RabbitMQ, such as 3.10, 3.9 or 3.8, we strongly encourage you to upgrade to RabbitMQ 3.11. This can be accomplished with just a few clicks in the AWS Management Console . We also encourage you to enable automatic minor version upgrades on RabbitMQ 3.11 to help ensure your brokers take advantage of future fixes and improvements in 3.11.
Amazon S3 now provides the Last-Modified time for delete markers using S3 Head and Get APIs
Amazon S3 now provides the Last-Modified time of delete markers in the response headers of S3 Head and Get APIs. For buckets that use S3 Versioning, when a customer issues a delete request without a versionId specified, S3 adds a delete marker on the latest version of the object to protect data from accidental deletions. With Last-Modified information added to S3 Head and Get API response headers for delete markers, customers can more easily track changes in their buckets.
AWS Systems Manager OpsCenter identifies the most issue-prone resources
Starting today, OpsCenter, a capability of AWS Systems Manager, offers a new insight which automatically identifies resources with the most open operational issues (OpsItems). This insight helps cut through event noise, so that customers can focus their efforts on fixing their most issue-prone resources.
AWS Telco Network Builder is now available in 5 new AWS Regions
Today, we are announcing that AWS Telco Network Builder is now available in 5 new regions across Asia, America and Europe. AWS Telco Network Builder is now generally available in 5 additional regions: Asia Pacific (Seoul), Canada (Central), Europe (Spain), Europe (Stockholm), and South America (Sao Paulo).
Amazon EC2 Instance Connect now available in additional AWS Regions
Starting today, EC2 Instance Connect is also available in Middle East (Bahrain), Asia Pacific (Jakarta), Africa (Cape Town), Middle East (UAE), Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Osaka), Europe (Milan), Europe (Spain), Europe (Zurich), Asia Pacific (Melbourne) regions. Amazon EC2 Instance Connect is a simple and secure way to connect to your instances using Secure Shell (SSH).
Amazon MSK now supports fully managed data delivery to Amazon S3 using Kinesis Data Firehose
Amazon Kinesis Data Firehose now integrates with Amazon MSK to offer a fully managed solution that simplifies the processing and delivery of streaming data from Amazon MSK Apache Kafka clusters into data lakes stored on Amazon S3. With just a few clicks, Amazon MSK customers can continuously load data from their desired Apache Kafka clusters to their Amazon S3 bucket, eliminating the need to develop or run their own connector applications.
Amazon CloudFront announces security recommendations
You can now better protect your CloudFront distributions with AWS WAF security recommendations in the CloudFront console. CloudFront conveniently displays additional security rules for your distributions based on elements of your CloudFront configuration including path patterns or your origin type. Simply select the rules you’d like to enable and CloudFront automatically adds those rules to your AWS WAF configuration.
AWS WAF now supports JA3 Fingerprint Match
AWS WAF now supports JA3 match, enabling customers to inspect incoming requests’ JA3 fingerprints. Customers can use the JA3 match to implement custom logic to block malicious clients or allow requests from expected clients only.