Recommended Approach
Qovery recommends using AWS Secrets Manager with Doppler to ease the synchronization of AWS Secrets Manager with Qovery.Integration Methods
API Keys
You can store your AWS API keys (Access Key ID and Secret Access Key) in Qovery’s environment variables and reference them in your application as standard environment variables. Your application can then use the AWS SDK to connect to AWS Secrets Manager using these credentials.Assume Roles (Recommended)
For EKS clusters, the recommended approach is to use IAM roles for service accounts (IRSA). This allows your applications to assume an IAM role and connect to AWS Secrets Manager without storing static credentials. This method provides:- Enhanced security with no static credentials
- Automatic credential rotation
- Fine-grained access control
- AWS CloudTrail audit logging
- Create an IAM role with permissions to access AWS Secrets Manager
- Configure the role to be assumable by your Kubernetes service account
- Annotate your application’s service account with the IAM role ARN
- Use the AWS SDK in your application to access secrets