Reference your own AWS Secrets Manager secrets in Amazon Bedrock AgentCore Identity
Summary
Amazon Bedrock AgentCore Identity has introduced a new capability allowing users to reference existing AWS Secrets Manager secrets for managing credentials. Previously, AgentCore Identity automatically created and managed secrets, which restricted customer control over aspects like custom tags, rotation policies, and customer-managed AWS Key Management Service (AWS KMS) key encryption. This update enables organizations to provide their own preconfigured secrets, thereby extending existing secrets governance processes to AgentCore. Users gain full control over encryption configuration, rotation, replication, tags, and resource policies. The feature supports referencing secrets from other AWS accounts within the same AWS Region and integrates with third-party secret managers via AWS Secrets Manager external connectors. Example use cases include leveraging existing team secrets, implementing custom rotation, scoping access, enforcing customer-managed encryption, and applying resource tags. Configuration can be done via the AWS Management Console, AWS CLI, or an AI agent.
Key takeaway
For AI Architects and MLOps Engineers building production-ready agentic systems on Amazon Bedrock, this update significantly enhances credential management. You can now integrate your AI agents with existing secrets governance frameworks by referencing preconfigured AWS Secrets Manager secrets. This ensures compliance with organizational security policies, enables custom rotation, and allows for granular access control and customer-managed encryption. Utilize this feature to streamline security audits and maintain consistent secret management practices across your AWS environment.
Key insights
Amazon Bedrock AgentCore Identity now allows referencing existing AWS Secrets Manager secrets for enhanced credential governance.
Principles
- Centralize secret governance for AI agents.
- Maintain full control over secret lifecycle.
- Integrate with existing security policies.
Method
Provide the AWS Secrets Manager secret ARN and JSON key when creating AgentCore Identity credential provider resources via console, CLI, or AI agent.
In practice
- Use existing team secrets for agent APIs.
- Apply custom rotation policies to agent credentials.
- Enforce customer-managed KMS encryption for secrets.
Topics
- Amazon Bedrock AgentCore Identity
- AWS Secrets Manager
- Credential Management
- API Security
- AWS KMS
- MLOps Security
Best for: AI Engineer, MLOps Engineer, AI Architect
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Artificial Intelligence.