AWS general documentation change
Summary
Updated endpoint protocols and renamed anomaly monitor categories (AWS managed vs customer managed)
Security assessment
Changes involve terminology updates and endpoint formatting without any security context or vulnerability references.
Diff
diff --git a/general/latest/gr/billing.md b/general/latest/gr/billing.md index c653e2963..25157d7be 100644 --- a//general/latest/gr/billing.md +++ b//general/latest/gr/billing.md @@ -54 +54 @@ Region Name | Region | Endpoint | Protocol -US East (N. Virginia) | us-east-1 | cost-optimization-hub.us-east-1.amazonaws.com | HTTPS +US East (N. Virginia) | us-east-1 | cost-optimization-hub.us-east-1.amazonaws.com cost-optimization-hub.us-east-1.api.aws | HTTPS HTTPS @@ -119 +119 @@ Cost Explorer saved reports | Each supported Region: 300 | No | The maximum numb -Number of AWS services anomaly monitors | Each supported Region: 1 | No | The maximum number of AWS services anomaly monitors you can create per account +Number of AWS managed services anomaly monitors | Each supported Region: 1 | No | The maximum number of AWS managed service anomaly monitors per account @@ -125 +125 @@ Number of anomaly alert subscriptions | Each supported Region: 100 | No | The ma -Number of linked account, cost category, and cost allocation tag anomaly monitors | Each supported Region: 500 | No | The maximum number of total linked account, cost category, and cost allocation tag anomaly monitors you can create per management account +Number of customer managed anomaly monitors | Each supported Region: 500 | No | Maximum number of customer managed anomaly monitors (linked account, cost category, or cost allocation tags) per account