elastic-beanstalk

How do I change the configured RDS endpoint of an AWS Elastic Beanstalk environment? E.g. after the RDS database was deleted or should be replaced with a new RDS database. Update The topic remains complex and the AWS Elastic Beanstalk (EB) documentation could still do a better job to clarify available options. The question has been about how to change an RDS endpoint , which seems to be read in two different ways: One could interpret it about how to attach an existing externally managed RDS endpoint to an existing (not new!) EB environment - this is indeed not possible, rather one would need

In my AWS environment there are some load balanced / autoscaled Elastic Beanstalk applications. I would like to have a load balancer in front of them, so any request to http://loadbalancer.com/app1 is routed to the first Elastic Beanstalk app, http://loadbalancer.com/app2 to the second and so on. I tried to set up an application load balancer with different listeners routing to different target groups. Unfortunately my solution is not ideal, because the target groups are bound to a fixed set of EC2 instances, while I want them to be associated to an environment where instances are created or

Trying to deploy a Docker image in AWS Elastic Beanstalk running on a single instance for now. It all works fine, apart from WebSockets which I am using through Socket.IO. Another post suggests to remove nginx, but that is either not possible anymore or just not an option for deployments with Docker. I have a python script that changes the nginx configuration to allow WebSocket connections. When I ssh into the instance and run that script, it works. However, that part of the nginx configuration does not exist yet when ebextensions are run, so I cannot run this script automatically. If you want

We are deploying a java web application in Elastic Beanstalk. The Beanstalk by default provides Redhat instances with Tomcat7 & openjdk. But i want to customize the instances so that i can use Sunjdk. Followed the steps as mentioned here , I launched a new instance from EC2 & installed sun jdk, tomcat7 and created a custom AMI of the instance and provided its ID in Custom AMI id field in edit Environment configuration in BeanStalk. But my Environment Health status is changing to RED, and the application is not deployed. Can you please suggest me a solution for this. I have done exactly what

I have an Elastic Beanstalk worker that can only run one task at a time and it takes some time to do so (from a few minutes to, hopefully, less than 30 minutes), so I'm queuing my tasks on a SQS. On my worker configuration, I have: HTTP connections: 1 Visibility timeout: 3600 Error visibility timeout: 300 (On "Advanced") Inactivity timeout: 1800 The problem is that there seems to be a 1 minute timeout (on nginx?) that overrides the "Inactivity timeout", returning a 504 (Gateway timeout). This is what I can find on the aws-sqsd.log file: 2016-02-03T16:16:27Z init: initializing aws-sqsd 2.0

I would like to switch off Elastic Load Balancer (ELB) for my Elastic Beanstalk environment. Currently I don't need it and I don't want to pay for it. It is possible to delete the ELB in EC2 managment window but then Elastic Beanstalk health state is switched from GREEN to RED. I just found a information that it's not possible. Does someone has a trick how to run Elastic Beanstalk without load balancing and have environment GREEN health state? Since July 2013 Elastic Beanstalk supports "single-instance" environments that have a single container instance running without a load balancer.

My Node.JS project contains references to private NPM repos hosted on github. This works fine locally, but I'm struggling to get this working on Elastic Beanstalk. dependencies: { ... "express": "^4.12.4", "jsonwebtoken": "^5.0.5", "my-private-module": "git@github.com:<my-user>/<my-repo>.git#<my-version>", ... } - What I need is to be able to set up a working SSH configuration for git on my Elastic Beanstalk instances, without having to store secret keys etc in source control. Obviously, the EB instances do not have the needed SSH keys to access my private github repos. If I use HTTPS style

I have been deploying my app without any issues to the beanstalk environment until my latest commit. Now I get this Time Type Details 2013-09-01 10:19:12 UTC+0800 ERROR Failed to deploy application. 2013-09-01 10:19:11 UTC+0800 ERROR Responses from [i-50f40d06] were received, but the commands failed. 2013-09-01 10:19:11 UTC+0800 ERROR Your requirements.txt is invalid. Snapshot your logs for details. 2013-09-01 10:19:11 UTC+0800 ERROR [Instance: i-50f40d06 Module: AWSEBAutoScalingGroup ConfigSet: Hook-PreAppDeploy] Failed on instance with return code: 1 Output: Error occurred during build:

I am deploying a Python Flask application with Elastic Beanstalk. I have a config file /.ebextensions/01.config where among other things I set some environment variables - some of which should be secret. The file looks something like this: packages: yum: gcc: [] git: [] postgresql93-devel: [] option_settings: "aws:elasticbeanstalk:application:environment": SECRET_KEY: "sensitive" MAIL_USERNAME: "sensitive" MAIL_PASSWORD: "sensitive" SQLALCHEMY_DATABASE_URI: "sensitive" "aws:elasticbeanstalk:container:python:staticfiles": "/static/": "app/static/" What are the best practices for keeping certain

I have a set-up running on Amazon cloud with a couple of EC2 Instances running through a load balancer. It is important that the site has a unique(static) IP or set of IPs as I'm plugging in 3rd party APIs which only accept requests made from IPs which have been added to their whitelist. So basically unless we can give these 3rd parties a static IP or range of IPs that the requests from the site will always come from then we would be unable to make any calls to them. Anyone knows how to achieve this as I know that Elastic IPs are not compatible with load balancers? If I were to look up the IP