Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hello guys,
I've developed a api using laravel and it's all working properly. I'm using elasticbean to run my application. My problem is: Every time that i do some change on my application, i have to access my instance through ssh and create manually my .env file. The problem is, while i'm still testing, that's ok, but when the application scales, new instances will not have the .env file, because aws elasticbean does not consider any changes made through ssh. I'm using .ebextensions, but i don't know how can i do this process of download the .env file from s3 for example. Has anyone ever experienced this issue before that could help me?
Thank you
Since no one answered, i've come to the solution a time ago and forget to write it here:
All you have to do is use the eb setenv command on your project folder. Then every time that a new instance is created, environments variables will be automatically created on it.
For example: eb setenv DB_CONNECTION=mysql ...
Link to the documentation: https://docs.aws.amazon.com/pt_br/elasticbeanstalk/latest/dg/eb3-setenv.html
Please or to participate in this conversation.