AWS step-functions documentation change
Summary
Updated CloudWatch metrics guidance: Removed specific Lambda metrics (LambdaFunctionsStarted/TimedOut), added recommendation for failure monitoring baseline, and clarified Lambda integration metrics for modern state machines.
Security assessment
Changes focus on monitoring best practices and metric updates, but don't address vulnerabilities or introduce security features. The removal of Lambda-specific metrics appears to be documentation cleanup rather than security-related.
Diff
diff --git a/step-functions/latest/dg/procedure-cw-metrics.md b/step-functions/latest/dg/procedure-cw-metrics.md index 5f3e91ab3..7a38d0d1f 100644 --- a//step-functions/latest/dg/procedure-cw-metrics.md +++ b//step-functions/latest/dg/procedure-cw-metrics.md @@ -30 +30 @@ The next step is to establish a baseline for normal performance in your environm -For example, with Step Functions, you can monitor how many activities or AWS Lambda tasks fail due to a heartbeat timeout. When performance falls outside your established baseline, you might have to change your heartbeat interval. +We recommend monitoring Activity and Task failures to establish a baseline. When performance falls outside your baseline metric, set an alert so you can research the root cause. @@ -42,4 +41,0 @@ To establish a baseline you should, at a minimum, monitor the following metrics: - * `LambdaFunctionsStarted` - - * `LambdaFunctionsTimedOut` - @@ -185 +181 @@ Dimension | Description -The `AWS/States` namespace includes the following metrics for Step Functions Lambda functions. +The `AWS/States` namespace includes the following metrics for Lambda functions which are referred to **directly** in the Resource field of a Task state definition. You might find these metrics in legacy state machines. In modern state machines, we recommend using the Optimized Lambda integration which emits Service Integration Metrics.