AWS AmazonCloudWatch documentation change

Service: AmazonCloudWatch · 2025-11-22 · Documentation low

File: AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.md

Summary

Renamed 'AWS VPN' to 'Site-to-Site VPN' in service list and section header

Security assessment

Cosmetic change to align with AWS service naming conventions, no security implications.

Diff

diff --git a/AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.md b/AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.md
index fb2cacc42..961d3c236 100644
--- a//AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.md
+++ b//AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.md
@@ -5 +5 @@
-Amazon API GatewayAmazon EC2 Auto ScalingAWS Certificate Manager (ACM)Amazon CloudFrontAmazon CognitoAmazon DynamoDBAmazon EBSAmazon EC2Amazon ElastiCacheAmazon ECSAmazon ECS with Container InsightsAmazon ECS with Container Insights with enhanced observabilityAmazon EFSAmazon EKS with Container InsightsAmazon EventBridge SchedulerAmazon Kinesis Data StreamsLambdaLambda InsightsAmazon VPC (AWS/NATGateway)AWS Private Link (AWS/PrivateLinkEndpoints)AWS Private Link (AWS/PrivateLinkServices)Amazon RDSAmazon Route 53 Public Data PlaneAmazon S3S3ObjectLambdaAmazon SNSAmazon SQSAWS VPN
+Amazon API GatewayAmazon EC2 Auto ScalingAWS Certificate Manager (ACM)Amazon CloudFrontAmazon CognitoAmazon DynamoDBAmazon EBSAmazon EC2Amazon ElastiCacheAmazon ECSAmazon ECS with Container InsightsAmazon ECS with Container Insights with enhanced observabilityAmazon EFSAmazon EKS with Container InsightsAmazon EventBridge SchedulerAmazon Kinesis Data StreamsLambdaLambda InsightsAmazon VPC (AWS/NATGateway)AWS Private Link (AWS/PrivateLinkEndpoints)AWS Private Link (AWS/PrivateLinkServices)Amazon RDSAmazon Route 53 Public Data PlaneAmazon S3S3ObjectLambdaAmazon SNSAmazon SQSSite-to-Site VPN
@@ -71 +71 @@ Some metrics might appear twice in the list. This happens when different alarms
-  * AWS VPN
+  * Site-to-Site VPN
@@ -3483 +3483 @@ We recommend setting best-practice alarms for the following Lambda Insights metr
-## AWS VPN
+## Site-to-Site VPN