Skip to main content

Secret Management

All secrets are stored in AWS Secrets Manager under the il-central-1 region.

⚠ïļ Important: All secrets are stored twice, and values may differ:

  1. Production secrets: Under the legionsecurity AWS account
  2. Development secrets: Under the legionsecurity-dev AWS account

👉 Always make sure to update secrets in both accounts when making changes.

Backend Secrets​

  • Secret manager instance: backend_secrets
  • Location:
    AWS Console → Login to dev/prod account → Secrets Manager → Region: il-central-1 → Select backend_secrets → Click Retrieve/Edit

Using secrets locally for testing​

To run tests locally, all secrets must be copied into a .env file, as they are loaded from it during tests.
We provide a script to help with this:

  1. Ensure you're logged in via AWS SSO: 
    aws sso login --sso-session {sso-session-name}
  2. In the backend repo, run: 
     py scripts/generate_env_secrets.py
  3. After execution, the script will output all secrets. Copy and paste them into your .env file under the appropriate section.

Infrastructure (Infra) Secrets​

  • Stored under: infra_secrets
  • Location:
    AWS Console → Login to dev/prod account → Secrets Manager → Region: il-central-1 → Select infra_secrets → Click Retrieve/Edit

Deployment behaviour​

During infrastructure deployment, secrets are pulled from this central location in il-central-1 and propagated to all other deployed regions (only if they are configured and used in the Pulumi infra setup)

How to add a new secret​

  1. Determine the correct storage location:
    • backend_secrets - the secret is used at runtime by the backend service.
    • infra_secrets - the secret itself is required for the infra deployment (e.g. api key for Cloudflare to configure DNS entires)
  2. Add the secret in the il-central-1 region in both the dev and prod Secret Manager stores
  3. Add the new secret to the Pulumi server infra configuration
  4. Run the Pulumi infra deployment in all regions (this will add the new secret to the service runtime)