AWS memory optimized R6id database instances are now generally available for Amazon RDS for PostgreSQL, MySQL, and MariaDB in the Tel Aviv region. R6gd instances are now supported for Amazon RDS for PostgreSQL, MySQL, and MariaDB in Asia Pacific (Osaka), and EU (Spain, Zurich) regions.

 AWS Graviton2-based instances provide up to 40% performance improvement over R5-based instances of equivalent sizes on Amazon Aurora and Amazon RDS databases, depending on database engine, version, and workload. R6gd instances also deliver local NVMe-based block level storage for low latency local storage. Memory-optimized R6id instances offer 58% higher TB storage per vCPU and 15% better price performance when compared with R5d instances.

You can easily launch R6gd or R6id database instances through the Amazon RDS Management Console or by using the AWS Command Line Interface (CLI). For detailed information about specific engine versions that support these database instance types, please refer to the Aurora and RDS documentation. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page.

 

​AWS memory optimized R6id database instances are now generally available for Amazon RDS for PostgreSQL, MySQL, and MariaDB in the Tel Aviv region. R6gd instances are now supported for Amazon RDS for PostgreSQL, MySQL, and MariaDB in Asia Pacific (Osaka), and EU (Spain, Zurich) regions.  AWS Graviton2-based instances provide up to 40% performance improvement over R5-based instances of equivalent sizes on Amazon Aurora and Amazon RDS databases, depending on database engine, version, and workload. R6gd instances also deliver local NVMe-based block level storage for low latency local storage. Memory-optimized R6id instances offer 58% higher TB storage per vCPU and 15% better price performance when compared with R5d instances. You can easily launch R6gd or R6id database instances through the Amazon RDS Management Console or by using the AWS Command Line Interface (CLI). For detailed information about specific engine versions that support these database instance types, please refer to the Aurora and RDS documentation. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page.  

Amazon Connect now enables you to apply tag-based access control to cases, giving administrators more control over who can view and manage case data. With this capability, you can associate tags with case templates and configure security profiles to control which users can access cases that include specific tags. For example, you can tag fraud-related cases and restrict access so that only users assigned to a fraud security profile can view or edit those cases, helping you enforce internal controls and data access policies.

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 now enables you to apply tag-based access control to cases, giving administrators more control over who can view and manage case data. With this capability, you can associate tags with case templates and configure security profiles to control which users can access cases that include specific tags. For example, you can tag fraud-related cases and restrict access so that only users assigned to a fraud security profile can view or edit those cases, helping you enforce internal controls and data access policies. 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.  

AWS Deadline Cloud now supports editing job names and descriptions after submission. This new feature makes it easier to organize and identify jobs after submission by updating names or adding useful tracking details in the description field.

Job names and descriptions are critical metadata for organizing and understanding between users and projects, often tracking things like shot and sequence number across systems. Previously they could only be set at job creation during submission, being able to edit them after submission allows you to fix issues in naming as well as add key tracking information to the job description for other users.

You can edit job names and descriptions using the AWS SDK, Deadline client, and Deadline Monitor. To learn more see the AWS Deadline Cloud documentation.

 

​AWS Deadline Cloud now supports editing job names and descriptions after submission. This new feature makes it easier to organize and identify jobs after submission by updating names or adding useful tracking details in the description field. Job names and descriptions are critical metadata for organizing and understanding between users and projects, often tracking things like shot and sequence number across systems. Previously they could only be set at job creation during submission, being able to edit them after submission allows you to fix issues in naming as well as add key tracking information to the job description for other users. You can edit job names and descriptions using the AWS SDK, Deadline client, and Deadline Monitor. To learn more see the AWS Deadline Cloud documentation.  

AWS Network Firewall now provides visibility into generative AI (GenAI) application traffic and supports traffic filtering based on web categories. This new capability simplifies governance by enabling you to identify and control access to GenAI services, social media platforms, streaming sites, and other web categories directly within your firewall rules using pre-defined URL categories.

This approach of inspecting traffic based on URL categories helps security and compliance teams enforce consistent policies across their AWS environments while providing visibility into usage of emerging technologies like GenAI. You can now easily block access to inappropriate or high-risk domains, restrict GenAI tool usage to approved services, and meet regulatory requirements—all while reducing operational overhead. When combined with AWS Network Firewall’s TLS inspection feature, you can inspect the full URL path using category-based rules for even more granular control.

This feature is available in all AWS commercial regions where AWS Network Firewall is supported.

To learn more about URL category filtering in AWS Network Firewall, visit AWS Network Firewall product page and service documentation. You can get started by updating your stateful rule groups in the AWS Management Console, AWS CLI, or AWS SDKs. 

 

​AWS Network Firewall now provides visibility into generative AI (GenAI) application traffic and supports traffic filtering based on web categories. This new capability simplifies governance by enabling you to identify and control access to GenAI services, social media platforms, streaming sites, and other web categories directly within your firewall rules using pre-defined URL categories. This approach of inspecting traffic based on URL categories helps security and compliance teams enforce consistent policies across their AWS environments while providing visibility into usage of emerging technologies like GenAI. You can now easily block access to inappropriate or high-risk domains, restrict GenAI tool usage to approved services, and meet regulatory requirements—all while reducing operational overhead. When combined with AWS Network Firewall’s TLS inspection feature, you can inspect the full URL path using category-based rules for even more granular control. This feature is available in all AWS commercial regions where AWS Network Firewall is supported. To learn more about URL category filtering in AWS Network Firewall, visit AWS Network Firewall product page and service documentation. You can get started by updating your stateful rule groups in the AWS Management Console, AWS CLI, or AWS SDKs.   

AWS announces advanced printer redirection for Amazon WorkSpaces Personal, enabling Windows users to access the full feature set of their printers from their virtual desktop environments. With this feature, customers can now use printer-specific capabilities such as double-sided printing, paper tray selection, finishing options (stapling, hole-punching), and color management directly from their Windows WorkSpaces.

Advanced printer redirection addresses the need for specialized printing features that require printer-specific drivers rather than generic drivers. This capability is ideal for organizations with users who need advanced printing features for professional documents, labels, or specialized output. The feature includes configurable driver validation modes (exact match, partial match, or name-only matching) to balance compatibility with feature support, allowing administrators to optimize for their specific environment. When matching drivers are not found, WorkSpaces automatically falls back to basic printing mode, ensuring users can always print.

This feature is available in all AWS Regions where Amazon WorkSpaces Personal is offered. Advanced printer redirection is supported on Windows WorkSpaces with Windows clients only, and requires WorkSpaces Agent version 2.2.0.2116 or later and Windows client version 5.31 or later. Matching printer drivers must be installed on both the WorkSpace and the client device.

For more information about advanced printer redirection in Amazon WorkSpaces, see Configure Printer Support for DCV in the Amazon WorkSpaces Administration Guide, or visit the Amazon WorkSpaces page to learn more about virtual desktop solutions from AWS.

 

​AWS announces advanced printer redirection for Amazon WorkSpaces Personal, enabling Windows users to access the full feature set of their printers from their virtual desktop environments. With this feature, customers can now use printer-specific capabilities such as double-sided printing, paper tray selection, finishing options (stapling, hole-punching), and color management directly from their Windows WorkSpaces.
Advanced printer redirection addresses the need for specialized printing features that require printer-specific drivers rather than generic drivers. This capability is ideal for organizations with users who need advanced printing features for professional documents, labels, or specialized output. The feature includes configurable driver validation modes (exact match, partial match, or name-only matching) to balance compatibility with feature support, allowing administrators to optimize for their specific environment. When matching drivers are not found, WorkSpaces automatically falls back to basic printing mode, ensuring users can always print.
This feature is available in all AWS Regions where Amazon WorkSpaces Personal is offered. Advanced printer redirection is supported on Windows WorkSpaces with Windows clients only, and requires WorkSpaces Agent version 2.2.0.2116 or later and Windows client version 5.31 or later. Matching printer drivers must be installed on both the WorkSpace and the client device.
For more information about advanced printer redirection in Amazon WorkSpaces, see Configure Printer Support for DCV in the Amazon WorkSpaces Administration Guide, or visit the Amazon WorkSpaces page to learn more about virtual desktop solutions from AWS.  

AWS Marketplace now offers a self-service listing experience for sellers listing Amazon Machine Image (AMI) products with FPGA (Field Programmable Gate Array) images. This new capability eliminates the previous dependency on manual Product Load Forms and accelerates time-to-market for AWS partners that offer specialized hardware accelerators using FPGA technology on supported Amazon F2 instance types.

With this launch, sellers can now create and manage AMIs with Amazon FPGA images using a new UI experience or programmatically through the AWS Marketplace Catalog API. During listing creation, sellers are guided through a step-by-step workflow to fill in required information about their listings including up to 15 Amazon FPGA images. The self-service experience includes comprehensive inline validation and error messages to help sellers identify and resolve configuration issues before submission, streamlining the publishing process and improving speed to market.

To learn more, see the AWS Marketplace Seller Guide and the AWS Marketplace Catalog API guide. To get started, visit the server product page in the AWS Marketplace Management Portal.

 

​AWS Marketplace now offers a self-service listing experience for sellers listing Amazon Machine Image (AMI) products with FPGA (Field Programmable Gate Array) images. This new capability eliminates the previous dependency on manual Product Load Forms and accelerates time-to-market for AWS partners that offer specialized hardware accelerators using FPGA technology on supported Amazon F2 instance types. With this launch, sellers can now create and manage AMIs with Amazon FPGA images using a new UI experience or programmatically through the AWS Marketplace Catalog API. During listing creation, sellers are guided through a step-by-step workflow to fill in required information about their listings including up to 15 Amazon FPGA images. The self-service experience includes comprehensive inline validation and error messages to help sellers identify and resolve configuration issues before submission, streamlining the publishing process and improving speed to market. To learn more, see the AWS Marketplace Seller Guide and the AWS Marketplace Catalog API guide. To get started, visit the server product page in the AWS Marketplace Management Portal.  

AWS IAM Identity Center now supports Internet Protocol version 6 (IPv6) through new dual-stack endpoints. Customers can now connect to AWS IAM Identity Center using IPv6, IPv4, or dual-stack clients. The existing AWS IAM Identity Center endpoints supporting IPv4 remain available for backward compatibility.

IAM Identity Center allows customers to enable workforce access to AWS managed applications and AWS accounts. When your client, such as a browsers or an application, makes a request to a dual-stack endpoint, the endpoint resolves to an IPv4 or IPv6 address, depending on the protocol used by your network and client. This launch helps you meet IPv6 compliance requirements, and minimize the need for complex NAT infrastructure.

IPv6 support is available in all AWS Regions where IAM Identity Center is available, except the AWS GovCloud (US) Regions and the Taipei Region. To learn more, visit the IAM Identity Center User Guide.

 

​AWS IAM Identity Center now supports Internet Protocol version 6 (IPv6) through new dual-stack endpoints. Customers can now connect to AWS IAM Identity Center using IPv6, IPv4, or dual-stack clients. The existing AWS IAM Identity Center endpoints supporting IPv4 remain available for backward compatibility. IAM Identity Center allows customers to enable workforce access to AWS managed applications and AWS accounts. When your client, such as a browsers or an application, makes a request to a dual-stack endpoint, the endpoint resolves to an IPv4 or IPv6 address, depending on the protocol used by your network and client. This launch helps you meet IPv6 compliance requirements, and minimize the need for complex NAT infrastructure. IPv6 support is available in all AWS Regions where IAM Identity Center is available, except the AWS GovCloud (US) Regions and the Taipei Region. To learn more, visit the IAM Identity Center User Guide.  

Amazon Lightsail now offers new Node.js, LAMP, and Ruby on Rails blueprints. These new blueprint have Instance Metadata Service Version 2 (IMDSv2) enforced by default, and support IPv6-only instances. With just a few clicks, you can create a Lightsail virtual private server (VPS) of your preferred size with Node.js, LAMP, or Ruby on Rails preinstalled.

With Lightsail, you can easily get started on the cloud by choosing a blueprint and an instance bundle to build your web application. Lightsail instance bundles include instances preinstalled with your preferred operating system, storage, and monthly data transfer allowance, giving you everything you need to get up and running quickly.

These new blueprints are now available in all AWS Regions where Lightsail is available. For more information on blueprints supported on Lightsail, see Lightsail documentation. For more information on pricing, or to get started with your free trial, click here.

 

​Amazon Lightsail now offers new Node.js, LAMP, and Ruby on Rails blueprints. These new blueprint have Instance Metadata Service Version 2 (IMDSv2) enforced by default, and support IPv6-only instances. With just a few clicks, you can create a Lightsail virtual private server (VPS) of your preferred size with Node.js, LAMP, or Ruby on Rails preinstalled. With Lightsail, you can easily get started on the cloud by choosing a blueprint and an instance bundle to build your web application. Lightsail instance bundles include instances preinstalled with your preferred operating system, storage, and monthly data transfer allowance, giving you everything you need to get up and running quickly. These new blueprints are now available in all AWS Regions where Lightsail is available. For more information on blueprints supported on Lightsail, see Lightsail documentation. For more information on pricing, or to get started with your free trial, click here.  

Amazon Bedrock now supports a 1-hour time-to-live (TTL) option for prompt caching for select Anthropic Claude models. With this update, you can extend the persistence of cached prompt prefixes from the default 5 minutes to 1 hour, improving cost efficiency and performance for long-running agentic workflows and multi-turn conversations.

Previously, cached content remained active for a fixed 5-minute window and refreshed when reused. With the new 1-hour TTL option, you can maintain context for users who interact less frequently, or for complex agents that require more time between steps—such as tool use, retrieval, and orchestration. The 1-hour TTL is also useful for longer sessions and batch processing where you want cached content to persist across extended periods.

1-hour TTL prompt caching is generally available for Anthropic’s Claude Sonnet 4.5, Claude Haiku 4.5, and Claude Opus 4.5 in all commercial AWS Regions and AWS GovCloud (US) Regions where these models are available. The 1-hour cache is billed at a different rate than the standard 5-minute cache. To learn more, refer to the Amazon Bedrock documentation and Amazon Bedrock Pricing page.

 

​Amazon Bedrock now supports a 1-hour time-to-live (TTL) option for prompt caching for select Anthropic Claude models. With this update, you can extend the persistence of cached prompt prefixes from the default 5 minutes to 1 hour, improving cost efficiency and performance for long-running agentic workflows and multi-turn conversations. Previously, cached content remained active for a fixed 5-minute window and refreshed when reused. With the new 1-hour TTL option, you can maintain context for users who interact less frequently, or for complex agents that require more time between steps—such as tool use, retrieval, and orchestration. The 1-hour TTL is also useful for longer sessions and batch processing where you want cached content to persist across extended periods. 1-hour TTL prompt caching is generally available for Anthropic’s Claude Sonnet 4.5, Claude Haiku 4.5, and Claude Opus 4.5 in all commercial AWS Regions and AWS GovCloud (US) Regions where these models are available. The 1-hour cache is billed at a different rate than the standard 5-minute cache. To learn more, refer to the Amazon Bedrock documentation and Amazon Bedrock Pricing page.  

Amazon Managed Grafana is now available in both AWS GovCloud (US-West) and AWS GovCloud (US-East) Regions, enabling government customers and regulated industries to securely visualize and analyze their operational data while meeting stringent compliance requirements. Amazon Managed Grafana is a fully managed service based on open-source Grafana that makes it easier for you to visualize and analyze your operational data at scale.

All Amazon Managed Grafana features are supported in AWS GovCloud (US) Regions except for Enterprise plugins. To get started with Amazon Managed Grafana, visit the AWS Console and Amazon Managed Grafana user guide. To learn more about Amazon Managed Grafana, visit the product page and pricing page.

 

​Amazon Managed Grafana is now available in both AWS GovCloud (US-West) and AWS GovCloud (US-East) Regions, enabling government customers and regulated industries to securely visualize and analyze their operational data while meeting stringent compliance requirements. Amazon Managed Grafana is a fully managed service based on open-source Grafana that makes it easier for you to visualize and analyze your operational data at scale. All Amazon Managed Grafana features are supported in AWS GovCloud (US) Regions except for Enterprise plugins. To get started with Amazon Managed Grafana, visit the AWS Console and Amazon Managed Grafana user guide. To learn more about Amazon Managed Grafana, visit the product page and pricing page.