AWS Step Functions Enables Access to Workflow Metadata
AWS Step Functions now enables access to metadata about workflow executions so that you can easily identify related resources. For example, your workflow can retrieve its execution ID or a timestamp indicating when a task started. This makes it easier to correlate logs for faster debugging and to measure workflow performance data. Your workflows pass metadata to tasks by referencing a context object available with each workflow execution.
AWS Step Functions now enables access to metadata about workflow executions so that you can easily identify related resources. For example, your workflow can retrieve its execution ID or a timestamp indicating when a task started. This makes it easier to correlate logs for faster debugging and to measure workflow performance data. Your workflows pass metadata to tasks by referencing a context object available with each workflow execution.
AWS Step Functions allows you to add resilient workflow automation to your applications. The steps of your workflow can exist anywhere, including in AWS Lambda functions, on Amazon EC2, or on-premises. AWS Step Functions is also integrated with Amazon ECS, AWS Fargate, Amazon DynamoDB, Amazon SNS, Amazon SQS, AWS Batch, AWS Glue, and Amazon SageMaker. You can connect and coordinate all these services in minutes—without writing code.
Support for the context object is included in AWS Step Functions pricing at no additional fee. AWS Step Functions supports access to workflow metadata from the context object today in all AWS public regions where Step Functions is available. For a complete list of regions where AWS Step Functions is offered, see AWS Regions.
To learn more about Step Functions, read the AWS Step Functions Developer Guide. To learn more about accessing workflow metadata, read about the AWS Step Functions Context Object.