Bitwarden Secrets Manager on EKS – Per-App Integration with Atlantis

Bitwarden Secrets Manager on EKS – Per-App Integration with Atlantis Sync secrets from Bitwarden Secrets Manager into Kubernetes on EKS using the sm-operator, AWS Secrets Manager for the machine token, and the Secrets Store CSI Driver. This guide expands on the base integration with a per-app, per-namespace pattern and uses Atlantis as a concrete example. It covers Terraform, Kustomize overlays, Argo CD, sync waves, and troubleshooting. Note: Use placeholder values for org IDs and secret IDs. Never commit real tokens. For production, follow least-privilege IAM and rotation practices. 1. Overview What this guide does: Integrates Bitwarden Secrets Manager with EKS via sm-operator, AWS Secrets Manager, and Secrets Store CSI Driver Uses a per-app namespace pattern : each app (e.g. Atlantis) gets its own SecretProviderClass, bw-auth-token-sync , and BitwardenSecret in its own namespace Walks through Terraform (EKS + Pod Identity per app), manifests, Argo CD Applications, validation, and for