elastic-beanstalk

I am trying to deploy an application to EC2 with elastic beanstalk and tomcat. In order to try and fix a different problem I had I changed my uploaded file from a .war to a .zip in order to include a .ebextensions folder. However, now I get the following error when trying to enter the website: I figured that there might be a problem with the .config file I added, so I tried zipping the .war file alone, however I get the exact same error, so this is ruled out. TL/DR: Put 2 .war files in the .zip file instead of 1. I realize this post is nearly 18 months old. But I experienced exactly the same

In AWS Elastic Beanstalk, there is a wizard flow for deploying node.js apps. When I get to the step for "upload your own" application source, it describes in generic terms their 3 requirements: zip file, less that 500MG, no parent folder. But they stop there. No specifics. I dropped out to bash and ran... ng build --prod ...and now have a dist folder. So... what do I include in my zip file and at what folder level? I have tried just /dist, and also /myapp/dist which included all the other loose files in /myapp but no other sub folders such as /src. I have looked all over the web, but don't see

Every time I push to a git remote there is a line that says "remote: processing..." This usually goes really fast when I push to github or Bitbucket but when I push to an Amazon Beanstalk deployment it takes between 10 seconds and 2 minutes". What exactly is the remote "processing"? I assume you refer to git aws.push that takes so long. The reason is that git push submits your changed files (commits) to the remote git repository while git aws.push issues AWS API commands to transfer your files to Elastic Beanstalk. To see that, you can check out the script that's executed during this command.

I have my MongoDB deployed in an EC2 instance, nice and steady. I will (hopefully) have my Elastic Beanstalk load-balanced Web App launched soon using Docker. However, I feel like my Database is too sensitive to dockerize or beastalk-ize, so I wanna keep it in a plain EC2 instance. My issue is with regard to the security groups. How can I create a security group that will only accept MongoDB traffic (port 27017) from the Elastic Beanstalk? Since EC2 instances will get created and destroyed arbitrarily, maybe I can get the least-common subnet of those? When you create your Elastic Beanstalk

We have SOLR in our app directory on EC2 server and not on our local git repository. When we are pushing our local repository to EC2, it is erasing the Solr directory. We have put the directory name in our .gitignore file, but it still overwrites the SOLR directory. How do we prevent overwriting certain files that are only on the EC2 server (in the var/app/current directory)? AWS Elastic Beanstalk instances do not have persistent storage. EC2 instance is restored with default filesystem on each git push. You can persist SOLR files in S3 and automatically retrieve them on container startup with

So I have a functionality in a Django Elastic Beanstalk app that works like so: Download a file Parse the file, run some calls to API's with the data from the file Update the database of the EB instance with the new data In testing instances where I just set up a local cron job. I just called wget on a specific URL of my Django application and it will run the command. My problem is how to handle this in a multi-instanced Elastic Beanstalk application. Only one instance of my EB application should run this command. I want to avoid race conditions on the database and redundant calls to external

I have a node.js application packaged in a docker image hosted in a public repository. I have deployed that image in an AWS Beanstalk docker application successfully. The problem is that I was expecting the Beanstalk application to be automatically updated when I update the image in the public repository, as the following configuration sugggests. Dockerrun.aws.json: { "AWSEBDockerrunVersion": "1", "Image": { "Name": "peveuve/dynamio-payment-service", "Update": "true" }, "Ports": [ { "ContainerPort": "8000" } ], "Logging": "/var/log/dynamio" } The Dockerfile is very simple: FROM node:4.2.1

Trying to upload my rails app to elastic beanstalk. I have successfully deployed my app and created postgres database. My app works on sqlite3 on development server. my eb status is ready and health is green. my eb logs file; /var/log/nginx/error.log ------------------------------------- 2016/05/27 11:15:44 [warn] 2797#0: conflicting server name "localhost" on 0.0.0.0:80, ignored 2016/05/27 11:27:26 [crit] 2805#0: *140 connect() to unix:///var/run/puma/my_app.sock failed (2: No such file or directory) while connecting to upstream, client: 172.31.26.77, server: _, request: "GET / HTTP/1.1",

I have a auto scaling Elastic Beanstalk app running Python where I want to use PIL. When I do, it says that my jpeg decoder is missing and that I need to install libjpeg. So I follow AWS official guides for "configuration files" here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers.html#customize-containers-format But I can't get it working. If I understand the guides correctly I should set up a directory called .ebextensions in my application folder. Inside my .ebextensions I should

Using the Elastic Beanstalk web console, I've launched a new Web Server 1.0 environment with: Predefined configuration: Node.js, 64bit Amazon Linux 2014.09 v1.0.9 Environment type: Load balancing, autoscaling and have set Proxy Server to none . I've successfully compressed & uploaded via the console my code: package.json { "name": "cool", "version": "0.0.0", "dependencies": { "ws": "0.4.x" } } server.js var wss = new (require('ws')).Server({port: (process.env.PORT || 3000)}) wss.on('connection', function(ws) { console.log('connected') ws.on('message', function(message) { console.log(message)