Loading content
Amazon Web Services Secrets Manager is a managed cloud service for securely storing, rotating, and retrieving database credentials, API keys, and other secrets. It supports automatic rotation, server-side encryption with AWS KMS, fine-grained IAM access control, and audit logging for compliance. It integrates with AWS services and runtime environments.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
AWS Secrets Manager is a managed service for securely storing, retrieving, and rotating credentials, API keys, and other secrets.
Secrets Manager grew from the need to keep secret configuration values out of source code, images, and manual deployments. AWS combines storage, access control, and optional rotation in one service.
An application requests a named secret at runtime. Secrets Manager checks the IAM permission and returns the current value; rotation can renew it on a defined schedule. Applications store only the reference, while policies and logs constrain and expose access.
A secret contains confidential values such as passwords, tokens, or keys.
Applications read secrets through an authorized API instead of embedding them in source.
Regular changes reduce the lifetime of compromised credentials.
IAM rules limit which identity may use a given secret.
Secrets Manager reduces the risk of credentials embedded in applications and deployment artifacts. Rotation, least privilege, failure behavior, and cost need to be part of operations.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.