Amazon RDS io2 Block Express volumes are now available in AWS GovCloud (US-West) and AWS GovCloud (US-East) Regions. Amazon RDS io2 Block Express volumes provide consistent sub-millisecond latency for mission critical workloads.

Amazon RDS io2 Block Express volumes are designed for all your critical database workloads that demand high performance, high throughput, and consistently low latency. io2 Block Express storage has the lowest p99.9 I/O latency and the best outlier latency control among major cloud providers, making it ideal for the most I/O-intensive, mission-critical database workloads. io2 Block Express supports 99.999% durability, up to 64 TiB volumes, 4,000 MB/s throughput, and up to 256,000 Provisioned IOPS for your most demanding database needs for the same price as Amazon RDS io1 volumes. You can upgrade from an Amazon RDS io1 volume to an Amazon RDS io2 Block Express without any downtime using the ModifyDBInstance API.

To learn more about Amazon RDS storage, visit the Amazon RDS User’s Guide. Create or update a fully managed Amazon RDS database with an io2 Block Express volume or modify an existing io1, gp2, or gp3 volume type without disruptions in the Amazon RDS Management Console.

 

​Amazon RDS io2 Block Express volumes are now available in AWS GovCloud (US-West) and AWS GovCloud (US-East) Regions. Amazon RDS io2 Block Express volumes provide consistent sub-millisecond latency for mission critical workloads. Amazon RDS io2 Block Express volumes are designed for all your critical database workloads that demand high performance, high throughput, and consistently low latency. io2 Block Express storage has the lowest p99.9 I/O latency and the best outlier latency control among major cloud providers, making it ideal for the most I/O-intensive, mission-critical database workloads. io2 Block Express supports 99.999% durability, up to 64 TiB volumes, 4,000 MB/s throughput, and up to 256,000 Provisioned IOPS for your most demanding database needs for the same price as Amazon RDS io1 volumes. You can upgrade from an Amazon RDS io1 volume to an Amazon RDS io2 Block Express without any downtime using the ModifyDBInstance API. To learn more about Amazon RDS storage, visit the Amazon RDS User’s Guide. Create or update a fully managed Amazon RDS database with an io2 Block Express volume or modify an existing io1, gp2, or gp3 volume type without disruptions in the Amazon RDS Management Console.  

As of today, AWS Batch has introduced two new instance type options for allowed instance types in Compute Environment default-x86_64 (default) and default-arm64. These new options will automatically select the most cost-effective instance type across different generations, based on your job queue requirements, where AWS Batch previously supported only optimal instance type. This makes it easier to run your Batch workloads with newer generation EC2 instance families and can provide better performance at a lower cost. As new instance types become available in a region, they’ll be automatically added to the corresponding default pool.

To get started, you can select default-x86_64 or default-arm64 in the instanceType parameter for managed compute environments. There is no need to create a new compute environment—the existing ‘optimal’ option (which applies to M, C, and R EC2 instance familes) will continue to be supported and is not being deprecated, no action is needed. However, please be aware that only ENABLED and VALID Compute Environments (CEs) will be automatically updated with new instance types. If you have any DISABLED or INVALID CEs, they will receive updates once they are re-enabled and set to a VALID state.

This capability is now available for AWS Batch in all commercial and the AWS GovCloud (US) Regions. To learn more, see our launch blog, visit Batch’s documentation page or the Batch troubleshooting User Guide.

 

​As of today, AWS Batch has introduced two new instance type options for allowed instance types in Compute Environment default-x86_64 (default) and default-arm64. These new options will automatically select the most cost-effective instance type across different generations, based on your job queue requirements, where AWS Batch previously supported only optimal instance type. This makes it easier to run your Batch workloads with newer generation EC2 instance families and can provide better performance at a lower cost. As new instance types become available in a region, they’ll be automatically added to the corresponding default pool. To get started, you can select default-x86_64 or default-arm64 in the instanceType parameter for managed compute environments. There is no need to create a new compute environment—the existing ‘optimal’ option (which applies to M, C, and R EC2 instance familes) will continue to be supported and is not being deprecated, no action is needed. However, please be aware that only ENABLED and VALID Compute Environments (CEs) will be automatically updated with new instance types. If you have any DISABLED or INVALID CEs, they will receive updates once they are re-enabled and set to a VALID state. This capability is now available for AWS Batch in all commercial and the AWS GovCloud (US) Regions. To learn more, see our launch blog, visit Batch’s documentation page or the Batch troubleshooting User Guide.  

Amazon Managed Service for Prometheus, a fully managed Prometheus-compatible monitoring service, now supports resource-based policies, making it easier to build applications that work across accounts. With resource-based policies, you can specify which Identity and Access Management (IAM) principals have access to ingest or query your Amazon Managed Service for Prometheus workspace.

To allow cross-account ingestion into an Amazon Managed Service for Prometheus workspace or query the metrics using PromQL from a different account, customers so far had to assume an IAM role in the workspace owner account. With this launch, you now can attach a resource-based policy to an Amazon Managed Service for Prometheus workspace and allow-list non-workspace owner to perform any actions using Prometheus-compatible APIs.

This feature is now available in all regions where Amazon Managed Service for Prometheus is generally available.

To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.

 

​Amazon Managed Service for Prometheus, a fully managed Prometheus-compatible monitoring service, now supports resource-based policies, making it easier to build applications that work across accounts. With resource-based policies, you can specify which Identity and Access Management (IAM) principals have access to ingest or query your Amazon Managed Service for Prometheus workspace.
To allow cross-account ingestion into an Amazon Managed Service for Prometheus workspace or query the metrics using PromQL from a different account, customers so far had to assume an IAM role in the workspace owner account. With this launch, you now can attach a resource-based policy to an Amazon Managed Service for Prometheus workspace and allow-list non-workspace owner to perform any actions using Prometheus-compatible APIs.
This feature is now available in all regions where Amazon Managed Service for Prometheus is generally available.
To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.  

Starting today, customers can view 6 new recommended actions added to the existing list of 15 recommended actions available in the AWS Billing and Cost Management Console recommended actions widget. These recommended actions include notifications across AWS payments and tax settings, such as an expired payment method or if tax registration numbers are invalid. All recommended actions are now categorized as critical, advisory, or informational, enabling customers to prioritize and timely resolve any identified billing issues. 

Using recommended actions on the AWS Billing and Cost Management Console, customers can quickly learn of and mitigate AWS billing or payment issues, identify cost saving opportunities, and avoid surprises by acting on time-sensitive information. Each recommended action includes a specific call-to-action, which allows customers to optimize their AWS spend and prevent any disruptions to their AWS account and billing status. Customers can access these recommendation actions through the recommended actions widget in the console or via a new public API at no additional cost.

The recommended actions widget and API is available in all AWS commercial regions, excluding China. To get started with new recommended actions, visit the recommended actions widgets on the AWS Billing and Cost Management Console. To learn more, see recommended actions in the AWS Billing and Cost Management user guide

 

​Starting today, customers can view 6 new recommended actions added to the existing list of 15 recommended actions available in the AWS Billing and Cost Management Console recommended actions widget. These recommended actions include notifications across AWS payments and tax settings, such as an expired payment method or if tax registration numbers are invalid. All recommended actions are now categorized as critical, advisory, or informational, enabling customers to prioritize and timely resolve any identified billing issues.  Using recommended actions on the AWS Billing and Cost Management Console, customers can quickly learn of and mitigate AWS billing or payment issues, identify cost saving opportunities, and avoid surprises by acting on time-sensitive information. Each recommended action includes a specific call-to-action, which allows customers to optimize their AWS spend and prevent any disruptions to their AWS account and billing status. Customers can access these recommendation actions through the recommended actions widget in the console or via a new public API at no additional cost. The recommended actions widget and API is available in all AWS commercial regions, excluding China. To get started with new recommended actions, visit the recommended actions widgets on the AWS Billing and Cost Management Console. To learn more, see recommended actions in the AWS Billing and Cost Management user guide  

Amazon Connect Cases now supports Contact Lens Rules that automatically update cases when created, streamlining case workflows and reducing manual tasks. For example, you can configure rules to auto-assign refund cases to the billing team, auto-close cases that don’t require follow-up, or automatically set priority based on case reason.

Amazon Connect Cases is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town) AWS regions. To learn more and get started, visit the Amazon Connect Cases webpage and documentation.

 

​Amazon Connect Cases now supports Contact Lens Rules that automatically update cases when created, streamlining case workflows and reducing manual tasks. For example, you can configure rules to auto-assign refund cases to the billing team, auto-close cases that don’t require follow-up, or automatically set priority based on case reason. Amazon Connect Cases is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town) AWS regions. To learn more and get started, visit the Amazon Connect Cases webpage and documentation.  

Amazon Athena now supports CREATE TABLE AS SELECT (CTAS) statements with Amazon S3 Tables. Using CTAS statements makes it simple to create a new table and populate it with data using the results of a SELECT query. You can now use CTAS statements in Athena to query existing datasets and create a new table in S3 Tables with the query results, all in a single SQL statement.

S3 Tables deliver the first cloud object store with built-in Apache Iceberg support and streamline storing tabular data at scale. With today’s launch, you can quickly and efficiently convert existing datasets stored in Parquet, CSV, JSON, and other formats, including Apache Iceberg, Hudi, and Delta Lake, into fully-managed tables that are continually optimized for performance and cost. Once created, use Athena to analyze your data, JOIN it with other datasets, and evolve it over time using INSERT and UPDATE operations. Using CTAS, you can partition the data on the fly, giving you flexibility to optimize query performance for different use cases.

You can use CTAS to create S3 Tables in all AWS Regions where both Athena and S3 Tables are supported. To learn more, see the Amazon Athena User Guide.

 

​Amazon Athena now supports CREATE TABLE AS SELECT (CTAS) statements with Amazon S3 Tables. Using CTAS statements makes it simple to create a new table and populate it with data using the results of a SELECT query. You can now use CTAS statements in Athena to query existing datasets and create a new table in S3 Tables with the query results, all in a single SQL statement. S3 Tables deliver the first cloud object store with built-in Apache Iceberg support and streamline storing tabular data at scale. With today’s launch, you can quickly and efficiently convert existing datasets stored in Parquet, CSV, JSON, and other formats, including Apache Iceberg, Hudi, and Delta Lake, into fully-managed tables that are continually optimized for performance and cost. Once created, use Athena to analyze your data, JOIN it with other datasets, and evolve it over time using INSERT and UPDATE operations. Using CTAS, you can partition the data on the fly, giving you flexibility to optimize query performance for different use cases. You can use CTAS to create S3 Tables in all AWS Regions where both Athena and S3 Tables are supported. To learn more, see the Amazon Athena User Guide.  

DynamoDB now supports more granular throttling exceptions along with their corresponding Amazon CloudWatch metrics. The additional fields in the new throttling exceptions identify the specific resources and reasons for throttling events, making it easier to understand and diagnose throttling-related issues.

You can see the new Amazon CloudWatch metrics immediately, and upon upgrading your SDK to the newest version, you will also see the new granular throttling exceptions. Every throttling exception now contains a list of reasons why the request was throttled, as well as the Amazon Resource Name (ARN) of the table or index that was throttled. These new throttle exception reasons help you understand why you were throttled and enable you to take corrective actions like adjusting your configured throughput, switching your table to on-demand capacity mode, or optimizing data access patterns.

The more granular throttling exceptions and their respective metrics are available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions.

To get started see the following list of resources:

• Diagnosing throttling issues in the DynamoDB developer guide
• Enhanced throttling observability in Amazon DynamoDB blog post
• Troubleshooting throttling in the DynamoDB developer guide

 

​DynamoDB now supports more granular throttling exceptions along with their corresponding Amazon CloudWatch metrics. The additional fields in the new throttling exceptions identify the specific resources and reasons for throttling events, making it easier to understand and diagnose throttling-related issues. You can see the new Amazon CloudWatch metrics immediately, and upon upgrading your SDK to the newest version, you will also see the new granular throttling exceptions. Every throttling exception now contains a list of reasons why the request was throttled, as well as the Amazon Resource Name (ARN) of the table or index that was throttled. These new throttle exception reasons help you understand why you were throttled and enable you to take corrective actions like adjusting your configured throughput, switching your table to on-demand capacity mode, or optimizing data access patterns. The more granular throttling exceptions and their respective metrics are available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions. To get started see the following list of resources:

Diagnosing throttling issues in the DynamoDB developer guide
Enhanced throttling observability in Amazon DynamoDB blog post
Troubleshooting throttling in the DynamoDB developer guide  

DynamoDB now supports the ability to selectively emit events for throttled keys to CloudWatch Contributor Insights, enabling you to monitor throttled keys without emitting events for all accessed keys. By emitting events for throttled keys exclusively, you no longer need to pay for all of your successful request events.

Cloudwatch Contributor Insights for DynamoDB can help you understand your traffic patterns by providing information about your most accessed and throttled keys in a table or global secondary index. This information can be used to understand your application usage patterns or diagnose throttling-related issues. By choosing to only emit events for throttled keys, you can reduce the amount you spend to receive these insights.

The new mode to exclusively emit throttled key events to CloudWatch Contributor Insights is available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions.

To get started, see the following list of resources:

• CloudWatch Contributor Insights for DynamoDB in the DynamoDB developer guide
• Enhanced throttling observability in Amazon DynamoDB blog post
• Troubleshooting throttling in the DynamoDB developer guide

 

​DynamoDB now supports the ability to selectively emit events for throttled keys to CloudWatch Contributor Insights, enabling you to monitor throttled keys without emitting events for all accessed keys. By emitting events for throttled keys exclusively, you no longer need to pay for all of your successful request events. Cloudwatch Contributor Insights for DynamoDB can help you understand your traffic patterns by providing information about your most accessed and throttled keys in a table or global secondary index. This information can be used to understand your application usage patterns or diagnose throttling-related issues. By choosing to only emit events for throttled keys, you can reduce the amount you spend to receive these insights. The new mode to exclusively emit throttled key events to CloudWatch Contributor Insights is available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions. To get started, see the following list of resources:

CloudWatch Contributor Insights for DynamoDB in the DynamoDB developer guide
Enhanced throttling observability in Amazon DynamoDB blog post
Troubleshooting throttling in the DynamoDB developer guide  

AWS Certificate Manager (ACM) now supports AWS PrivateLink so that you can access ACM APIs from your Amazon Virtual Private Cloud (VPC) without traversing the public internet. This feature can help you meet compliance requirements by allowing you to access and use ACM APIs entirely within the AWS network.

ACM simplifies the process of provisioning and managing public and private TLS certificates, wherever you need to securely terminate traffic; Whether it’s with integrated AWS services such as Amazon CloudFront, Load Balancing or with hybrid workloads. You can now create interface endpoints in AWS Private Link to connect your VPC to ACM. Communication between your VPC and ACM is then conducted entirely within the AWS network, providing a secure pathway for your data.

To get started, you can create an AWS PrivateLink to connect to ACM using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands or AWS CloudFormation. This new feature is available in all AWS Regions including AWS GovCloud (US) and China Regions where AWS Certificate Manager Service and AWS PrivateLink are available. For more information, please refer to the AWS PrivateLink documentation.

 

​AWS Certificate Manager (ACM) now supports AWS PrivateLink so that you can access ACM APIs from your Amazon Virtual Private Cloud (VPC) without traversing the public internet. This feature can help you meet compliance requirements by allowing you to access and use ACM APIs entirely within the AWS network. ACM simplifies the process of provisioning and managing public and private TLS certificates, wherever you need to securely terminate traffic; Whether it’s with integrated AWS services such as Amazon CloudFront, Load Balancing or with hybrid workloads. You can now create interface endpoints in AWS Private Link to connect your VPC to ACM. Communication between your VPC and ACM is then conducted entirely within the AWS network, providing a secure pathway for your data. To get started, you can create an AWS PrivateLink to connect to ACM using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands or AWS CloudFormation. This new feature is available in all AWS Regions including AWS GovCloud (US) and China Regions where AWS Certificate Manager Service and AWS PrivateLink are available. For more information, please refer to the AWS PrivateLink documentation.  

Amazon Relational Database Service (RDS) for Db2 now supports cross-region automated backups for encrypted databases, providing customers with an additional layer of data protection while safeguarding their mission critical Db2 workloads against regional outages.

Customers can now securely copy encrypted database snapshots to regions outside of their primary AWS region for improved disaster recovery. The feature can be enabled by simply turning on encryption for RDS for Db2 instances, and configuring backup replication to the desired AWS region.

To learn more about Amazon RDS for Db2 cross-region automated backups and the supported destination regions, visit the documentation page. Amazon RDS for Db2 makes it simple to set up, operate, and scale Db2 deployments in the cloud. See Amazon RDS for Db2 Pricing for up-to-date pricing of instances, storage, backup, data transfer, and regional availability.

 

​Amazon Relational Database Service (RDS) for Db2 now supports cross-region automated backups for encrypted databases, providing customers with an additional layer of data protection while safeguarding their mission critical Db2 workloads against regional outages. Customers can now securely copy encrypted database snapshots to regions outside of their primary AWS region for improved disaster recovery. The feature can be enabled by simply turning on encryption for RDS for Db2 instances, and configuring backup replication to the desired AWS region. To learn more about Amazon RDS for Db2 cross-region automated backups and the supported destination regions, visit the documentation page. Amazon RDS for Db2 makes it simple to set up, operate, and scale Db2 deployments in the cloud. See Amazon RDS for Db2 Pricing for up-to-date pricing of instances, storage, backup, data transfer, and regional availability.