This open source External Secrets operator can be leveraged to pull secrets from AWS Secrets Manager, AWS Parameter store, Hashicorp Vault and various other cloud secrets providers. This operator also supports EKS Fargate.
With AWS Secrets Manager, you can establish a private connection between your VPC and Secrets Manager by creating an Interface VPC endpoint which lets you privately access Secrets Manager APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. It is more secure as the network traffic between your VPC and Secrets Manager does not leave the AWS network.
You might want to look into AWS Secrets and Configuration Provider (ASCP). This approach enables secrets from Secrets Manager and parameters from Parameter Store to be mounted as files in Amazon EKS pods. The GitHub project is here.
Relevant questions
Greengrass access local device environment variables
Accepted Answerasked 7 months agoAre the environment variables used in the task definitions for the ECS service encrypted?
Accepted Answerasked 7 years agoAL2 - predeploy script and environment variables
asked 2 years agoNeed help in configuring and accessing env variables in aws code build
asked 2 years agoHow do I access Lambda environment variables in IoT Greengrass?
Accepted Answerasked 2 years agoWhat is the best practice and downtime for migrating an existing AWS environment to use the Transit Gateway?
Accepted Answerasked 3 years agoWhat is the best way to generate a visual diagram of the AWS environment which includes VPC, VPN
Accepted Answerasked 2 years agoWhat is the best way to work with kubernetes and environment variables in containers?
asked a month agoTrying to use environment variables
asked 2 years agoCodeDeploy Environment Variables On Windows
asked 6 months ago