AWS Secrets Manager
This feature is released as and should not be deployed in a production environment.
AWS Secrets Manager can be configured in multiple ways. The current version of Kong Gateway’s implementation only supports
configuring via environment variables.
For example, let’s use an AWS Secrets Manager Secret with the name
In this object, you have multiple key=value pairs.
Access these secrets from
my-secret-name like this:
The Vault entity can only be used once the database is initialized. Secrets for values that are used before the database is initialized can’t make use of the Vaults entity.
"description": "Storing secrets in AWS Secrets Manager",
With the Vault entity in place, you can now reference the secrets. This allows you to drop the
You can create multiple entities, which lets you have secrets in different regions:
http PUT :8001/vaults-beta/aws-eu-central-vault name=aws config.region="eu-central-1" -f
http PUT :8001/vaults-beta/aws-us-west-vault name=aws config.region="us-west-1" -f
This lets you source secrets from different regions: