AWS Security ChangesHomeSearch

AWS transfer: Extend structured logging guidance to managed workflows

Service: transfer · 2026-10-02 · Documentation low

File: transfer/latest/userguide/structured-logging.md · Type: logging

Summary

Updates structured logging documentation to cover managed workflows in addition to servers, and clarifies that logging roles are needed for connectors and for workflows not using JSON structured logging.

Security assessment

Documents recommended structured logging and associated IAM permissions for servers and workflows, improving auditability. No specific vulnerability is addressed.

Evidence

For logging server and managed workflow events, we recommend using JSON structured logging. This provides a more comprehensive logging format that enables CloudWatch log querying.

Diff

diff --git a/transfer/latest/userguide/structured-logging.md b/transfer/latest/userguide/structured-logging.md
index e4ac402..d0c89f5 100644
--- a//transfer/latest/userguide/structured-logging.md
+++ b//transfer/latest/userguide/structured-logging.md
@@ -43 +43 @@ Transfer Family provides two ways to log events to CloudWatch:
-For Transfer Family servers, you can choose the logging mechanism that you prefer. For connectors and workflows, only logging roles are supported.
+For Transfer Family servers and managed workflows, you can choose the logging mechanism that you prefer. For connectors, only logging roles are supported.
@@ -47 +47 @@ For Transfer Family servers, you can choose the logging mechanism that you prefe
-For logging server events, we recommend using JSON structured logging. This provides a more comprehensive logging format that enables CloudWatch log querying. For this type of logging, the IAM policy for the user that creates the server (or edits the server's logging configuration) must contain the following permissions:
+For logging server and managed workflow events, we recommend using JSON structured logging. This provides a more comprehensive logging format that enables CloudWatch log querying. For servers, this type of logging requires that the IAM policy for the user that creates the server (or edits the server's logging configuration) contains the following permissions:
@@ -96 +96 @@ For details on setting up JSON structured logging, see [Creating, updating, and
-To log events for a managed workflow that is attached to a server, as well as for connectors, you need to specify a logging role. To set access, you create a resource-based IAM policy and an IAM role that provides that access information. The following is an example policy for an AWS account that can log server events.
+For connectors, and for managed workflows when you are not using JSON structured logging, you need to specify a logging role. To set access, you create a resource-based IAM policy and an IAM role that provides that access information. The following is an example policy for an AWS account that can log server events.