AWS wellarchitected documentation change
Summary
Updated 'ELB' to 'Elastic Load Balancing' for terminology consistency.
Security assessment
Minor terminology correction in monitoring context. No security features added or modified; monitoring capabilities described remain identical.
Diff
diff --git a/wellarchitected/2022-03-31/framework/rel_monitor_aws_resources_notification_aggregation.md b/wellarchitected/2022-03-31/framework/rel_monitor_aws_resources_notification_aggregation.md index cf9048377..8ce331737 100644 --- a//wellarchitected/2022-03-31/framework/rel_monitor_aws_resources_notification_aggregation.md +++ b//wellarchitected/2022-03-31/framework/rel_monitor_aws_resources_notification_aggregation.md @@ -11 +11 @@ Store log data and apply filters where necessary to calculate metrics, such as c -Amazon CloudWatch and Amazon S3 serve as the primary aggregation and storage layers. For some services, such as AWS Auto Scaling and ELB, default metrics are provided by default for CPU load or average request latency across a cluster or instance. For streaming services, such as VPC Flow Logs and AWS CloudTrail, event data is forwarded to CloudWatch Logs and you need to define and apply metrics filters to extract metrics from the event data. This gives you time series data, which can serve as inputs to CloudWatch alarms that you define to trigger alerts. +Amazon CloudWatch and Amazon S3 serve as the primary aggregation and storage layers. For some services, such as AWS Auto Scaling and Elastic Load Balancing, default metrics are provided by default for CPU load or average request latency across a cluster or instance. For streaming services, such as VPC Flow Logs and AWS CloudTrail, event data is forwarded to CloudWatch Logs and you need to define and apply metrics filters to extract metrics from the event data. This gives you time series data, which can serve as inputs to CloudWatch alarms that you define to trigger alerts.