4/18/2025, 12:00:00 AM ~ 4/21/2025, 12:00:00 AM (UTC)
Recent Announcements
AWS HealthOmics announces workflow versioning support
AWS HealthOmics now supports workflow versioning, enabling customers to manage multiple versions of their bioinformatics workflows efficiently. 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. With this release, workflow developers can create and maintain multiple versions of their workflows while retaining consistent workflow IDs and base ARNs across versions.\n With workflow versioning, users can select specific workflow versions when starting a run, enabling better control and reproducibility of their analyses. This simplifies collaboration by automatically sharing new workflow versions with existing subscribers, eliminating the need for manual resharing and ensuring teams always have access to the latest workflow iterations. Workflow versioning is 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 get started with workflow versioning, see the AWS HealthOmics documentation.
Amazon CloudWatch launches cross-account observability in the AWS GovCloud (US) Regions
AWS launches CloudWatch cross-account observability in the AWS GovCloud (US) Regions, enabling monitoring and troubleshooting of applications across multiple AWS accounts within an AWS GovCloud (US) Region. CloudWatch Cross-account observability allows seamless searching, visualization, and analysis of metrics, logs, and traces, removing account boundaries.\n Security teams, operations teams, and service owners can now easily explore cross-account telemetry and analyze them to drive powerful insights helping to efficiently monitor and troubleshoot application health issues. CloudWatch Cross-account observability enables searching log groups across multiple accounts, running cross-account Logs Insights queries, and creating Contributor Insights rules to identify top contributors generating log entries. You can now run Metrics Insights queries on your cross-account metrics for a consolidated view and create cross-account alarms. With cross-account observability, you can now use AWS X-Ray Trace Map to monitor your cross-account applications or achieve single pane of glass observability on your end-to-end distributed traces for requests spanning across multiple accounts. For example, users can obtain end-to-end distributed traces tracking AWS Lambda functions calling each other across accounts. This eliminates the need to switch between accounts during troubleshooting, saving time and providing comprehensive visibility. CloudWatch cross-account observability is now available in all commercial AWS Regions and the AWS GovCloud (US) Regions with no extra cost for logs and metrics, and the first trace copy is free. Detailed pricing information and documentation are available on the Amazon CloudWatch pricing page and documentation pages.
Amazon CloudWatch agent now supports Red Hat OpenShift Service on AWS (ROSA)
Amazon CloudWatch agent support for Red Hat OpenShift Service on AWS (ROSA) enables monitoring of applications and infrastructure using familiar CloudWatch tools such as Container Insights and Application Signals. ROSA is a fully-managed cloud service that helps customers to quickly deploy, operate, and scale containerized applications on AWS with the same consistent OpenShift experience they have on-premises. This new capability allows DevOps teams and application owners to gain deep visibility into their ROSA clusters’ performance, health, and resource utilization leveraging AWS’s native observability tools.\n CloudWatch agent on ROSA enables the collection and analysis of metrics, logs, and traces from containerized applications and underlying infrastructure components, helping customers to identify the impact of anomalies on end-user experience. This integration streamlines the troubleshooting process and allows teams to quickly identify issues across their ROSA clusters and other AWS services. Through unified infrastructure and application monitoring, customers can set up automated alerts, track performance trends, and correlate events across their entire application stack. Amazon CloudWatch agent is available in all public AWS Regions and AWS GovCloud (US). Please see Amazon CloudWatch pricing for pricing details. To get started with Amazon CloudWatch agent on Red Hat OpenShift Service on AWS, see Setting up Container Insights on RedHat OpenShift on AWS (ROSA) in the Amazon CloudWatch User Guide.
AWS STS global endpoint now serves your requests locally in regions enabled by default
AWS Security Token Service (AWS STS) now automatically serves all requests to the global endpoint (sts.amazonaws.com) in the same AWS Region as your deployed workloads, enhancing resiliency and performance. Previously, all requests to the STS global endpoint were served from the US East (N. Virginia) Region.\n With this enhancement, your applications benefit from improved latency and fault isolation as requests are processed in the same Region as your workloads. For example, if your application runs in US West (Oregon) and calls the STS global endpoint, your requests are now served locally in US West (Oregon) instead of being routed to US East (N. Virginia). This update is available in all AWS Regions that are enabled by default. No action is required from customers to benefit from these improvements. Any requests to the STS global endpoint from Regions not enabled by default (i.e. opt-in Regions) will continue to be served in US East (N. Virginia). We continue to recommend that you use the appropriate STS Regional endpoints whenever possible. For more information about these changes, see AWS STS global endpoint changes , and the announcement blogpost.
AWS Console Mobile Application adds support for Amazon Lightsail
AWS customers can now access Amazon Lightsail from within the AWS Console Mobile App to monitor and manage Lightsail instances, containers, databases, network, storage, snapshots, domains and DNS while on the go. Visit the Services tab in the AWS Console Mobile App and select Lightsail to get started.\n The AWS Console Mobile App enables AWS customers monitor and manage a select set of resources and receive push notifications to stay informed and connected with their AWS resources while on-the-go. The sign-in process supports biometrics authentication, making access to AWS resources simple, secure, and quick. Lightsail offers easy-to-use virtual private server (VPS) instances, storage, databases, and more for a cost-effective monthly price. For AWS services not available natively, customers can access the AWS Management Console via an in-app browser to access service pages without additional authentication, manual navigation, or need to switch from the app to a browser. Visit the AWS Console Mobile App product page for more information about the AWS Console Mobile App, including a full list of supported services and regions. Visit the Amazon Lightsail product page for more information about Amazon Lightsail, including supported regions.
Amazon Managed Service for Prometheus now supports label-based active series limits
Amazon Managed Service for Prometheus now supports label-based active series limits within your workspace. This feature helps you manage active series volume across different producers such as applications, services or teams that share a workspace.\n You can now allocate specific active series limits to different metric producers in your workspace, enabling you to protect your critical metrics. If a sub-set of metrics experience an unexpected surge, only the metrics sharing the same label-based active series limits are throttled. For example, you can set different limits for metrics from different applications using label sets like {app=“payment-service”, environment=“prod”}. If the payment-service application produced an unexpected surge in metrics, only ingested metrics originating from the payment-service application are throttled.
This experience is enabled by the new Workspace Configuration APIs. Using these APIs, you can also manage the data retention period of your workspace. You can specify the number of days to retain metrics data within your workspace, before permanent deletion. To get started, visit AMP console’s workspace configuration tab or use AWS CLI, SDK, or APIs. Check out the Amazon Managed Service for Prometheus user guide for detailed documentation. This feature is now available in all AWS regions where Amazon Managed Service for Prometheus is generally available.
AWS Blogs
AWS Japan Blog (Japanese)
- Amazon S3 Express Announces Up to 85% Price Reduction for One Zone
- AWS announces Pixtral Large 25.02 model for Amazon Bedrock Serverless
- Amazon Bedrock Guardrail Enhances Safety for Generative AI Applications with New Features
AWS Open Source Blog
AWS Architecture Blog
Desktop and Application Streaming
AWS Machine Learning Blog
- Build a FinOps agent using Amazon Bedrock with multi-agent capability and Amazon Nova as the foundation model
- Stream ingest data from Kafka to Amazon Bedrock Knowledge Bases using custom connectors