Try changing the efs-mount to read the following, the directory clearly doesn't exist so lets just create it.

container_commands:
  1chown:
    command: "chown webapp:webapp /wpfiles"
  2create:
    command: "sudo -u webapp mkdir -p wp-content/uploads"
  3link:
    command: "sudo -u webapp ln -s /wpfiles wp-content/uploads"

2create will create the directory owned by the webapp user and should let you continue.

I just faced the same issue. I am going to assume deploying via the AWS console. That is how I started.

STEP 1: I checked if there was an actual directory wp-content/uploads in wordpress-beanstalk and there was not. It might get created on the first WP upload So, I created the folder, rezipped the application, and deployed to Beanstalk via the AWS Console.

I still received the same error and moved on to step 2

STEP 2: Run EB DEPLOY from the command line from my local wordpress-beanstalk directory

• eb init

  • choose region (if you already created your app should be this region)
  • if you already created application choose that wordpress-beanstalk for example

• eb use name of your environment

• eb deploy

I am not certain that Step 1 is related to Step 2, but was able to successfully deploy facing the same issue using EB CLI.

This is the mounting error of EFS . EB is using EFS storage to store the wordpress files .

Please check the no.7 in documentation .

"Modify the configuration files in the .ebextensions folder with the IDs of your default VPC and subnets, and your public IP address."

Please edit the efs-create.config file inside the .ebextension folder.