Under the hood
No functional change found in sandboxed AWS credential detection and masking
What
The sandbox's detection and masking of an implicit AWS credential pair (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN) is still present with the same messaging; the underlying code appears to have only been renamed internally.
Why
This is an internal cleanup with no expected effect on how AWS credentials are handled inside the sandbox.