I'm looking for a way to centralize secrets across multiple environments and possibly use 1Password as a basic key-value store. During deployments, I'd like a script to load secrets into process memory as environment variables and also provision selected values into AWS services. For example, some Lambda configuration could live in Parameter Store, while a script initializes standard values from 1Password when creating new AWS accounts. I'm not set on 1Password, but it seems like a convenient option for AWS credentials and other secrets. Does buying it through AWS Marketplace provide any meaningful benefit compared with subscribing directly?
2 Answers
You may also want to evaluate OpenBao. It’s an open-source secrets-management option designed for storing and retrieving secrets programmatically, and it may fit better than a password manager if automated deployments, machine authentication, rotation, and environment-specific access controls are central requirements. Whichever tool you choose, avoid broadly exporting secrets as environment variables when possible, limit their lifetime and scope, and use IAM-based access for AWS services such as Parameter Store or Secrets Manager.
The Marketplace listing is generally the same 1Password product and subscription. The main benefit is billing convenience: charges appear on your AWS invoice and may count toward an existing AWS spending commitment or help with consolidated enterprise billing. If those billing considerations don’t matter to you, buying directly is usually simpler and may avoid effectively giving AWS a share for no functional difference.
Exactly. Marketplace mainly makes sense if consolidated billing or reaching a negotiated AWS commitment threshold is important. It doesn’t add special integration features by itself.