elastic-beanstalk

I am following the instructions at https://docs.docker.com/compose/django/ to get a basic dockerized django app going. I am able to run it locally without a problem but I am having trouble to deploy it to AWS using Elastic Beanstalk. After reading here , I figured that I need to translate docker-compose.yml into Dockerrun.aws.json for it to work. The original docker-compose.yml is version: '2' services: db: image: postgres web: build: . command: python manage.py runserver 0.0.0.0:8000 volumes: - .:/code ports: - "8000:8000" depends_on: - db and here is what I translated so far {

i'm trying to follow the tutorial: deploy django on aws Elastic Beanstalk when i'm doing the Step 6's substep 5: git aws.push I get a ImportError message: (tryhasinenv)Lee-Jamess-MacBook-Pro:tryhasin h0925473$ git aws.push Traceback (most recent call last): File ".git/AWSDevTools/aws.elasticbeanstalk.push", line 21, in <module> from aws.dev_tools import * File "/Users/h0925473/tryhasin_root/tryhasin/.git/AWSDevTools/aws/dev_tools.py", line 5, in <module> import boto ImportError: No module named boto I have no idea what to do. Can somebody tell me what's wrong? On OSX I found that pip install

I'm trying to deploy my django app via amazon Elastic BeanStalk(using this tutorial ), but getting the following error. ERROR: Elastic Beanstalk could not find any platforms. Ensure you have the necessary permissions to access Elastic Beanstalk. How can i fix this issue? Thanks! Problem is, as @helloV said, your user does not have access. Now this was a complete surprise to me because I was using the root (which I really shouldn't) and I ASSUMED it would just have access. So solution is that you HAVE TO ATTACH a policy as shown in the screenshot below since even the root IAM account does not

In aws elasticbean talk. When we setup extensions in .ebextensions i wonder what is difference between commands and container_commands My command is like this container_commands: 04_insert_app: command: "cat .ebextensions/insertapp_job.txt > /etc/cron.d/insertapp_job && chmod 644 /etc/cron.d/insertapp_job" leader_only: true container_commands is work. commands: has error .ebextensions/insertapp_job.txt not found The major difference between these two pieces is when in the Elastic Beanstalk deployment process they are run. Commands These commands are run early in the deployment process, before

I get the following error when deploying to EB: ERROR: You cannot have more than 500 Application Versions. Either remove some Application Versions or request a limit increase. I went manually and deleted some versions. I don't want deploys to fail because of this limit. Is there a way in Elastic Beanstalk to auto-evict unused versions? A feature was recently added to eb cli (v3.3) to cleanup old versions https://m.reddit.com/r/aws/comments/340ce0/whats_the_thinking_behind_beanstalks_versioning/ Copying command from reddit link $ eb labs cleanup-versions --help usage: eb labs cleanup-versions

I defined an environment variable called MY_ENVIRONMENT_VARIABLE in AWS Elastic Beanstalk's Software Configuration tab. Now I would like to use this environment variable in the "files:" section of a .ebextensions config file. Resources: AWSEBAutoScalingGroup: Metadata: AWS::CloudFormation::Authentication: S3Auth: type: S3 buckets: arn:aws:s3:::SomeS3Bucket roleName: aws-elasticbeanstalk-ec2-role files: "/tmp/application.properties" : mode: "000644" owner: root group: root source: { "Ref" : "MY_ENVIRONMENT_VARIABLE" } authentication: S3Auth container_commands: 01-apply-configuration: command:

Basically I'm structuring my app similar to this GitHub project: https://github.com/zackargyle/angularjs-django-rest-framework-seed Is it possible to deploy both the backend and frontend onto a single PaaS such as Heroku/Elastic Beanstalk? Having a separated REST backend and JavaScript frontend seems like a cleaner/more scalable way to do things rather than trying to mix them together like [django-angular]: ( http://django-angular.readthedocs.org/en/latest/index.html/ ), or having a REST backend mix with the Django app like http://blog.mourafiq.com/post/55099429431/end-to-end-web-app-with

I am having trouble getting my docker elastic beanstalk deploy to read my .ebextensions/setup.config file. The documentation for eb environment configuration says: You can include one or more configuration files with your source bundle. Configuration files must be named with the extension .config (for example, myapp.config) and placed in an .ebextensions top-level directory in your source bundle. However it looks like for Docker that the source bundle is not a .zip or .war file, but a .json file, e.g., the docs say to create a Dockerrun.aws.json file —and it looks like that is the source

I'm running a rails application on Ruby 2.0/Puma instances and am trying to customize the nginx configuration. I need to increase the permitted request size to allow file uploads. I've found some other posts that have lead me to add this to my .ebextensions: files: "/etc/nginx/conf.d/proxy.conf" : mode: "000755" owner: root group: root content: | client_max_body_size 70M; That does create the file as expected, but it doesn't seem to work until I manually restart nginx. Because of that, I've tried to figure out a way to restart nginx with .ebextensions commands, but haven't had any success.

I am running Meteor on AWS Elastic Beanstalk. Everything is up and running except that it's not running Websockets with the following error: WebSocket connection to 'ws://MYDOMAIN/sockjs/834/sxx0k7vn/websocket' failed: Error during WebSocket handshake: Unexpected response code: 400 My unstanding was to add something like: proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; To the proxy config, via my YML config file. Via my .exbextension config file: files: "/etc/nginx/conf.d/proxy.conf" : mode: "000755" owner: root group: root content: | proxy_set_header Upgrade