New AWS and AI Product Updates: What Changes for Security, Agent Governance and Cloud Operations

What Happened

• Security and agents: On October 14, AWS Security Hub added resource criticality for sorting, filtering and assessing exposures. Automation rules can set it for existing and new resources; Security Hub can also infer it from tags and names. It is on at no additional cost for Security Hub Essentials customers. On October 13, AWS Agent Registry added schema-validated custom metadata and filtering for agents, MCP servers, skills, gateways and custom resources in its five supported Regions. [1] [3]
• Containers and data: Amazon ECS introduced the free LiveTaskCount metric, which includes tasks in ACTIVATING, RUNNING and DEACTIVATING states. The existing Container Insights RunningTaskCount metric has no additional charge from October 1, 2026; the metrics count different task populations. AWS DataSync Enhanced mode added FSx for OpenZFS, NFS 4.2 and an ObjectMetadata transfer control. Existing tasks are unaffected. [2] [8]
• Application and infrastructure tools: Amazon Location Service launched a console playground for all 14 Places, Routes and Maps APIs. Deadline Cloud’s monitor now discovers resources a user can access. Route 53 Domains added premium-domain registration, transfer, renewal and restoration with upfront search pricing. Amazon DCV 2026.0 added newer Linux platform support, updated clients and latency improvements. [4] [5] [6] [9]
• Database and video: Amazon RDS for SQL Server added SQL Server 2025 CU8, KB5104822, as engine version 17.00.4075.5.v1. Separately, Higgsfield described plans for longer AI video, more precise images and voice filmmaking using products it calls GPT-6 Astra, GPT-Image-2.5 and GPT-Live; the available information does not establish API availability or release versions. [7] [10]

Why It Matters to Businesses

These changes can reduce manual work, but they do not remove the need for validation. Criticality can put exposures to important assets first; registry metadata can make approved agents easier to find; and LiveTaskCount can give capacity planning a view that includes draining tasks. Teams should not substitute LiveTaskCount for RunningTaskCount without revisiting alert and scaling thresholds. [1] [2] [3]

Kimbodo Engineering Perspective

The useful distinction is between a feature becoming available and a system being ready to depend on it. Security Hub’s inferred criticality needs an authoritative asset owner; registry fields need a stable vocabulary; and a new database CU needs application testing. We would adopt each change where it solves a measured operational problem, rather than enable a broad migration because a release exists. [1] [3] [10]

How We Would Implement It

• Define criticality from a controlled asset inventory, apply Security Hub automation rules, and review inferred values and their recorded sources before using them to drive response priority. [1]
• Publish a versioned Agent Registry metadata schema with required owner, environment and approval fields; validate record creation in CI and restrict who can edit governance fields. Confirm the deployment Region is supported. [3]
• Run LiveTaskCount and RunningTaskCount side by side through scale-in events, then tune dashboards and autoscaling thresholds against their different definitions. Test DataSync metadata behavior and SQL Server CU8 in non-production before rollout. [2] [8] [10]

Risks, Costs and Security

Do not treat inferred criticality or self-declared agent metadata as proof of business importance or approval. Keep sensitive information out of searchable registry fields, verify Deadline Cloud permissions with representative users, and review the cost of premium domains before purchase. Although the specified ECS metric changes and Security Hub Essentials criticality carry no additional charge, other service usage and migration work still need normal cost review. [1] [2] [3] [5] [9]

Sources

1. [1] AWS Security Hub now supports resource criticality for prioritization
2. [2] Amazon ECS adds LiveTaskCount and removes the charge for RunningTaskCount metric
3. [3] AWS Agent Registry now supports custom metadata for registry records
4. [4] Amazon DCV releases version 2026.0 with RHEL 10 support and new clients
5. [5] AWS Deadline Cloud now helps users find their accessible resources in the Deadline Cloud monitor
6. [6] Amazon Location Service launches an interactive API Playground featuring Places, Routes and Maps APIs
7. [7] Higgsfield takes AI video from 1 minute to over 10
8. [8] AWS DataSync Enhanced mode now supports FSx for OpenZFS, NFS 4.2, and object metadata controls
9. [9] Amazon Route 53 now supports registrations, transfers, and renewals for Premium Domains
10. [10] Amazon RDS now supports the latest CU for Microsoft SQL Server