Amazon CloudWatch now supports ingesting Security Hub CSPM findings with organization-wide enablement

Amazon CloudWatch now supports ingesting AWS Security Hub CSPM findings, enabling customers to centrally analyze and monitor security findings directly in CloudWatch Logs. Security Hub CSPM findings are supported in AWS Security Finding Format (ASFF) and Open Cybersecurity Schema Framework (OCSF) format using CloudWatch Pipelines, providing standardized security data ingestion. Customers can now use CloudWatch Logs Insights to query findings, create metric filters for monitoring, and leverage Amazon S3 Tables integration for advanced analytics, helping security teams identify and respond to threats faster across their AWS environment.
With today’s launch, customers can automatically enable Security Hub findings delivery to CloudWatch Logs using CloudWatch enablement rules that apply to the entire organization or specific accounts, to standardize security monitoring coverage. For example, a security team can create an enablement rule to automatically send Security Hub findings to CloudWatch Logs for all production accounts, ensuring consistent visibility into security posture.
Security Hub findings to CloudWatch logs are available in all AWS commercial regions.
Security Hub findings are charged as tiered pricing when delivered to CloudWatch Logs. For pricing information, see the CloudWatch pricing page. To learn more about Security Hub findings in CloudWatch Logs and organization-level enablement, visit the Amazon CloudWatch documentation..
Quelle: aws.amazon.com

AWS DevOps Agent is now generally available

Now generally available, AWS DevOps Agent is your always-available operations teammate that resolves and proactively prevents incidents, optimizes application reliability and performance, and handles on-demand SRE tasks across AWS, multicloud, and on-prem environments. Building on the preview launch, DevOps Agent now adds new use cases, broader integrations, enhanced intelligence, and enterprise-ready features, including the ability to investigate applications in Azure and on-prem environments, add custom agent skills to extend capabilities, and create custom charts and reports for deeper operational insights. DevOps Agent investigates incidents and identifies operational improvements as an experienced teammate would: by learning your applications and their relationships, working with your observability tools, runbooks, code repositories, and CI/CD pipelines, and correlating telemetry, code, and deployment data. It autonomously triages incidents and guides teams to rapid resolution, reducing mean time to resolution (MTTR) from hours to minutes, while analyzing patterns across historical incidents to deliver actionable recommendations that prevent future outages. For the full list of AWS Regions where AWS DevOps Agent is available, visit the Regions list. Pricing details are available on the AWS DevOps Agent pricing page. AWS Support customers receive monthly DevOps Agent credits based on the prior month’s gross AWS Support spend: 100% for Unified Operations, 75% for Enterprise Support, or 30% for Business Support+. For many customers, this significantly reduces or eliminates DevOps Agent costs. For details, visit the support compare page. If you are a preview customer, review the migration documentation to ensure seamless access to new AWS DevOps Agent capabilities. To learn more, read the launch blog and see getting started.
Quelle: aws.amazon.com

Amazon ECS Managed Instances now supports Amazon EC2 instance store

Amazon ECS Managed Instances now supports Amazon EC2 instance store volumes as a data volume option for container workloads. You can now leverage instance store volumes on your ECS container instances instead of provisioning an Amazon EBS data volume, reducing storage costs and accelerating I/O performance for latency-sensitive workloads. Amazon ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead, dynamically scale EC2 instances to match your workload requirements, and continuously optimize task placement to reduce infrastructure costs. With today’s launch, you can enable local storage by configuring a custom ECS Managed Instances capacity provider and selecting the desired Amazon EC2 instance types that include instance store volumes. When an instance lacks instance store volumes or when local storage is disabled, Amazon ECS automatically provisions an Amazon EBS data volume. Support for instance store is available in all commercial AWS Regions where Amazon ECS Managed Instances is available. To learn more about local storage support, visit the documentation. To learn more about Amazon ECS Managed Instances, visit the feature page, documentation, and AWS News launch blog.
Quelle: aws.amazon.com

AWS Service Availability Updates

We’re announcing availability changes to the following AWS services and features. Services moving to Maintenance
Services moving to maintenance will no longer be accessible to new customers starting April 30, 2026. Customers already using these services and features can continue to do so. AWS will continue to operate and support these services and features. We recommend that customers learn about the changes in the product pages and documentation.

Amazon Application Recovery Controller (ARC) – Readiness Check Feature
Amazon Comprehend – Topic Modeling, Event Detection, and Prompt Safety Classification Features
Amazon Rekognition – Streaming Events and Batch Image Content Moderation Features
Amazon Simple Notification Service (SNS) – Message Data Protection (MDP) Feature
AWS App Runner
AWS Audit Manager
AWS CloudTrail Lake
AWS Glue – Ray Jobs Feature
AWS IoT FleetWise

Services entering Sunset
The following services are entering sunset, and we are announcing the date upon which we will end operations and support of the service. Customers using these services should click on the links below to understand the sunset timeline and begin planning migration to alternatives as recommended in the updated service web pages and documentation.

Amazon RDS Custom for Oracle
Amazon WorkMail
Amazon WorkSpaces Thin Client
AWS Service Management Connector

Services reaching End of Support
The following feature has reached end of support and is no longer available as of March 31, 2026.

Amazon Chime SDK – Proxy Sessions

For customers affected by these changes, we’ve prepared comprehensive migration guides, and our support teams are ready to assist with your transition. Visit AWS Product Lifecycle Page to learn more, and subscribe to the RSS feed for future updates. 
Quelle: aws.amazon.com

Aurora DSQL launches new connectors that simplify building .NET and Rust applications

Today we are announcing the release of Aurora DSQL connectors for .NET (Npgsql) and Rust (SQLx) that make it easy to build .NET and Rust applications on Aurora DSQL. The connectors streamline authentication and eliminate security risks associated with traditional user-generated passwords by automatically generating tokens for each connection, ensuring valid tokens are always used while maintaining full compatibility with existing Npgsql and SQLx features. The connectors handle IAM token generation, SSL configuration, and connection pooling, enabling customers to scale from simple scripts to production workloads without changing their authentication approach. They also provide opt-in optimistic concurrency control (OCC) retry with exponential backoff, custom IAM credential providers, and AWS profile support, making it easier to develop client retry logic and manage AWS credentials. To get started, visit the Connectors for Aurora DSQL documentation page. For code examples, visit our GitHub pages for the .NET connector and Rust connector. Get started with Aurora DSQL for free with the AWS Free Tier. To learn more about Aurora DSQL, visit the webpage.
Quelle: aws.amazon.com

AWS Deadline Cloud now supports new fleet scaling configurations for render farms

Today, AWS Deadline Cloud introduces three powerful new fleet scaling options that give you greater flexibility in managing your render farm capacity and performance: worker idle duration, standby worker count, and scale out rate. AWS Deadline Cloud is a fully managed service that helps creative teams efficiently manage and scale their rendering workloads in the cloud. These new options give you direct control over balancing rendering speed and efficiency. Configurable worker idle duration allows you to specify how long workers remain available after completing a job, eliminating wait times between job submissions and speeding up artist’s iteration workflow. Standby worker count maintains a pool of pre-warmed, idle workers that are immediately available at job submission so your renders start right away. Scale out rate lets you configure how quickly your fleet scales, up to 500 workers per minute, giving you the control you need to match your infrastructure needs.
These flexible scaling controls are now available in AWS Deadline Cloud. To learn more, visit the AWS Deadline Cloud documentation.
Quelle: aws.amazon.com

Amazon Athena launches Capacity Reservations in additional regions

Amazon Athena now offers Capacity Reservations in additional commercial AWS Regions. Capacity Reservations give you dedicated serverless capacity for your most important workloads. When you use Capacity Reservations, your queries run in isolation from other workloads in your account, and you control how many queries run concurrently.
Capacity Reservations is now available in US West (N. California), Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Thailand), Asia Pacific (Taipei), Canada (Central), Canada West (Calgary), Europe (Frankfurt), Europe (London), Europe (Milan), Europe (Paris), Europe (Zurich), and Mexico (Central). To learn more, see Manage query processing capacity in the Athena User Guide.
Quelle: aws.amazon.com

AWS HealthOmics introduces VPC-connected workflows

AWS HealthOmics announces VPC-connected workflows, giving customers the ability to run bioinformatics pipelines that access AWS resources across regions and public internet resources through a customer’s Virtual Private Cloud (VPC). With this launch, life sciences customers no longer need to migrate their data and dependencies to the same AWS Region as their workflow before running analyses. AWS HealthOmics is a HIPAA-eligible service that helps accelerate scientific breakthroughs at scale with fully managed bioinformatics workflows.
This launch enables life sciences customers to develop and test bioinformatics workflows more quickly. Customers can design workflows that access publicly-hosted data sets as well as AWS resources in different regions without making changes to the workflow code or migrating data between regions. Customers can use new Configuration APIs to specify a VPC configured to access public internet resources to which HealthOmics can send and receive network traffic, making it easy to use different network configurations for different use cases. With Configuration APIs, you can add and remove public internet dependencies anytime. Networking settings are configured at the per-run level, allowing you to opt-in only the workflows that you want to be VPC connected. 
VPC-connected workflows are now available in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), Asia Pacific (Singapore), and Asia Pacific (Seoul). To learn more about connecting workflows to your VPC, see the HealthOmics documentation.
Quelle: aws.amazon.com

AWS Security Hub is now available in AWS GovCloud (US) Regions

AWS Security Hub is now available in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. Security Hub is a unified cloud security solution that prioritizes critical security issues and helps you respond at scale, reduce security risks, and improve team productivity. Security Hub detects critical risks by correlating and enriching security signals from Amazon GuardDuty, Amazon Inspector, and AWS Security Hub CSPM, enabling you to quickly surface and prioritize active risks in your cloud environment. The service delivers near real-time risk analytics and advanced trends, transforming correlated security signals into actionable insights through enhanced visualizations and contextual enrichment. You can enable Security Hub for individual accounts or across your entire organization with centralized deployment and management. Capabilities include exposure findings, security-focused resource inventory, attack path visualization, and automated response workflows. The service automatically visualizes potential attack paths by showing how adversaries could chain together threats, vulnerabilities, and misconfigurations to compromise critical resources. Streamlined pricing consolidates charges across multiple AWS security services for improved cost predictability. To get started, visit the AWS Security Hub console or the AWS Security Hub product page. For the full list of AWS Regions where Security Hub is available, see the AWS Regional Services List.
Quelle: aws.amazon.com

Amazon CloudWatch now supports multi-account and region log centralization based on data source

Amazon CloudWatch centralization now supports centralizing logs based on data source name and type. CloudWatch allows customers to copy log data from multiple AWS accounts and regions into a single destination account using centralization rules. With today’s launch, customers can now define rules that target data sources by name and type, such as VPC Flow Logs, EKS Audit Logs, and CloudTrail Logs, in addition to the existing log group name-based selection.
Data source name and type are discovered automatically by CloudWatch for AWS service logs and are based on log group tags for application logs.  Now, customers can specifically target which logs they want to centralize using these parameters. For example, a central security team can create a rule that centralizes all logs from CloudTrail and VPC data sources across their entire organization without needing to know or maintain a list of individual log group names.
To get started, create or modify a centralization rule in the Amazon CloudWatch console or through the AWS CLI and AWS SDKs, and specify your data source selection criteria in the centralization rule configuration.
Data source selection criteria is available in all AWS commercial regions where CloudWatch log centralization is available. Standard CloudWatch Logs pricing applies for log ingestion, storage, and data transfer. For more information, see the CloudWatch Logs Centralization documentation.
Quelle: aws.amazon.com