Changing file permissions on AWS Elastic beanstalk environment

amazon-web-serviceselastic-beanstalk

I have an AWS worker tier environment and I want to change file permissions so i can write logs to file. I have tried doing this in eb extensions .config file but cannot get it to work.

If the command is run (sudo chmod 777 /path/to/file.rb) under the 'commmands:' then its executed before the env is built and does not work.

If its under 'container_commands:' then it also does not work.

I cannot find any guidance on how to do this in the AWS docs (it may of course be there)

Help much appreciated.

Best Answer

If your challenge is that you need to change the permissions after your application has been deployed, then you'll need to use a post-deploy hook. Unfortunately post-deploy hooks are not officially supported by AWS, but they seem to be pretty widely used.

I done similar things using the technique described here: https://forums.aws.amazon.com/thread.jspa?messageID=493887

Your hook might look something like this:

files:
  "/opt/elasticbeanstalk/hooks/appdeploy/post/99_change_permissions.sh":
    mode: "000755"
    owner: root
    group: root
    content: |
      #!/usr/bin/env bash
      chmod 777 /path/to/file.rb

Related Solutions

AWS Elastic Beanstalk File Upload Limit Issue

If you're using NGINX or other proxy server, it may be related to it's client_max_body_size directive. To fix it create folder .ebextensions in app root, and a file .ebextensions/01_nginx.config. Then tell build script to add this directive while building your environment, adding this to your created .ebextensions/01_nginx.config:

container_commands:
  01_reload_nginx:
    command: "service nginx reload"
files:
    "/etc/nginx/conf.d/proxy.conf":
      mode: "000755"
      owner: root
      group: root
      content: |
        client_max_body_size 25M;

Commit your folder to git, if you're using it. Then eb deploy, cross fingers and try to upload your 6MB PDF.

However, according to my experience, sometimes you have to completely rebuild entire environment to make it work.

Elastic Beanstalk – How to Force HTTPS

I think you need to specify what Elastic Beanstalk environment that you use (see: Supported Platforms), because different environment has different configuration.

Basically, you need to customize:

Elastic Load Balancer:
- Listen on port 80 and proxy it to EC2 instance port 80.
- Listen on port 443 and proxy it to EC2 instance port 443.
EC2 Web Server/Proxy:
- Listen on port 80 and response with redirect to HTTPS.
- Listen on port 443 and serve the request.

To customized it, you can use CLI or .ebextensions.

You can check on Enable HTTPS and HTTP-Redirect on AWS Elastic Beanstalk. It tells you how to configure Elastic Beanstalk Single Docker Container serve HTTPS and HTTP (redirect to HTTPS). You can adjust the config as your need.

Best Answer

Related Solutions

AWS Elastic Beanstalk File Upload Limit Issue

Elastic Beanstalk – How to Force HTTPS

Related Topic