Cloud Computing Köln

AWS Deadline Cloud now helps users find their accessible resources in the Deadline Cloud monitor

AWS Deadline Cloud now lets users who have access to specific queues, fleets, or jobs, rather than an entire farm, find the resources they can reach directly from the Deadline Cloud monitor. Deadline Cloud is a fully managed service that helps teams run compute-intensive workloads for visual effects, animation, product design, simulation, and gaming.
Previously, a user with access to only one queue had to get the farm ID from an administrator before they could reach their work. With this launch, the Deadline Cloud monitor displays to users queues they have access to, the parent IDs needed to reach them, and their level of access, covering both direct and group-inherited permissions. Teams now can share a single monitor entry point (URL) across different permission levels without additional coordination.
Resource discovery is available in all AWS Regions where Deadline Cloud is available. To learn more, visit the AWS Deadline Cloud user guide.
Quelle: aws.amazon.com

Amazon DCV releases version 2026.0 with RHEL 10 support and new clients

Amazon DCV 2026.0 is now available, adding support for RHEL 10, Rocky Linux 10, CentOS 10, and Ubuntu 26.04 along with a new macOS client and updated Windows and Linux clients. Amazon DCV is a high-performance remote display protocol that enables customers to securely access remote desktops and application sessions across Windows, Linux, and macOS.
Amazon DCV 2026.0 includes the following key features and improvements:

Support for RHEL 10, Rocky Linux 10, CentOS 10, and Ubuntu 26.04, with Linux hosts and sessions running on the modern Wayland display server

A new macOS client with gamepad support, and updated Windows and Linux clients

URL redirection on Windows hosts, so configured links opened in a remote session launch in the local browser on the client device

Printer preferences redirection on Windows, giving remote sessions access to client-side printer settings

Performance improvements, including H.264 frame slice support and slice-based multithreaded decoding on the Linux and macOS clients for lower latency

Support for new macOS server versions on Amazon EC2

For more information about the new features and enhancements in Amazon DCV 2026.0, see the release notes or visit the Amazon DCV webpage to learn more and get started.
 
Quelle: aws.amazon.com

AWS Agent Registry now supports custom metadata for registry records

AWS Agent Registry is the centralized, governed catalog for agents, MCP servers, agent skills, gateways, and custom resources within your organization. As organizations scale to hundreds of such resources, a name and description alone are insufficient for effective governance and discovery. Custom metadata lets you extend every registry record with your organization’s own structured fields, so both people and automated systems can find and govern resources consistently.

With custom metadata, publishers can record fields like team ownership, data classification, or review status directly on each registry record. You define a schema once per registry with common attributes, then extend it with type-specific fields — such as a model family for agent records. Each field supports free text, a URL, a Boolean, or a choice from a list of allowed values, and the registry validates required fields and values on every record creation or update. You can then filter search results on any custom metadata field from the AWS Management Console, the AWS CLI, the AWS SDKs, or the registry’s MCP endpoint.

Custom metadata is available in all AWS Regions where AWS Agent Registry is available: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Europe (Ireland).

To learn more, visit the AWS Agent Registry documentation. For detailed setup guidance, see Define a custom metadata schema and Set custom metadata values on a record.
Quelle: aws.amazon.com

Amazon ECS adds LiveTaskCount and removes the charge for RunningTaskCount metric

Today, Amazon Elastic Container Service (Amazon ECS) announces LiveTaskCount, a new ECS service metric that reports how many tasks are actively running in your service, available to all customers at no additional charge. Additionally, the existing RunningTaskCount metric in Amazon CloudWatch Container Insights no longer incurs a charge.
LiveTaskCount reports the number of actively running ECS tasks across all desired states (ACTIVATING, RUNNING, and DEACTIVATING), including tasks still running while transitioning to a stopped state, for example, tasks undergoing connection draining during a scale-in event. This comprehensive state coverage makes LiveTaskCount well suited for autoscaling policies and capacity planning where a complete view of active, metric-generating tasks is required. It is available at no charge as part of ECS service utilization metrics and does not require opting in to CloudWatch Container Insights. The existing CloudWatch Container Insights RunningTaskCount metric tracks tasks where both the current and desired state are RUNNING, and continues to serve as a health and stability signal for customers who depend on it. With today’s update, RunningTaskCount is now available at no additional charge for all CloudWatch Container Insights users.
These updates are available in all AWS Regions where Amazon ECS is available. No action is required, and the pricing change for RunningTaskCount takes effect beginning October 1, 2026, and applies automatically. To learn more, see ECS CloudWatch metrics and ECS Container Insights metrics. For a pricing example, see Amazon CloudWatch pricing.
Quelle: aws.amazon.com

AWS Security Hub now supports resource criticality for prioritization

Today, AWS Security Hub adds resource criticality to exposure prioritization, helping central security teams focus on the exposures that threaten their most business-critical resources.
You can set criticality with an automation rule, for example marking every compute resource in a specific account as Very High. The rule applies to resources already in your inventory and to new resources as Security Hub discovers them. Security Hub also infers criticality from resource tags and resource names, with no configuration required, and records which source determined the value. Criticality appears as a column on the Resources page for sorting, filtering, and grouping, and on the Impact assessment tab of an exposure finding. Resource criticality is included with Security Hub Essentials at no additional cost and is always on for all customers.
Resource criticality is included with Security Hub Essentials at no additional cost and requires no new enablement. To learn more, see  AWS Security Hub User Guide and the AWS Security Hub product page. For a list of AWS Regions where Security Hub is available, see the AWS Region table.
Quelle: aws.amazon.com