elastic-beanstalk

I would like to view SQS messages before they get picked up by sqsd on my Elastic Beanstalk intstance. Is there a way, once ssh'ed into the instance, that sqsd can be stopped / started as a service all together? For the purpose of debugging you may stop sqsd by running sudo service aws-sqsd stop on the instance. You can check the status by running sudo service aws-sqsd status . Note this is not recommended for a production service but for the purpose of debugging you may try this. 来源： https://stackoverflow.com/questions/24172661/start-stop-sqsd-daemon-on-elastic-beanstalk-to-view-sqs-queue

I have problem with execute command after deploy, i have some node.js project and script, this script use some bin from node_modules, if i write my command for script in .ebextensions/.config he execute before npm install and return error ( "node_modules/.bin/some": No such file or directory ). How i can execute command after deploy. Thanks. siavolt I found the following solution I add to beanstalk config next command: commands: create_post_dir: command: "mkdir /opt/elasticbeanstalk/hooks/appdeploy/post" ignoreErrors: true files: "/opt/elasticbeanstalk/hooks/appdeploy/post/some_job.sh": mode:

I added .ebextensions/start.config file to the root folder of my WAR bundle (as suggested by AWS ), deployed it to Elastic Beanstalk, but nothing happened. Where in the EC2 instance can I see log of this file processing? Or maybe I can see this information in TAIL report of EBT? On a Linux 32 bits Tomcat 7 container, I was able to find logs at: /var/log/eb-tools.log , where I was able to see which of my commands failed. Snapshot the Logs for your Elastic Beanstalk environment through the online console. When you view the logs, search for a section beginning "cfn-init.log". In that section you

I wanted to know if there is an option to STOP Amazon Elastic Beanstalk as an atomic unit as I can do with EC2 servers instead of going through each service (e.g. load balancer, EC2..) and STOP (and START) them independently? The EB command line interface has an eb stop command. Here is a little bit about what the command actually does: The eb stop command deletes the AWS resources that are running your application (such as the ELB and the EC2 instances). It however leaves behind all of the application versions and configuration settings that you had deployed, so you can quickly get started

I am getting the 502 bad gateway error after uploading my application via eclipse and I don't understand why its happening? I created a Sample Application through the AWS Elastic Beanstalk Console. Then I loaded the server in eclipse. Afterwards I published it and got the "Environment update completed successfully." message in the EB Console. However when I go to the url, I get a 502 Bad Gateway error. I looked at the logs to see what went wrong however only thing I found is " failed (111: Connection refused) while connecting to upstream, client: 172.31.11.136, server: , request: "GET /favicon

I am running my rails app on the AWS Elastic Beanstalk platform, which is running a single EC2 instance with Auto Scaling & Elastic Load Balancing. I'm wondering how to run resque , delayed_job or sidekicq or some other solution for background jobs on Elastic Beanstalk. What are the possible options for background jobs on Elastic Beanstalk? Best way to start/stop/restart background jobs could be via init scripts for these tasks. You could have these init scripts triggered as services when instances are launched. More about Customizing ElasticBeanstalk containers for services here . Once done,

I'm trying to serve some static css, png's, etc. from my Pyramid app that's hosted on Elastic Beanstalk. It works fine on my local machine but when I try to run on EB, neither the CSS nor the images are found. Here's the relevant code: From .ebextensions: option_settings: aws:elasticbeanstalk:container:python: WSGIPath: pyramid.wsgi aws:elasticbeanstalk:application: Application Healthcheck URL: /health aws:elasticbeanstalk:container:python:staticfiles: "/static/": "static/" From home.make <link rel="stylesheet" href="/static/css/settings/globals.css"/> <link rel="stylesheet" href="/static/css

We’re trying to create a setup of multiple APIs via the Amazon AWS Elastic Beanstalk (AEB) component. The reason we have chosen AEB is because it provides seamless deployment and scaling for the applications we deploy, without the need to manually create Load Balancers (LB) and scaling rules. We would very much like to keep it this way as we are planning on launching a (large) number of applications and APIs. However, we’re facing a number of challenges with AEB. First and foremost, some of the API’s need to communicate internally, and low latency is a core requirement for us. In order to

OK, odd thing is happening on AWS. I downloaded the AWS .NET developer tools and created an elastic beanstalk default instance. I then, for one reason or another, created another instance via the Visual Studio interface and that instance is where all the clients code / configurations reside. I then returned to the default instance created by elastic beanstalk and terminated it. An hour later, I logged back on and another default instance was up and running. It seems that AWS has detected that I terminated the instance and has spawned another. Some sort of check seems to be in place. Can

I want to configure my staging environment in Elastic Beanstalk to always disallow all spiders. The nginx directive would look like this: location /robots.txt { return 200 "User-agent: *\nDisallow: /"; } I understand that I would want to create a file under the .ebextensions/ folder, such as 01_nginx.config, but I'm not sure how to structure the YAML inside it such that it would work. My goal is to add this location directive to existing configuration, not have to fully replace any existing configuration files which are in place. María Luisa Carrión Donderis I wanted to do the same thing.