{"version":"2.1.224","anchor":"sandbox-credential-restrictions-no-longer-lost-when-settings","canonical_anchor":"sandbox-credential-restrictions-no-longer-lost-when-settings","heading":"Sandbox credential restrictions no longer lost when settings are merged","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sandbox-credential-restrictions-no-longer-lost-when-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Sandbox credential restrictions no longer lost when settings are merged\n\nManaged limits on which AWS credentials the sandbox may use survive settings merges now.\n\n**What**\n\nRestrictions on which AWS credential forms the sandbox may use now survive merging of managed settings into child settings, instead of being dropped at the merge boundary.\n\n**Details**\n\n- Inheritance now carries the `sandbox.credentials.sigv4` deny list, whose values are `streaming`, `presigned` and `sigv4a`.\n- A normalized `awsPairs` list of allowed AWS key pairs is carried through the same merge.\n\n**Evidence**\n\n`sigv4a`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}