AWS adds managed ArgoCD and org-wide EC2 monitoring
AWS now offers managed ArgoCD directly from the EKS console — no Helm or manual upgrades required — and ties it into IAM Identity Center for SSO, though customization is limited announced. Amazon also enabled organization-wide EC2 detailed monitoring in CloudWatch to simplify fleet observability reported.
Amazon announced Amazon EKS Capabilities, which introduced the managed Argo CD capability, at AWS re:Invent on Nov 30, 2025. (aws.amazon.com) The Argo CD capability runs inside EKS’s managed capabilities layer in EKS service‑owned accounts and requires creating an IAM capability role with a trust policy that allows the capabilities.eks.amazonaws.com service principal to assume it. (docs.aws.amazon.com) Authentication requires an existing AWS Identity Center instance (local users aren’t supported) and the console flow lets operators map Identity Center users/groups to Argo CD RBAC roles such as Admin, Editor, and Viewer during setup. (docs.amazonaws.cn) AWS documentation and deep‑dive coverage note the tradeoff: AWS handles installation, scaling, patching, and high availability for the capability, while some advanced in‑cluster customizations and operator workflows remain more feasible in a self‑managed Argo CD deployment. (docs.aws.amazon.com) Amazon published an update on Mar 16, 2026 adding organization‑wide EC2 detailed monitoring in CloudWatch, which uses CloudWatch Ingestion enablement rules to auto‑enable 1‑minute detailed metrics for existing and newly launched EC2 instances. (aws.amazon.com) The CloudWatch change can be scoped to an entire AWS Organization, specific accounts, or resources by tag, is available in all AWS commercial regions, and AWS states the 1‑minute detailed metrics will be billed according to CloudWatch pricing (detailed monitoring replaces the default 5‑minute basic metrics and incurs charges). (aws.amazon.com)
