Level 80
@cuetracker An .env file is just a replacement for actual environment variables. So just load the secrets as actual environment variables and your application will read them just fine.
1 like
Dec 23, 2021
5
Level 1
Environment vars from AWS Secrets Manager
Hi,
I have my app's environment-vars stored in AWS Secrets Manager. These get loaded into my current (raw PHP) application from the task definition when the Docker containers get deployed to ECS. I'm going to switch to Laravel, but can't figure out how to load in these env-vars, as there won't be a .env-file. Would I need to create an empty file during the deploy, and the app takes the values using getenv()? Is there a standard way to handle secrets for a Laravel app when using AWS ECS containers?
Level 1
@martinbean Great. Will give it a try after christmas. Thanks!
Level 5
@martinbean I am also working with secrets manager and i am trying to load the variables like normal but its not pulling them into the places it needs them. do we need to change the way they are retrieved. I have tried the following.
- getenv('KEY')
- env('KEY')
- print_r($_ENV[KEY])
None of these seem to work. Any help would be great on this.
Level 2
@madsynn fetch the secrets and set them via Env::getRepository()->set('KEY', 'Totally secret value') and you will get what you set when call env('KEY')
Level 51
Another option could be the use of a package - this one seems a good option - https://github.com/TappNetwork/laravel-aws-secrets-manager
Please or to participate in this conversation.