Amazon CloudWatch adds support for Internet Protocol version 6 (IPv6) addresses to ingest and query metrics, as well as manage alarms, dashboards, and Observability Access Manager (OAM) cross-account observability settings. Customers moving to IPv6 can simplify their network stack by running their CloudWatch monitoring on a dual-stack network that supports both IPv4 and IPv6.
The addition of IPv6 support provides customers with a vastly expanded address space, eliminating concerns about address exhaustion and simplifying network architecture for IPv6-native applications. With simultaneous support for both IPv4 and IPv6 clients on CloudWatch public endpoints, customers can gradually transition from IPv4 to IPv6-based systems and applications without needing to switch all systems at once. This enhancement is particularly valuable for modern cloud-native applications and organizations transitioning to IPv6 as part of their modernization efforts.
Support for IPv6 on CloudWatch endpoints is now available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions.
To start using CloudWatch IPv6 on endpoints related to metrics, alarms, dashboards, or OAM settings, you simply need to update your network configuration and the URL of the CloudWatch endpoints or CloudWatch OAM endpoints you connect to. Please refer to AWS service endpoints documentation for the updated URL endpoint syntax. For use within a VPC, please refer to how to add IPv6 support for your VPC.
Categories:
Source: Amazon Web Services
Latest Posts
- SharePoint site analytics: OneNote usage included in site usage reports [MC1194626]
- Microsoft Excel: Enabling M365 subscribers to use Copilot Chat in locally stored modern workbooks [MC1194615]
- (Updated) Microsoft 365 Copilot: Steer your presentation length, tone, style, and images when creating with Copilot [MC1185911]
- (Updated) Changes to how users install Microsoft 365 apps from the Microsoft 365 Copilot app [MC1062453]
