Dev News Daily ENDE

AWS KMS keys can now be shared through Resource Access Manager without editing key policies

AWS Key Management Service now integrates with AWS Resource Access Manager, AWS said on 16 November. KMS keys can be shared across accounts, within an organisation in AWS Organizations and with specific IAM roles and users by creating a resource share: select the keys, choose a managed permission and name the principals.

The managed permission can be one of AWS's own for common cases or a customer managed permission. Such a permission can be written by the key owner or by a trusted party, such as a SaaS provider or a central security team, who publishes the policy once. The key owner fills in the values that scope it to their environment and attaches it to the share; the existing key policy is not changed. When the author releases a new version of the permission, the owner decides when to apply it.

The feature rests on new RAM capabilities that apply to every resource type RAM supports. Customer managed permissions can now hold several policy statements and more IAM condition operators, including StringNotEquals, BoolIfExists and ArnLike, with the ForAnyValue and ForAllValues prefixes. Parameterised permissions let an author leave a placeholder that each share owner fills in, so one permission can serve many accounts. Permissions can also be published and shared across accounts, so the author maintains a single version and can see every resource share that uses it.

KMS key sharing with RAM is available in all Regions where both services run, except Middle East (UAE) and Middle East (Bahrain).

AWS KMS keys can now be shared through Resource Access Manager without editing key policies
AWS KMS keys can now be shared through Resource Access Manager without editing key policies — Dev News Daily

Why it matters

Cross-account access to a KMS key used to mean hand edits to the key policy. AWS now offers a route where the party that needs the access writes the policy and the key owner only fills in values and decides when a new version applies - with the key policy itself left as it was.

Written by Victoria Shinder.