We are excited to announce that AWS Mainframe Modernization service is now available with greater control of managed runtime environments that run modernized mainframe applications.

For both refactored and replatformed applications, you can now export data sets to an Amazon S3 bucket. Optionally, you can choose to encrypt the exported data set. This export feature makes it easier to move data set across environments, or to archive data sets.

For applications refactored with AWS Blu Age, you can now restart a batch job at a specific step. This enables advanced batch operational and recovery procedures.

For applications replatformed with Rocket Software, you can now configure your managed runtime application using a base configuration compatible with Rocket Enterprise Server deployed on non-managed environments. This base configuration provides flexibility by allowing numerous advanced configuration parameters supported by Rocket Enterprise Server, such as CICS or IMS granular parameters. It also allows transferring exported configuration parameters from a Rocket Enterprise Server deployed on Amazon EC2 to an AWS Mainframe Modernization managed runtime application.

These new features are available in any AWS Region where AWS Mainframe Modernization managed runtime is already deployed. To learn more, please visit AWS Mainframe Modernization product and documentation pages.
 

 

​We are excited to announce that AWS Mainframe Modernization service is now available with greater control of managed runtime environments that run modernized mainframe applications. For both refactored and replatformed applications, you can now export data sets to an Amazon S3 bucket. Optionally, you can choose to encrypt the exported data set. This export feature makes it easier to move data set across environments, or to archive data sets. For applications refactored with AWS Blu Age, you can now restart a batch job at a specific step. This enables advanced batch operational and recovery procedures. For applications replatformed with Rocket Software, you can now configure your managed runtime application using a base configuration compatible with Rocket Enterprise Server deployed on non-managed environments. This base configuration provides flexibility by allowing numerous advanced configuration parameters supported by Rocket Enterprise Server, such as CICS or IMS granular parameters. It also allows transferring exported configuration parameters from a Rocket Enterprise Server deployed on Amazon EC2 to an AWS Mainframe Modernization managed runtime application. These new features are available in any AWS Region where AWS Mainframe Modernization managed runtime is already deployed. To learn more, please visit AWS Mainframe Modernization product and documentation pages.    

AWS announces the end of sale for AWS Elemental Link HD devices effective April 15, 2024. AWS Elemental Link UHD devices will continue to be available for purchase. To support HD content contribution workflows, Link UHD has now added HD ingest pricing, providing a seamless path for new deployments. Existing Link HD devices will continue to be supported, with Link UHD now serving as the recommended solution for both HD and UHD contribution workflows.

To enable HD pricing on Link UHD devices, you can configure the device’s input resolution on the Link device configuration page when the device is not actively streaming. The configuration option provides the flexibility to optimize costs when contributing HD content through Link UHD devices.

This feature is available immediately in all AWS Regions where Link UHD is supported. The input resolution configuration option is accessible through the AWS Management Console for all Link UHD devices.

To learn more about Link UHD’s HD ingest rates and configuration options, visit the AWS Elemental Link documentation. For detailed pricing information, see AWS Elemental Link input pricing.
 

 

​AWS announces the end of sale for AWS Elemental Link HD devices effective April 15, 2024. AWS Elemental Link UHD devices will continue to be available for purchase. To support HD content contribution workflows, Link UHD has now added HD ingest pricing, providing a seamless path for new deployments. Existing Link HD devices will continue to be supported, with Link UHD now serving as the recommended solution for both HD and UHD contribution workflows. To enable HD pricing on Link UHD devices, you can configure the device’s input resolution on the Link device configuration page when the device is not actively streaming. The configuration option provides the flexibility to optimize costs when contributing HD content through Link UHD devices. This feature is available immediately in all AWS Regions where Link UHD is supported. The input resolution configuration option is accessible through the AWS Management Console for all Link UHD devices. To learn more about Link UHD’s HD ingest rates and configuration options, visit the AWS Elemental Link documentation. For detailed pricing information, see AWS Elemental Link input pricing.    

Today, AWS announces that AWS Control Tower supports an additional 223 managed Config rules in Control Catalog for various use cases such as security, cost, durability, and operations. With this launch, you can now search, discover, enable and manage these additional rules directly from AWS Control Tower and govern more use cases for your multi-account environment.

To get started, in AWS Control Tower go to the Control Catalog and search for controls with the implementation filter AWS Config, you will then see all the AWS Config rules present in the Catalog. If you find rules that are relevant for you, you can then directly enable them from the AWS Control Tower console. You can also use ListControls, GetControl and EnableControl APIs. With this launch we’ve updated ListControls and GetControl APIs to support three new fields: Create Time, Severity and Implementation, that you can use when searching for a control in Control Catalog. For example, you can now programmatically find high severity Config rules which were created after your previous evaluation.

You can search the new AWS Config rules in all AWS Regions where AWS Control Tower is available, including AWS GovCloud (US). When you want to deploy a rule, reference the list of supported regions for that rule to see where it can be enabled. To learn more, visit the AWS Control Tower User Guide.

 

​Today, AWS announces that AWS Control Tower supports an additional 223 managed Config rules in Control Catalog for various use cases such as security, cost, durability, and operations. With this launch, you can now search, discover, enable and manage these additional rules directly from AWS Control Tower and govern more use cases for your multi-account environment. To get started, in AWS Control Tower go to the Control Catalog and search for controls with the implementation filter AWS Config, you will then see all the AWS Config rules present in the Catalog. If you find rules that are relevant for you, you can then directly enable them from the AWS Control Tower console. You can also use ListControls, GetControl and EnableControl APIs. With this launch we’ve updated ListControls and GetControl APIs to support three new fields: Create Time, Severity and Implementation, that you can use when searching for a control in Control Catalog. For example, you can now programmatically find high severity Config rules which were created after your previous evaluation. You can search the new AWS Config rules in all AWS Regions where AWS Control Tower is available, including AWS GovCloud (US). When you want to deploy a rule, reference the list of supported regions for that rule to see where it can be enabled. To learn more, visit the AWS Control Tower User Guide.  

Amazon Redshift Concurrency Scaling is now available in Israel (Tel Aviv) and Canada West (Calgary) regions.

Amazon Redshift Concurrency Scaling elastically scales query processing power to provide consistently fast performance for hundreds of concurrent queries. Concurrency Scaling resources are added to your Redshift cluster transparently in seconds, as concurrency increases, to process queries without wait time. Amazon Redshift customers with an active Redshift cluster earn up to one hour of free Concurrency Scaling credits, which is sufficient for the concurrency needs of most customers. Concurrency scaling allows you to specify usage control providing customers with predictability in their month-to-month cost, even during periods of fluctuating analytical demand.

To enable Concurrency Scaling, set the Concurrency Scaling Mode to Auto in your Amazon Web Services Management Console. You can allocate Concurrency Scaling usage to specific user groups and workloads, control the number of Concurrency Scaling clusters that can be used, and monitor Cloudwatch performance and usage metrics.

To learn more about concurrency scaling including regional-availability, see our documentation and pricing page.

 

​Amazon Redshift Concurrency Scaling is now available in Israel (Tel Aviv) and Canada West (Calgary) regions. Amazon Redshift Concurrency Scaling elastically scales query processing power to provide consistently fast performance for hundreds of concurrent queries. Concurrency Scaling resources are added to your Redshift cluster transparently in seconds, as concurrency increases, to process queries without wait time. Amazon Redshift customers with an active Redshift cluster earn up to one hour of free Concurrency Scaling credits, which is sufficient for the concurrency needs of most customers. Concurrency scaling allows you to specify usage control providing customers with predictability in their month-to-month cost, even during periods of fluctuating analytical demand. To enable Concurrency Scaling, set the Concurrency Scaling Mode to Auto in your Amazon Web Services Management Console. You can allocate Concurrency Scaling usage to specific user groups and workloads, control the number of Concurrency Scaling clusters that can be used, and monitor Cloudwatch performance and usage metrics. To learn more about concurrency scaling including regional-availability, see our documentation and pricing page.  

On Apr 15, 2025 Amazon announced quarterly security and critical updates for Amazon Corretto Long-Term Supported (LTS) and Feature Release (FR) versions of OpenJDK. Corretto 24.0.1, 21.0.7, 17.0.15, 11.0.27, 8u452 are now available for download. Amazon Corretto is a no-cost, multi-platform, production-ready distribution of OpenJDK.

Click on the Corretto home page to download Corretto 8, Corretto 11, Corretto 17, Corretto 21, or Corretto 24. You can also get the updates on your Linux system by configuring a Corretto Apt or Yum repo.

Feedback is welcomed!

 

​On Apr 15, 2025 Amazon announced quarterly security and critical updates for Amazon Corretto Long-Term Supported (LTS) and Feature Release (FR) versions of OpenJDK. Corretto 24.0.1, 21.0.7, 17.0.15, 11.0.27, 8u452 are now available for download. Amazon Corretto is a no-cost, multi-platform, production-ready distribution of OpenJDK. Click on the Corretto home page to download Corretto 8, Corretto 11, Corretto 17, Corretto 21, or Corretto 24. You can also get the updates on your Linux system by configuring a Corretto Apt or Yum repo. Feedback is welcomed!  

Starting today, we are making it easier for customers to understand their inter-availability zone (AZ) VPC Peering usage within the same AWS Region by introducing a new usage type in their bill. These changes won’t affect customers’ charges and will help them easily understand their VPC Peering costs, enabling them to choose the right architecture based on cost, performance, and ease of management.

VPC Peering is an Amazon VPC feature that allows customers to establish networking connection between two VPCs, helping them route traffic between two VPCs using private IPv4 or IPv6 addresses. Previously, VPC Peering usage was reported under the intra-regional Data Transfer usage, making it difficult for customers to understand their VPC Peering usage and charges. With this launch, customers can now view their VPC Peering usage using the new usage type “Region_Name-VpcPeering-In/Out-Bytes” in Cost Explorer or Cost and Usage Report. Customers do not need to make any changes to their existing VPC Peering connections to benefit from this change, as these changes will be automatically applied.

There are no changes to the pricing for data transferred over VPC Peering connections. These changes will apply to all AWS commercial and the AWS Gov Cloud (US) Regions.
 

 

​Starting today, we are making it easier for customers to understand their inter-availability zone (AZ) VPC Peering usage within the same AWS Region by introducing a new usage type in their bill. These changes won’t affect customers’ charges and will help them easily understand their VPC Peering costs, enabling them to choose the right architecture based on cost, performance, and ease of management. VPC Peering is an Amazon VPC feature that allows customers to establish networking connection between two VPCs, helping them route traffic between two VPCs using private IPv4 or IPv6 addresses. Previously, VPC Peering usage was reported under the intra-regional Data Transfer usage, making it difficult for customers to understand their VPC Peering usage and charges. With this launch, customers can now view their VPC Peering usage using the new usage type “Region_Name-VpcPeering-In/Out-Bytes” in Cost Explorer or Cost and Usage Report. Customers do not need to make any changes to their existing VPC Peering connections to benefit from this change, as these changes will be automatically applied. There are no changes to the pricing for data transferred over VPC Peering connections. These changes will apply to all AWS commercial and the AWS Gov Cloud (US) Regions.    

Starting today, Amazon Elastic Compute Cloud (EC2) I4g storage-optimized instances powered by AWS Graviton2 processors and 2nd generation AWS Nitro SSDs are now available in the South America (Sao Paulo) region.

I4g instances are optimized for workloads performing a high mix of random read/write operations and requiring very low I/O latency and high compute performance, such as transactional databases (MySQL, and PostgreSQL), real-time databases including in-memory databases, NoSQL databases, time-series databases (Clickhouse, Apache Druid, MongoDB) and real-time analytics such as Apache Spark.

Get started with I4g instances by visiting the AWS Management Console, AWS Command Line Interface (CLI), or AWS SDKs. To learn more, visit the I4g instances page.

 

 

 

​Starting today, Amazon Elastic Compute Cloud (EC2) I4g storage-optimized instances powered by AWS Graviton2 processors and 2nd generation AWS Nitro SSDs are now available in the South America (Sao Paulo) region.
I4g instances are optimized for workloads performing a high mix of random read/write operations and requiring very low I/O latency and high compute performance, such as transactional databases (MySQL, and PostgreSQL), real-time databases including in-memory databases, NoSQL databases, time-series databases (Clickhouse, Apache Druid, MongoDB) and real-time analytics such as Apache Spark. Get started with I4g instances by visiting the AWS Management Console, AWS Command Line Interface (CLI), or AWS SDKs. To learn more, visit the I4g instances page.
 
   

Gateway Load Balancer (GWLB) now supports Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum bandwidth capacity for your load balancer, complementing its existing ability to auto-scale based on your traffic pattern.

Gateway Load Balancer helps you deploy, scale, and manage third-party virtual appliances. With this feature, you can reserve a guaranteed capacity for anticipated traffic surge. The LCU reservation is ideal for scenarios such as onboarding and migrating new workload to your GWLB gated services without the need to wait for organic scaling, or maintaining a minimum bandwidth capacity for your firewall applications to meet specific SLA or compliance requirements. When using this feature, you pay only for the reserved LCUs and any additional usage above the reservation. You can easily configure this feature through the ELB console or API.

The feature is available for GWLB in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm) AWS Regions. This feature is not supported on Gateway Load Balancer Endpoint (GWLBe). To learn more, please refer to the GWLB documentation.

 

​Gateway Load Balancer (GWLB) now supports Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum bandwidth capacity for your load balancer, complementing its existing ability to auto-scale based on your traffic pattern. Gateway Load Balancer helps you deploy, scale, and manage third-party virtual appliances. With this feature, you can reserve a guaranteed capacity for anticipated traffic surge. The LCU reservation is ideal for scenarios such as onboarding and migrating new workload to your GWLB gated services without the need to wait for organic scaling, or maintaining a minimum bandwidth capacity for your firewall applications to meet specific SLA or compliance requirements. When using this feature, you pay only for the reserved LCUs and any additional usage above the reservation. You can easily configure this feature through the ELB console or API. The feature is available for GWLB in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm) AWS Regions. This feature is not supported on Gateway Load Balancer Endpoint (GWLBe). To learn more, please refer to the GWLB documentation.  

Starting today, Amazon S3 Express One Zone has reduced pricing for storage by 31%, PUT requests by 55%, and GET requests by 85%. In addition, S3 Express One Zone has reduced its per-gigabyte data upload and retrieval charges by 60% and now applies these charges to all bytes rather than just portions of requests exceeding 512 kilobytes.

Amazon S3 Express One Zone is a high-performance, single-Availability Zone storage class purpose-built to deliver consistent single-digit millisecond data access for your most frequently accessed data and latency-sensitive applications, such as machine learning training, analytics for live streaming events, and market analysis for financial services.

These pricing changes apply to S3 Express One Zone in all AWS Regions where the storage class is available. For updated pricing information, visit the S3 pricing page. To learn more about these pricing reductions, read the AWS News Blog, and to learn more about the S3 Express One Zone storage class, visit the product page and S3 User Guide.
 

 

​Starting today, Amazon S3 Express One Zone has reduced pricing for storage by 31%, PUT requests by 55%, and GET requests by 85%. In addition, S3 Express One Zone has reduced its per-gigabyte data upload and retrieval charges by 60% and now applies these charges to all bytes rather than just portions of requests exceeding 512 kilobytes. Amazon S3 Express One Zone is a high-performance, single-Availability Zone storage class purpose-built to deliver consistent single-digit millisecond data access for your most frequently accessed data and latency-sensitive applications, such as machine learning training, analytics for live streaming events, and market analysis for financial services. These pricing changes apply to S3 Express One Zone in all AWS Regions where the storage class is available. For updated pricing information, visit the S3 pricing page. To learn more about these pricing reductions, read the AWS News Blog, and to learn more about the S3 Express One Zone storage class, visit the product page and S3 User Guide.    

Amazon Bedrock Knowledge Bases now extends support for hybrid search to knowledge bases created using Amazon Aurora PostgreSQL and MongoDB Atlas vector stores. This capability, which can improve relevance of the results, previously only worked with Opensearch Serverless and Opensearch Managed Clusters in Bedrock Knowledge Bases.

Retrieval augmented generation (RAG) applications use semantic search, based on vectors, to search unstructured text. These vectors are created using foundation models to capture contextual and linguistic meaning within data to answer human-like questions. Hybrid search merges semantic and full-text search methods, executing dual queries and combining results. This approach improves results relevance by retrieving documents that match conceptually from semantic search or that contain specific keywords found in full-text search. The wider search scope enhances result quality, particularly for keyword-based queries.

You can enable hybrid search through the Knowledge Base APIs or through the Bedrock console. In the console, you can select hybrid search as your preferred search option within Knowledge Bases, or choose the default search option to use semantic search only. Hybrid search with Aurora PostgreSQL is available in all AWS Regions where Bedrock Knowledge Bases is available, excluding Europe (Zurich) and GovCloud (US) Regions. Hybrid search with Mongo DB Atlas is available in the US West (Oregon) and US East (N. Virginia) AWS Regions. To learn more, refer to Bedrock Knowledge Bases documentation. To get started, visit the Amazon Bedrock console.

 

​Amazon Bedrock Knowledge Bases now extends support for hybrid search to knowledge bases created using Amazon Aurora PostgreSQL and MongoDB Atlas vector stores. This capability, which can improve relevance of the results, previously only worked with Opensearch Serverless and Opensearch Managed Clusters in Bedrock Knowledge Bases. Retrieval augmented generation (RAG) applications use semantic search, based on vectors, to search unstructured text. These vectors are created using foundation models to capture contextual and linguistic meaning within data to answer human-like questions. Hybrid search merges semantic and full-text search methods, executing dual queries and combining results. This approach improves results relevance by retrieving documents that match conceptually from semantic search or that contain specific keywords found in full-text search. The wider search scope enhances result quality, particularly for keyword-based queries. You can enable hybrid search through the Knowledge Base APIs or through the Bedrock console. In the console, you can select hybrid search as your preferred search option within Knowledge Bases, or choose the default search option to use semantic search only. Hybrid search with Aurora PostgreSQL is available in all AWS Regions where Bedrock Knowledge Bases is available, excluding Europe (Zurich) and GovCloud (US) Regions. Hybrid search with Mongo DB Atlas is available in the US West (Oregon) and US East (N. Virginia) AWS Regions. To learn more, refer to Bedrock Knowledge Bases documentation. To get started, visit the Amazon Bedrock console.