Log file permissions error on AWS elastic beanstalk with Laravel 6:

It happens ALL THE TIME, really annoying. Don't know what AWS image you are using, but the AWS AMI uses webapp as the web user, not apache or ec2-user as the file shows. In that case, the webapp user has no access rights over those files.

But even instructing AWS to give permissions to the files and folders to the correct user (using .ebextensions files), sometimes, for mysterious reasons, it creates things as the root user. I'm really thinking about put the ec2-user and webapp into the root group, because I don't know how to prevent things being created as root.

@claudsonm

AWS image

PHP 7.3 running on 64bit Amazon Linux/2.9.0

Is it always this hard dealing with AWS in general? I've had nothing but problems.

So do I just have to give webapp access 775 permissions to the storage/logs folder? Or do I have to create an .ebextensions file and some how tell AWS to give permissions to webapp? Is there anything in the docs or any StackOverflow threads about this?

Sorry, I'm just a little bit confused.

Actually I just got it!

sudo chown $USER:webapp ./storage -R

find ./storage -type d -exec chmod 775 {} \;

find ./storage -type f -exec chmod 664 {} \;

If you think everything looks good I'll give you the best answer, since you pointed out that

AWS AMI uses webapp as the web user, not apache or ec2-user

Thank you so much!

Yeah, that's the way to go.

Things run smoothly most of the times. But sometimes a new deployment gets triggered and even with those commands inside the .ebextensions files things get created as root, and we are back to it.

But there is this repo (https://github.com/rennokki/laravel-aws-eb) with really great insights. It helped me to setup supervisor. Maybe it helps you too.

If someone knows how to tackle that, would be much appreciated.

I'm having this exact problem with an EB. I have no idea why the error log it's creating is owned by root. Pulling my hair out at the moment.

I was having a very similar problem but with using EB with Docker. To fix this I added a new permissions.config file in .ebextensions

commands:
  command block:app
    command: |
      groupadd -g ${DOCKER_PERMISSIONS_ID} www
      useradd -u ${DOCKER_PERMISSIONS_ID} -ms /bin/bash -g www www
container_commands:
  changePermissions:
    command: chown -R www:www /var/app/staging

This adds a new group and user (with a same id) and assigns it where my project is extracted. "/var/app/staging" may be different for you if you're using a different stack (see https://aws.amazon.com/premiumsupport/knowledge-center/elastic-beanstalk-mount-efs-volumes-app/) The ${DOCKER_PERMISSIONS_ID} is coming from a variable in my .env file. This ID needs to be unique to other users in the instance(s) being deployed. ec2-user in Docker Amazon Linux 2 is 1000, so DOCKER_PERMISSIONS_ID cannot be 1000

If the EB stack you're using is also docker and you have a dockerfile using php-fpm with docker-compose, ensure the DOCKER_PERMISSIONS_ID is also the same ID for that image