AWS lambda documentation change
Summary
Updated wording in monitoring best practices
Security assessment
Single word change ('ensure' to 'verify') in monitoring guidance. No security context or implications present in the change.
Diff
diff --git a/lambda/latest/dg/lambda-managed-instances-best-practices.md b/lambda/latest/dg/lambda-managed-instances-best-practices.md index a32e93c63..ea49a55ac 100644 --- a//lambda/latest/dg/lambda-managed-instances-best-practices.md +++ b//lambda/latest/dg/lambda-managed-instances-best-practices.md @@ -85 +85 @@ Note that execution environments with very low concurrency may experience thrott -**Monitor capacity provider metrics.** Track capacity provider level metrics including CPUUtilization, MemoryUtilization, vCPUAvailable, and MemoryAvailable to ensure sufficient resources are available for your workloads. +**Monitor capacity provider metrics.** Track capacity provider level metrics including CPUUtilization, MemoryUtilization, vCPUAvailable, and MemoryAvailable to verify sufficient resources are available for your workloads.