sqsd | simple alternative to the Amazon SQS Daemon | AWS library

Turns out that Beanstalk likes to try to do things its own way, and I have it set to the Nodejs platform so it is going to try to run npm install and npm start at all costs.

I ended up disabling it through not including my package.json or package lock files in CodeBuild's artifact. This at least stopped it from trying to run its own NPM install. Not exactly efficient and I port all my node_modules over but it is zipped as an artifact from CodeBuild and sent to Beanstalk for deployment.

The nginx setting you are trying to use (/etc/nginx/conf.d/proxy.conf) is for Amazon Linux 1.

Since you are probably using Amazon Linux 2 you should be using different files for customizing nginx. For AL2, the nginx settings should be in .platform/nginx/conf.d/, not in .ebextentions as shown in the docs.

Therefore, you could have the following .platform/nginx/conf.d/myconfig.conf with content:

Many thanks to @GrahamDumpleton for his help. The solution I used was:

-Edit the wsgi.conf file found at /etc/httpd/conf.d/wsgi.conf on the Elastic Beanstalk EC2 instance.

To do this I used the command sudo -e /etc/httpd/conf.d/wsgi.conf to open the editor, hit INSERT to start editing, and added WSGIApplicationGroup %{GLOBAL} anywhere in the file. I then his ESCAPE and used the command :wq to save the changes.

After this I selected Restart App Servers from the Action drop-down of the Elastic Beanstalk console. After this, the program would load and give the AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND' message, but not the error messages afterwards. In addition, the application would receive SQS messages and run as expected.

One thing to note, is that it appears the wsgi.conf file will revert if any configuration changes are made to the Elastic Beanstalk configuration. I'm not sure of a way around this, but if I find something I'll post it here.

Thanks again to @GrahamDumpleton for his prompt response and help in solving this issue!

This is almost certainly because your latest deploy has failed the health check. See the contents of /var/log/aws-sqsd/default.log (which can be found via the "Logs" section of the environment). This will give you a more informative error, such as:

service healthcheck to URL "http://localhost/" failed with http status code "500"

It finally works !

It seems the error occured because I forget to configure the format_listener of my FOSRest Route.

The problem is the leading space in the schedule. It works if you change it to this:

It works just fine for me on localhost

• Run like this on console node server.js (where server.js has the code you posted)

• Did you double check the PORT env variable when you start the server? If you didn't set PORT env variable, make sure to go to http://localhost:8080/ on browser. To check env variables on console, you can execute the command env

• Do you have an index.html so that html = fs.readFileSync('index.html'); works?

By default, jobs will be re-posted if your web server doesn't respond within five minutes. There are a few possible approaches:

1) Increase the "Inactivity Timeout" under Configuration/Worker Configuration/Advanced Options. The maximum value is 1800 (30 minutes.)

2) Make your jobs run more quickly by adding processing power or splitting them into smaller chunks.

3) When you receive a job, execute it in a background thread and return from the main thread immediately.