7/2/2024, 12:00:00 AM ~ 7/3/2024, 12:00:00 AM (UTC)

Recent Announcements

AWS Private CA is now available in the Beijing and Ningxia Regions in China

AWS Private Certificate Authority (AWS Private CA) is now available in the AWS China (Beijing) Region, operated by Sinnet, and in the AWS China (Ningxia) Region, operated by NWCD. AWS Private CA is a managed, highly-available, cloud certificate authority (CA) with private keys secured in AWS-managed hardware security modules (HSMs). By using AWS Private CA, you can reduce the operational costs and complexity of using public key infrastructure (PKI) at scale across industries and use cases including financial services, automotive, manufacturing, healthcare, electronics, technology, energy, and smart home.\n AWS Private CA enables you to create customizable private certificates for a broad range of scenarios. AWS services such as AWS Certificate Manager, Amazon Managed Streaming for Apache Kafka (MSK), AWS IAM Roles Anywhere and Amazon Elastic Kubernetes Service (EKS) can all leverage private certificates from AWS Private CA. You can use AWS Private CA to create private certificates for Internet of Things (IoT) devices including Matter smart home devices. For regions where AWS Private CA is available, see AWS Services by Region. To learn more about AWS Private CA, visit the product page and documentation. To learn how to use AWS Private CA to create and operate Matter-compliant CAs, see Using the Matter standard.

AWS Managed Services (AMS) Accelerate now includes Trusted Remediator

AWS Managed Services (AMS) Accelerate customers can now use Trusted Remediator to automatically remediate recommendations based on Trusted Advisor checks. By eliminating human effort required to fix misconfigurations on the accounts, Trusted Remediator improves security, fault tolerance, performance, while simultaneously reducing cost for AMS customers. AMS helps you operate AWS efficiently and securely. It extends your operations team’s capabilities with operational and security monitoring, incident detection and management, patch, backup, and cost optimization.\n Trusted Remediator uses tested and proven automation solutions to not only minimize security risks but also scales operations processes by consistently providing quality remediations. Examples of supported checks include underutilized Amazon EBS Volumes and Amazon Redshift should have automatic upgrades to major versions enabled. Trusted Remediator provides customers with the flexibility to configure remediations across single or multiple accounts. Customers can choose to remediate checks at the account level or resource level, with the ability to apply tag-based exceptions. To learn more, see Trusted Remediator. Learn more about AMS here.

RDS for Db2 now supports Private Offers on licensing through AWS Marketplace

Amazon RDS for Db2 customers using hourly Db2 licensing through AWS Marketplace can now obtain customized contract terms from IBM, using AWS Marketplace Private Offers. This complements the existing options of using the public hourly license price to get started instantly, or using the Bring-Your-Own-License (BYOL) option.\n Customers can request a Private Offer from IBM and, if available, get individualized quotes on Db2 hourly licensing through AWS Marketplace. Amazon RDS for Db2 makes it easy to set up, operate, and scale Db2 databases in the cloud. See the Amazon RDS for Db2 Pricing page for pricing and regional availability information. To learn more about the AWS Marketplace license option, visit the AWS Documentation to get started.

Elastic Fabric Adapter (EFA) now supports cross-subnet communication

We are excited to announce that AWS now supports cross-subnet communication between Elastic Fabric Adapter (EFA) interfaces for Amazon EC2 instances within the same Availability Zone (AZ). This enhancement makes it possible to communicate with EC2 instances across subnets while benefiting from the low latency and high throughput provided by EFA. EFA is a network device that you can attach to your Amazon EC2 instance to accelerate High Performance Computing (HPC) and Machine Learning (ML) applications.\n Previously, EFA traffic was limited to the same subnet, thus requiring all instances to be configured within a single subnet. With this update, you have the option to send traffic over EFA across subnets for both existing and new instances. To take advantage of this capability, you need to configure your security group rules to allow traffic to and from security groups of instances from other subnets. You will also need to ensure your application configuration and orchestration logic accounts for hosts from other subnets when provisioning and managing EFA-enabled instances to communicate across subnets over EFA. The cross-subnet communication support over EFA is available in all AWS commercial regions, the AWS GovCloud (US) regions, and the Amazon Web Services China (Beijing) region, operated by Sinnet, and the Amazon Web Services China (Ningxia) region, operated by NWCD. For more information about EFA, please visit EFA documentation page.

Amazon EKS natively supports EC2 capacity blocks for ML

You can now use Amazon EC2 instances reserved using Capacity Blocks for ML natively in Amazon EKS clusters with managed node groups. EKS managed node groups make it easy to run highly-available and secure Kubernetes clusters by automating the provisioning and lifecycle of cluster worker nodes. EC2 Capacity Blocks provide you with assured and predictable access to GPU instances for your artificial intelligence / machine learning (AI/ML) workloads.\n Customers increasingly choose Kubernetes as the platform for their AI/ML workloads and Amazon EKS lets them combine the benefits of Kubernetes with the security, scalability, and availability of the AWS cloud. Native support for EC2 Capacity Blocks in Amazon EKS simplifies capacity planning for cutting-edge AI/ML workloads in Kubernetes clusters, helping to ensure that GPU capacity is available when and where it’s needed. To get started, create an EKS managed node group with an EC2 Launch Template targeting a Capacity Block reservation so that the reserved GPU capacity will be accessible in the EKS cluster when the reservation becomes active. EC2 Capacity Blocks can be reserved up to eight weeks in advance and for just the amount of time that you require the instances. Native EKS support for EC2 Capacity Blocks via managed node groups is available in the US East (Ohio), US East (N. Virginia), and US West (Oregon) AWS Regions. Read more about Amazon EKS support for EC2 Capacity Blocks for ML in the Amazon EKS User Guide.

Amazon MQ now supports RabbitMQ version 3.13

Amazon MQ now provides support for RabbitMQ version 3.13, which includes several fixes and performance improvements to the previous versions of RabbitMQ supported by Amazon MQ. Starting from RabbitMQ 3.13, Amazon MQ will manage patch version upgrades for your brokers. All brokers on version 3.13 will be automatically upgraded to the latest compatible and secure patch version in your scheduled maintenance window.\n If you are running earlier versions of RabbitMQ, such as 3.8, 3.9, 3.10, 3.11 or 3.12, we strongly encourage you to upgrade to RabbitMQ 3.13. This can be accomplished with just a few clicks in the AWS Management Console. Amazon MQ for RabbitMQ will soon end support for RabbitMQ versions 3.8, 3.9 and 3.10. To learn more about upgrading, see Managing Amazon MQ for RabbitMQ engine versions in the Amazon MQ Developer Guide. To learn more about the changes in RabbitMQ 3.13, see the Amazon MQ release notes. This version is available in all the regions Amazon MQ is available in. For a full list of available regions see the AWS Region Table.

AWS Blogs

AWS Japan Blog (Japanese)

AWS Cloud Operations & Migrations Blog

AWS Big Data Blog

AWS Compute Blog

AWS Database Blog

Desktop and Application Streaming

AWS Developer Tools Blog

Front-End Web & Mobile

AWS HPC Blog

AWS for Industries

AWS Machine Learning Blog

AWS for M&E Blog

Open Source Project

AWS CLI

AWS CDK

Amplify UI