You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, your account ID will not be masked in workflow logs. This was changed from being masked by default in the previous version. AWS does consider account IDs as sensitive information, so this change reflects that stance. You can revert to the old default and mask your account ID in workflow logs by setting the mask-aws-account-id input to true.
...which has these contradictory statementst:
account ID will NOT be masked;
AWS DOES consider account IDs as sensitive information
Further in the README it states:
Your account ID is not masked by default in workflow logs since it's not considered sensitive information.
From the default behaviour presumably AWS does NOT consider account IDs as sensitive; the initial statement is incorrect.
The text was updated successfully, but these errors were encountered:
** Note **
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the issue
In the README it states:
By default, your account ID will not be masked in workflow logs. This was changed from being masked by default in the previous version. AWS does consider account IDs as sensitive information, so this change reflects that stance. You can revert to the old default and mask your account ID in workflow logs by setting the mask-aws-account-id input to true.
...which has these contradictory statementst:
Further in the README it states:
Your account ID is not masked by default in workflow logs since it's not considered sensitive information.
From the default behaviour presumably AWS does NOT consider account IDs as sensitive; the initial statement is incorrect.
The text was updated successfully, but these errors were encountered: