Pick a log destination per workflow: Transfer Family adds custom CloudWatch log groups
Hi, it's Shii-chan! No more workflow logs mixed into the server's logs!
AWS What's New
aws.amazon.com
What was announced?
AWS What's New announced that AWS Transfer Family now lets you choose a custom log group in Amazon CloudWatch Logs for managed workflow execution logs.
The story so far
Every workflow attached to a Transfer Family server sent its execution logs to that server's CloudWatch log group. So you couldn't set a separate log destination for each workflow.
What changes
When you create a workflow in the Transfer Family console or API, you can select a workflow-level log group separate from the server's log group.
You can organize logs in two ways:
- Monitor individual workflows separately
- Bring logs from related workflows together
Sending logs from multiple workflows to a shared log group also lets you create consolidated metrics and dashboards for tracking workflow execution.
Dive Deep
- Transfer Family delivers workflow logs only to the selected group, so no server logging role is required
- Logs keep their existing structured JSON format and stay queryable with CloudWatch Logs Insights
- If you don't select a structured log destination, workflow logs continue using the server's role-based logging configuration when configured
- Existing workflows keep their current logging configuration
- Available in all Regions where Transfer Family managed workflows are offered
Wrap-up
- Choose a workflow-level custom log group for managed workflow execution logs
- Monitor workflows individually or consolidate them
- Logs go only to the chosen group, so no server logging role is needed
- Existing workflows are unaffected
A nice update for ops folks running multiple file transfer workflows!
