AWS Secrets Manager console now allows you to specify a custom customer managed AWS Key Management Service (KMS) key when creating secrets. You can now provide a KMS key Amazon Resource Name (ARN) directly in the console, in addition to selecting from the pre-populated list of KMS keys in your current account.
Previously, when creating a secret through the AWS Secrets Manager console, you could only select customer managed KMS keys from a dropdown list that displayed keys within the same AWS account. With this enhancement, you can now enter a KMS key ARN to use a key from a different account, aligning the console experience with the existing API capabilities. This simplifies cross-account encryption workflows and provides greater flexibility in managing your encryption keys across multiple accounts.
This feature is available in all AWS Regions where AWS Secrets Manager is available. To learn more about using customer managed KMS keys with AWS Secrets Manager, visit the AWS Secrets Manager documentation.
Categories: general:products/aws-secrets-manager
Source: Amazon Web Services
Latest Posts
- MC1476200: Microsoft 365 Copilot Business Adds Default Usage-Based Billing for Easier AI Access
- MC1227622: Microsoft Teams Moves Android Device Management from Teams Admin Center to Teams Rooms Pro Management Portal
- MC796790: Microsoft 365 Unifies App and Agent Availability and Installation Management Across Teams and Outlook
- Rules – Handle missing values with coalesce()
