5/14/2025, 12:00:00 AM ~ 5/15/2025, 12:00:00 AM (UTC)
Recent Announcements
Amazon RDS for Oracle now supports the April 2025 Release Update (RU)
Amazon Relational Database Service (Amazon RDS) for Oracle now supports the April 2025 Release Update (RU) for Oracle Database versions 19c and 21c. These RUs include bug and security fixes and are available for RDS for Oracle Standard Edition 2 and Enterprise Edition. Review the Oracle release notes for April RU for details.\n We recommend upgrading to this RU as it includes security fixes. You can upgrade with just a few clicks in the Amazon RDS Management Console or by using the AWS SDK or CLI. You can also enable auto minor version upgrade (AmVU) to automatically upgrade your database instances. Learn more about upgrading your database instances from the Amazon RDS User Guide. This new minor version is available in all AWS regions where Amazon RDS for Oracle is available. See Amazon RDS for Oracle Pricing for pricing details and regional availability.
AWS Control Tower introduces account-level reporting for baseline APIs
AWS Control Tower customers can now programmatically view statuses for their governed accounts via baseline APIs. The AWS Control Tower baseline contains best practice configurations, controls, and resources required for governance. When you enable this baseline on an organizational unit (OU), member accounts within the OU are enrolled under governance.\n With this new experience, you can use baseline status to view enrollment for your accounts and use drift status to identify when account and OU baseline configurations are out of sync. In addition to seeing statuses for your accounts and OUs in the AWS Control Tower console, you can use the ListEnabledBaselines API to view statuses for your enabled baselines. To view statuses for individual accounts, use the “includeChildren” flag. You can filter by these statuses to view only the accounts and OUs which require your attention. These APIs include AWS CloudFormation support, allowing you to build automations to manage your OUs and accounts with infrastructure as code (IaC). To learn more about these APIs, review Baselines and API Reference in the AWS Control Tower User Guide. Baseline APIs and the newly launched reporting capabilities are available in all AWS Regions where AWS Control Tower is available. For a list of AWS Regions where AWS Control Tower is available, see the AWS Region Table.
Amazon Aurora MySQL 3.09 (compatible with MySQL 8.0.40) is now generally available
Starting today, Amazon Aurora MySQL - Compatible Edition 3 (with MySQL 8.0 compatibility) will support MySQL 8.0.40 through Aurora MySQL v3.09. In addition to several security enhancements and bug fixes, MySQL 8.0.40 contains enhancements that improve database availability when handling large number of tables and reduce InnoDB issues related to redo logging, and index handling.\n Aurora MySQL 3.09 includes performance enhancements to improve write throughput for 32xl and larger instances running on I/O-Optimized configuration. This release also contains improvements that increase the cross-region resiliency of Aurora Global Database secondary region clusters. For more details, refer to the Aurora MySQL 3.09 and MySQL 8.0.40 release notes. To upgrade to Aurora MySQL 3.09, you can initiate a minor version upgrade manually by modifying your DB cluster, or you can enable the “Auto minor version upgrade” option when creating or modifying a DB cluster. For upgrading a Global Database, you can refer to upgrading an Amazon Aurora global database guide. This 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 Amazon Web Services services. To get started with Amazon Aurora, take a look at our getting started page.
Amazon EC2 makes it easier to launch Windows instances with EC2 Fast Launch
Starting today, you can launch Windows instances using EC2 Fast Launch, without requiring a launch template or a default VPC.\n EC2 Fast Launch reduces the launch times of Windows instances using pre-provisioned snapshots. Previously, customers needed a launch template or a default VPC to enable EC2 Fast Launch for their Windows AMIs. With this update, you can enable EC2 Fast Launch with only the AMI ID. The updated EC2 Fast Launch is now available through the AWS Console, CLI, and SDK in all AWS Commercial Regions and AWS GovCloud Regions. To get started with EC2 Fast Launch and to learn more about this new streamlined configuration, please visit the EC2 Fast Launch User Guide.
Amazon Kinesis Data Streams expands IPv6 support to VPC endpoints
Amazon Kinesis Data Streams now allows customers to make API requests over Internet Protocol version 6 (IPv6) with dual-stack AWS PrivateLink interface Virtual Private Clouds (VPC) endpoints. This enhancement extends IPv6 compatibility, previously available only for public endpoints, to VPC endpoints across all AWS Regions. Dual-stack endpoints that have been validated under the Federal Information Processing Standard (FIPS) 140-3 program are also available.\n Kinesis Data Streams allows users to capture, process, and store data streams in real time at any scale. Customers can now leverage IPv6 connectivity for data-streaming workloads within their Virtual Private Clouds (VPCs). IPv6 support is crucial for organizations facing IPv4 address exhaustion or those required to support IPv6 for compliance reasons. This feature allows for seamless integration of Kinesis Data Streams with IPv6-only networks, simplifying network management and reducing the need for complex IPv4 to IPv6 translations. IPv6 support for VPC endpoints is now available in all AWS Regions, including commercial regions and AWS China regions operated by Sinnet and NWCD. See here for a full listing of our Regions and endpoints. To learn more about using Kinesis Data Streams with interface VPC endpoints, please refer to our Developer Guide. To learn more about AWS PrivateLink, see accessing AWS services through AWS PrivateLink.
Amazon RDS for Oracle now supports April 2025 Spatial Patch Bundle
Amazon Relational Database Service (Amazon RDS) for Oracle now supports the Spatial Patch Bundle (SPB) for the April 2025 Release Update (RU) for Oracle Database version 19c. This update delivers important fixes for Oracle Spatial and Graph functionality, helping ensure reliable and optimal performance for your spatial operations.\n You can now create new DB instances or upgrade existing ones to engine version ‘19.0.0.0.ru-2025-04.spb-1.r1’. The SPB engine version will be visible in the AWS Console by selecting the “Spatial Patch Bundle Engine Versions” checkbox in the engine version selector, making it simple to identify and implement the latest spatial patches for your database environment. To learn more about Oracle SPBs supported on Amazon RDS for each engine version, see the Amazon RDS for Oracle Release notes. For more information about the AWS Regions where Amazon RDS for Oracle is available, see the AWS Region table.
Customers running Amazon Aurora and RDS for PostgreSQL, MySQL, and MariaDB databases can now purchase Reserved Instances for Graviton4-based R8g and M8g instances. These instances provide larger sizes up to 48xlarge with an 8:1 ratio of memory to vCPU and the latest DDR5 memory. Graviton4-based instances deliver up to 40% performance improvement and 29% better price-performance compared to equivalent Graviton3-based instances.\n Reserved Instances offer significant savings over On-Demand rates with three flexible payment options: All Upfront providing the highest discount, Partial Upfront balancing between upfront and hourly payments, and No Upfront requiring no initial payment. Reserved Instances for 8th generation Graviton instances (R8g and M8g) offer deeper discounts as compared to the 7th generation Graviton instances (R7g and M7g), further improving the price-performance for these instances and enhancing cost-optimization opportunities. Reserved Instances provide instance size flexibility within the same family and automatically apply to both Single-AZ and Multi-AZ configurations, making them ideal for varying production workloads. These 1-year Reserved Instances are available for Aurora MySQL, Aurora PostgreSQL, RDS for MySQL, RDS for PostgreSQL, and RDS for MariaDB in all AWS regions where Graviton4-based instances are offered with On-Demand pricing. For information on specific engine versions that support these DB instance types, refer to Aurora and RDS documentation. To get started, purchase Reserved Instances through the AWS Management Console, AWS CLI, or AWS SDK. For detailed pricing information and purchase options, visit Aurora and RDS pricing pages. For additional questions related to Reserved Instances, refer to RDS FAQs.
Customers running Amazon Aurora and RDS for PostgreSQL, MySQL, and MariaDB databases can now purchase Reserved Instances for R7i and M7i instances. These instances are powered by custom 4th Generation Intel Xeon Scalable processors and provide larger sizes up to 48xlarge with an 8:1 ratio of memory to vCPU and the latest DDR5 memory.\n Reserved Instances offer significant savings over On-Demand rates with three flexible payment options: All Upfront providing the highest discount, Partial Upfront balancing between upfront and hourly payments, and No Upfront requiring no initial payment. Reserved Instances provide instance size flexibility within the same family and automatically apply to both Single-AZ and Multi-AZ configurations, making them ideal for varying production workloads. These 1-year Reserved Instances are available for Aurora MySQL, Aurora PostgreSQL, RDS for MySQL, RDS for PostgreSQL, and RDS for MariaDB in all AWS regions where R7i and M7i instances are offered with On-Demand pricing. For information on specific engine versions that support these DB instance types, refer to Aurora and RDS documentation. To get started, purchase Reserved Instances through the AWS Management Console, AWS CLI, or AWS SDK. For detailed pricing information and purchase options, visit Aurora and RDS pricing pages. For additional questions related to Reserved Instances, refer to RDS FAQs.
Amazon Bedrock Guardrails now supports cross-region inference
Amazon Bedrock Guardrails announces support for cross-region inference, an optional feature that enables customers to seamlessly manage traffic bursts by utilizing compute across different AWS regions.\n Bedrock Guardrails provides configurable safeguards to help detect and block harmful content and prompt attacks, define topics to deny and disallow specific topics, and helps redact personally identifiable information (PII) such as personal data from input prompts and model responses. Additionally, Bedrock Guardrails helps detect and block model hallucinations, and identify, correct, and explain factual claims in model responses using Automated Reasoning checks. Guardrails can be applied across any foundation model including those hosted with Amazon Bedrock, self-hosted models, and third-party models outside Bedrock using the ApplyGuardrail API, providing a consistent user experience and helping to standardize safety and privacy controls. By using cross-region inference, Amazon Bedrock Guardrails customers will be able to get consistent throughput and enhanced resilience during periods of peak demand. By opting in, customers no longer have to spend time and effort predicting demand fluctuations. Instead, cross-region inference dynamically routes traffic across multiple regions, ensuring optimal availability for each request and smoother performance during high-usage periods. There’s no additional routing cost for using cross-region inference with Amazon Bedrock Guardrails. Please find the list of supported regions here. To learn more about the feature and how to get started, refer to the technical documentation.
AWS HealthOmics now supports output mapping files for CWL workflows
Today, AWS HealthOmics announces enhancements to its Common Workflow Language (CWL) support by automatically generating comprehensive outputs.json mapping files for every workflow run. With this launch, HealthOmics now provides researchers and bioinformaticians with a complete catalog of all outputs generated by workflow runs along with their precise locations in Amazon S3. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows.\n The new output mapping capability simplifies downstream process automation and validation of run outputs, enabling more efficient data analysis pipelines. Customers can now easily track and access all workflow results without manual tracking or custom parsing scripts, saving time and reducing the possibility of errors when working with complex, multi-step bioinformatics workflows at scale. CWL output mapping files are now supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv). To learn more about AWS HealthOmics and this new feature, see the AWS HealthOmics documentation.
YouTube
AWS Black Belt Online Seminar (Japanese)
- AWS Database Migration Service Best Practices - Planning [AWS Black Belt]
- DR Strategy Thinking with AWS Backup #1 Basic Edition [AWS Black Belt]
AWS Blogs
AWS Japan Blog (Japanese)
- Build multi-architecture containers using GitHub Actions on AWS
- Leveraging Amazon Redshift Serverless’s Optimization Features
- Detailed explanation: Amazon EKS Auto Mode
- Enabling Direct-to-Consumer (D2C) Marketing with First-Party Data: Providing Personalized Experiences with Generative AI
AWS Compute Blog
AWS Database Blog
AWS DevOps & Developer Productivity Blog
Front-End Web & Mobile
AWS for Industries
AWS Machine Learning Blog
- Cost-effective AI image generation with PixArt-Σ inference on AWS Trainium and AWS Inferentia
- Customize DeepSeek-R1 671b model using Amazon SageMaker HyperPod recipes – Part 2
- Build a financial research assistant using Amazon Q Business and Amazon QuickSight for generative AI–powered insights