AWS transfer: Document workflow log stream formats by logging mechanism
Summary
Adds explanation of the two possible workflow log stream name formats depending on whether the workflow uses a logging role or a structured log destination.
Security assessment
Purely descriptive documentation of log stream naming conventions; no security control or vulnerability is involved.
Evidence
The format for the workflow log stream depends on which logging mechanism the workflow uses:
Diff
diff --git a/transfer/latest/userguide/view-log-entries.md b/transfer/latest/userguide/view-log-entries.md index acd93fb..3af3eb3 100644 --- a//transfer/latest/userguide/view-log-entries.md +++ b//transfer/latest/userguide/view-log-entries.md @@ -33 +33,5 @@ -The format for the log stream for the workflow is ``username`.`workflowId`.`uniqueStreamSuffix``. For example, **decrypt-user.w-a1111222233334444.aaaa1111bbbb2222** could be the name of a log stream for user `decrypt-user` and workflow `w-a1111222233334444`. +The format for the workflow log stream depends on which logging mechanism the workflow uses: + + * If the workflow uses a logging role, the format is ``username`.`workflowId`.`uniqueStreamSuffix``. For example, **decrypt-user.w-a1111222233334444.aaaa1111bbbb2222** could be the name of a log stream for user `decrypt-user` and workflow `w-a1111222233334444`. + + * If the workflow uses a structured log destination, the format is ``workflowId`/`executionId``. For example, **w-a1111222233334444/aaaa1111bbbb2222** could be the name of a log stream for workflow `w-a1111222233334444`.