AWS transfer: Clarify logging role requirement for workflows with structured log destination
Summary
Updates guidance to explain that a logging role is only required for workflows without a structured log destination; workflows with a CloudWatch Logs StructuredLogDestinations deliver logs directly without a logging role.
Security assessment
The change clarifies when a logging role is needed for workflow logging, which affects audit/visibility configuration. It is documentation of logging behavior rather than a fix for a specific vulnerability.
Evidence
To enable logging for a workflow that does not have a structured log destination configured, you must use a logging role on the server that the workflow is attached to.
Diff
diff --git a/transfer/latest/userguide/log-server-manage.md b/transfer/latest/userguide/log-server-manage.md index 978ea10..c066c13 100644 --- a//transfer/latest/userguide/log-server-manage.md +++ b//transfer/latest/userguide/log-server-manage.md @@ -26 +26 @@ For all AWS Transfer Family servers, we provide structured logging. We recommend -To enable logging for workflows that are attached to servers, you must use a logging role. +To enable logging for a workflow that does not have a structured log destination configured, you must use a logging role on the server that the workflow is attached to. If the workflow has a structured log destination configured (a CloudWatch Logs log group specified in its `StructuredLogDestinations` parameter), Transfer Family delivers the workflow execution logs to that log group and a logging role is not required. For details, see [Managing logging for workflows](./cloudwatch-workflows.html). @@ -38 +38 @@ If you create a new server by using the Transfer Family console, logging is enab -Currently, for workflows, if you want logging enabled, you must specify a logging role: +For a workflow that does not have a structured log destination configured, if you want logging enabled, you must specify a logging role: @@ -40 +40 @@ Currently, for workflows, if you want logging enabled, you must specify a loggin - * If you associate a workflow with a server, using either the `CreateServer` or `UpdateServer` API operation, the system does not automatically create a logging role. If you want to log your workflow events, you need to explicitly attach a logging role to the server. + * If you associate a workflow with a server, using either the `CreateServer` or `UpdateServer` API operation, the system does not automatically create a logging role. If you want to log the events of a workflow that does not have a structured log destination, you need to explicitly attach a logging role to the server.