{"version":"2.1.271","anchor":"sandbox-aws-credential-pair-collision-logging-no-functional","canonical_anchor":"sandbox-aws-credential-pair-collision-logging-no-functional","heading":"Sandbox AWS credential-pair collision logging: no functional change found","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/sandbox-aws-credential-pair-collision-logging-no-functional","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Sandbox AWS credential-pair collision logging: no functional change found\n\nSandbox AWS credential-collision handling was renamed internally with no functional change found\n\n**What**\n\nThe logic that decides which AWS access-key\/secret\/session credential pair wins when multiple environment variables collide (the `credentials.awsPairs` resolution logic) is still present with the same warning messages, just with renamed internal variables.\n\n**Why**\n\nThis is internal cleanup only; the previously reported behavior for dropping conflicting AWS credential pairs is unchanged.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}