Starting today, long-term support (LTS) will also be provided on Aurora MySQL 3.10 (compatible with MySQL 8.0.42) minor version. Database clusters that use LTS releases can stay on the same minor version for at least three years or until end of standard support for the major version, whichever is sooner. During the lifetime of an Aurora MySQL LTS release, new patches introduce fixes for select high severity security and operational issues. These patches don’t include any new features. For more details about Aurora MySQL 3.10, refer to the Aurora MySQL 3.10 launch announcement and release notes.

This is the second minor version designated as LTS on Aurora MySQL-Compatible Edition 3 in addition to Aurora MySQL 3.04 (compatible with MySQL 8.0.26) minor version. This LTS version does not change the end of life schedules for other LTS versions or engine major versions. For more details about LTS and how to stay on the LTS minor version, refer to LTS documentation. This LTS release is available in all AWS regions where Aurora MySQL is available.

Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.

 

​Starting today, long-term support (LTS) will also be provided on Aurora MySQL 3.10 (compatible with MySQL 8.0.42) minor version. Database clusters that use LTS releases can stay on the same minor version for at least three years or until end of standard support for the major version, whichever is sooner. During the lifetime of an Aurora MySQL LTS release, new patches introduce fixes for select high severity security and operational issues. These patches don’t include any new features. For more details about Aurora MySQL 3.10, refer to the Aurora MySQL 3.10 launch announcement and release notes. This is the second minor version designated as LTS on Aurora MySQL-Compatible Edition 3 in addition to Aurora MySQL 3.04 (compatible with MySQL 8.0.26) minor version. This LTS version does not change the end of life schedules for other LTS versions or engine major versions. For more details about LTS and how to stay on the LTS minor version, refer to LTS documentation. This LTS release is available in all AWS regions where Aurora MySQL is available. Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.  

Amazon S3 Express One Zone, a high-performance S3 storage class for latency-sensitive applications, now supports resilience testing with AWS Fault Injection Service (FIS). With this launch, you can use the FIS network disruption action to test the failover response and recovery of your latency-sensitive applications in the unlikely event of a disruption to an Availability Zone (AZ) that impairs access to your data. You can use the results of FIS experiments to verify your monitoring, test recovery processes, and improve application resilience.

With FIS, you can disrupt connectivity to your S3 Express One Zone data in S3 directory buckets, helping you validate application resilience. During the FIS experiment, data plane requests made to directory buckets will timeout. This fault action is also included in the FIS AZ Availability: Power Interruption scenario, so you can test the resilience of your applications when an AZ event impacts multiple AWS services.

You can use the updated FIS network disruption action for S3 Express One Zone data in all AWS Regions where the storage class is available. To get started with testing the resilience of applications that store data in S3 Express One Zone, you can use the AWS Management Console, AWS CLI, or FIS API. For pricing information, visit the FIS pricing page. To learn more, visit the AWS FIS user guide.

 

​Amazon S3 Express One Zone, a high-performance S3 storage class for latency-sensitive applications, now supports resilience testing with AWS Fault Injection Service (FIS). With this launch, you can use the FIS network disruption action to test the failover response and recovery of your latency-sensitive applications in the unlikely event of a disruption to an Availability Zone (AZ) that impairs access to your data. You can use the results of FIS experiments to verify your monitoring, test recovery processes, and improve application resilience. With FIS, you can disrupt connectivity to your S3 Express One Zone data in S3 directory buckets, helping you validate application resilience. During the FIS experiment, data plane requests made to directory buckets will timeout. This fault action is also included in the FIS AZ Availability: Power Interruption scenario, so you can test the resilience of your applications when an AZ event impacts multiple AWS services. You can use the updated FIS network disruption action for S3 Express One Zone data in all AWS Regions where the storage class is available. To get started with testing the resilience of applications that store data in S3 Express One Zone, you can use the AWS Management Console, AWS CLI, or FIS API. For pricing information, visit the FIS pricing page. To learn more, visit the AWS FIS user guide.  

You can now easily deliver task and email based customer experiences on your websites and applications using the new contact form option in the Amazon Connect communication widget. For example, you can add the communication widget to your website and give customers the ability to submit callback requests outside business hours or send emails through webforms.

Supervisors and managers can configure customer-facing forms using the drag and drop editor and generate code snippets for seamless website integration. This expanded capability gives customers more flexible engagement options while enabling you to manage all engagements through existing Amazon Connect workflows.

For region availability, please see the availability of Amazon Connect features by Region. To learn more, see our documentation. To learn more about Amazon Connect, the easy-to-use cloud contact center, visit the Amazon Connect website.

 

​You can now easily deliver task and email based customer experiences on your websites and applications using the new contact form option in the Amazon Connect communication widget. For example, you can add the communication widget to your website and give customers the ability to submit callback requests outside business hours or send emails through webforms. Supervisors and managers can configure customer-facing forms using the drag and drop editor and generate code snippets for seamless website integration. This expanded capability gives customers more flexible engagement options while enabling you to manage all engagements through existing Amazon Connect workflows. For region availability, please see the availability of Amazon Connect features by Region. To learn more, see our documentation. To learn more about Amazon Connect, the easy-to-use cloud contact center, visit the Amazon Connect website.  

Amazon Connect now supports recurring activities in agent schedules, making it easier for you to add repeating events in a few clicks. With this launch, you can now schedule activities such as daily stand-up at 8 a.m. or team meeting every Monday at 9 a.m. as a series that automatically gets added to agent schedules. You can schedule these as individual recurring series for each agent or a shared recurring series across multiple agents. This launch eliminates the need for manually creating each occurrence as a separate activity and ensures timely addition of activities to agent schedules, thus improving manager productivity and ensuring agent schedules are up to date.

This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about Amazon Connect agent scheduling, click here.

 

​Amazon Connect now supports recurring activities in agent schedules, making it easier for you to add repeating events in a few clicks. With this launch, you can now schedule activities such as daily stand-up at 8 a.m. or team meeting every Monday at 9 a.m. as a series that automatically gets added to agent schedules. You can schedule these as individual recurring series for each agent or a shared recurring series across multiple agents. This launch eliminates the need for manually creating each occurrence as a separate activity and ensures timely addition of activities to agent schedules, thus improving manager productivity and ensuring agent schedules are up to date. This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about Amazon Connect agent scheduling, click here.  

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.