4/23/2025, 12:00:00 AM ~ 4/24/2025, 12:00:00 AM (UTC)

Recent Announcements

Amazon Redshift adds history mode support to 8 third-party SaaS applications

Amazon Redshift now supports history mode for zero-ETL integrations with eight third-party applications including Salesforce, ServiceNow, and SAP. This addition complements existing history mode support for Amazon Aurora PostgreSQL-compatible and MySQL-compatible, DynamoDB, and RDS for MySQL databases. The expansion enables you to track historical data changes without Extract, Transform, and Load (ETL) processes, simplifying data management across AWS and third-party applications.\n History Mode for zero-ETL integrations with third-party applications lets customers easily run advanced analytics on historical data from their applications, build comprehensive lookback reports, and perform trend analysis and data auditing across multiple zero-ETL data sources. This feature preserves the complete history of data changes without maintaining duplicate copies across various external data sources, allowing organizations to meet data retention requirements while significantly reducing storage needs and operational costs. Available for both existing and new integrations, history mode offers enhanced flexibility by allowing selective enabling of historical tracking for specific tables within third-party application integrations, giving businesses precise control over their data analysis and storage strategies. To learn more about history mode for zero-ETL integrations in Amazon Redshift and how it can benefit your data analytics workflows, visit the history mode documentation. To learn more about the supported third-party applications, visit the AWS Glue documentation. To get started with zero-ETL integrations, visit the getting started guides for Amazon Redshift.

Prompt Optimization in Amazon Bedrock now generally available

In November 2024, we launched Prompt Optimization in Amazon Bedrock to accelerate prompt creation and engineering for foundation models (FMs). Today, we’re announcing its general availability and pricing.\n Prompt engineering is the process of designing prompts to guide FMs to generate relevant responses. These prompts must be customized for each FM according to its best practices and guidelines, which is a time-consuming process that delays application development. With Prompt Optimization in Amazon Bedrock, you can now automatically rewrite prompts for better performance and more concise responses on Anthropic, Llama, Nova, DeepSeek, Mistral and Titan models. You can compare optimized prompts against original versions without deployment and save them in Amazon Bedrock Prompt Management for prompt lifecycle management. You can also use Prompt Optimization in Bedrock Playground, or directly via API. Prompt Optimization is now generally available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), South America (São Paulo). To get started, see the following resources:

Blog

Amazon Bedrock Pricing

Amazon Bedrock user guide

Amazon Bedrock API reference

Announcing AWS DMS Serverless automatic storage scaling

AWS Database Migration Service Serverless (AWS DMS Serverless) now offers storage scaling. With this enhancement you never have to worry about exceeding the DMS Serverless 100GB default replication storage capacity limit when processing very large transaction volumes or using detailed logging.\n You can now use AWS DMS Serverless for replicating even the highest of transaction volumes since there is no longer any storage capacity limits. AWS DMS Severless will automatically increase the storage for your replications any time the existing capacity reaches it limits. To learn more, see the AWS DMS Serverless storage capacity documentation. For AWS DMS regional availability, please refer to the AWS Region Table.

Amazon EC2 M8g instances now available in AWS US West (N. California) Region

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) M8g instances are available in AWS US West (N. California). These instances are powered by AWS Graviton4 processors and deliver up to 30% better performance compared to AWS Graviton3-based instances. Amazon EC2 M8g instances are built for general-purpose workloads, such as application servers, microservices, gaming servers, midsize data stores, and caching fleets. These instances are built on the AWS Nitro System, which offloads CPU virtualization, storage, and networking functions to dedicated hardware and software to enhance the performance and security of your workloads.\n AWS Graviton4-based Amazon EC2 instances deliver the best performance and energy efficiency for a broad range of workloads running on Amazon EC2. These instances offer larger instance sizes with up to 3x more vCPUs and memory compared to Graviton3-based Amazon M7g instances. AWS Graviton4 processors are up to 40% faster for databases, 30% faster for web applications, and 45% faster for large Java applications than AWS Graviton3 processors. M8g instances are available in 12 different instance sizes, including two bare metal sizes. They offer up to 50 Gbps enhanced networking bandwidth and up to 40 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS). To learn more, see Amazon EC2 M8g Instances. To explore how to migrate your workloads to Graviton-based instances, see AWS Graviton Fast Start program and Porting Advisor for Graviton. To get started, see the AWS Management Console.

AWS CodeBuild adds support for specifying EC2 instance type and configurable storage size

AWS CodeBuild now supports selecting an EC2 instance by name when using reserved capacity fleets. This enhancement also allows you to configure the amount of storage attached to each instance. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces ready-to-deploy software packages.\n You can select a compute type that is most suitable for your workload. Customize your build environment to match specific resource needs - whether that’s more CPU, memory, storage, faster network speed, or GPU support. This allows you to optimize cost and feedback cycle, resulting in improved developer productivity. The feature is now available in US East (N. Virginia), US East (Ohio), US West (Oregon), South America (Sao Paulo), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Mumbai), Europe (Ireland), and Europe (Frankfurt) where reserved capacity fleets are supported. To learn more about the instance types supported by reserved capacity fleets, please visit our documentation. To learn more about how to get started with CodeBuild, visit the AWS CodeBuild product page.

AWS announces upgrades to Amazon Q Business integrations for M365 Word and Outlook

Today, AWS announced upgrades to the Amazon Q Business integrations for M365 Word and Outlook to enhance their utility when performing document and email centered tasks. The upgrades include company knowledge access, image file attachment support, and an expanded prompt context window.\n With company knowledge support, users can now ask questions about their company’s indexed data directly through the Word and Outlook integrations allowing them to instantly find relevant information when drafting their documents and emails without needing to switch context. With image attachment support and an expanded context window, users can incorporate richer context through larger file attachments, images, and more detailed prompts to enhance the helpfulness of responses they receive from Amazon Q. These new features are available on the Amazon Q Business integrations for M365 Word and Outlook in all regions where Amazon Q Business is available. To learn more, visit the Amazon Q Business product page or review the documentation for detailed setup instructions and feature descriptions.

AWS Account Management now supports IAM-based account name updates

Today, we are introducing a new account management API that enables customers to update the account name via authorized IAM principals and more efficiently manage account names. This new API is added to the AWS account management APIs that enable AWS Organizations customers to centrally and programmatically manage primary email addresses, primary contact information, alternate contact information, and AWS Regions for their accounts. Using the new API, customers will no longer need root access to manage their account names, and they will be able to use authorized IAM principals within the account. Additionally, customers using AWS Organizations in all-features mode can now update member account names via authorized IAM principals in the management and delegated admin accounts, providing a centralized and secure way to manage account names across their organization at scale. Customers can also use the new API via the AWS Command Line Interface (CLI) and AWS Software Development Kit (SDK) to update account names.\n The ability to manage account names via authorized IAM principals is available at no additional charge in all commercial AWS Regions and the China Regions. To get started managing your account names via IAM principals, see the documentation.

Thinkbox Deadline 10.4.1 release

AWS Thinkbox Deadline 10.4.1 is now generally available with support for managing Deadline Cloud Usage-Based Licensing (UBL) together with your existing floating licenses. This release also brings support for Cinema4D 2025, After Effects 2025, Nuke 16, 3ds Max 2026, and Maya 2026.\n This release enhances how you can manage license limits when using a combination of floating licenses and Deadline Cloud Usage-Based Licensing (UBL) for third party software. By configuring limits for Deadline Cloud License Endpoints, you can now better control license usage across your render farm, helping teams scale more effectively while maintaining their existing license infrastructure. New updates in third-party integrations include support for Autodesk Maya 2026, Autodesk 3ds Max 2026, Maxon Cinema 4D 2025, Adobe After Effects 2025, and Foundry Nuke 16. These updates ensure compatibility with the latest versions of major content creation tools. To get started, download the latest version of Deadline 10 from here. For details on configuring Deadline Cloud License Endpoints, read our documentation.

Amazon EC2 I4g instances are now available in AWS Asia Pacific (Sydney) Region

Starting today, storage optimized Amazon Elastic Compute Cloud (EC2) I4g instances powered by AWS Graviton2 processors and 2nd generation AWS Nitro SSDs are now available in the AWS Asia Pacific (Sydney) Region.\n 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.

Customer Carbon Footprint Tool has new features and an updated methodology

Today, AWS announced three updates to enhance your experience with the Customer Carbon Footprint Tool (CCFT). These updates include easier access to carbon emissions data, visibility into emissions by AWS Region, and an updated, independently-verified methodology (v2.0).\n You can now export your monthly data through AWS’s Billing and Cost Management Data Exports service. This feature delivers carbon emissions estimates for all member accounts linked to their management account when using AWS Organizations. Additionally, you can now see your carbon emissions broken down by AWS Region (e.g., US East (Ohio)), so you can identify the Regions where your usage contributes the most to your carbon footprint to help you re-assess the regional distribution of your workloads. Lastly, the methodology v2.0 addresses the challenge of tracking and apportioning carbon emissions for customers using a wide array of AWS services across multiple regions. This methodology update leverages globally recognized standards to support the CCFT, including the GHG Protocol Corporate Standard, GHG Protocol Product Standard, ISO 14040/44 (LCA), ISO 14067, and ICT Sector Guidance. The CCFT provides an overview of the estimated carbon emissions associated with your usage of AWS products and services. Use easy-to-understand data visualizations to help measure the emissions from your AWS usage. For detailed information on the updates, please refer to the CCFT user guide, and the Data Exports user guide. Current AWS customers can visit the AWS Billing console to start using this tool now.

AWS Blogs

AWS Japan Blog (Japanese)

AWS Cloud Financial Management

AWS Cloud Operations Blog

Containers

AWS DevOps & Developer Productivity Blog

AWS Machine Learning Blog

AWS for M&E Blog

AWS Security Blog

Open Source Project

AWS CLI

AWS CDK

OpenSearch

Amplify UI