aws-sqs | AWS Simple Queue Service library for Node.js | Runtime Evironment library

CDK doesn't have backwards compatibility in minor version upgrades.

That means that your cdk.Construct from package

have you tried doing maven update or rebuild to get the import into scope?

At first , apache-camel tag is excess here. As second, you missed that asker is using spring context and you are using blueprint context. Try something like this:

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!

I changed the listner method signature to

If you don't specify a name for something CloudFormation will generate a name based on the name of the stack and the name of the resource. They will add some extra to the end of it to make sure it's unique.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-name.html

Try to use setHeader instead of setProperty

'Version' here specifies which version of 'SQS' service to use and should be specified as a query parameter and not the header e.g.:

The answer you linked is accurate.

You must write a program that polls SQS for a message (or up to 10 messages). It is more efficient to use long polling because you require less calls.

If you wish to know about a message very quickly, then you will need to poll continually. That is, as soon as it comes back and says "nothing to receive", you should call it again. To reduce the frequency of these calls, you can set long polling, up to a maximum of 20 seconds. This means that, if there are no messages in the queue, the ReceiveMessages() option will take 20 seconds before it returns a response of "no messages". If, however, a message arrives in the meantime, it will respond immediately. The long polling option is specified when making the ReceiveMessages() request.

If you do not require instant notification, your application could call less often (eg every minute, or every few minutes). This would involve less calls to Amazon SQS.

When making the ReceiveMessages() call, your application can request up to 10 messages. This means that multiple messages might be returned.

Once your application has finished processing a message, it must call DeleteMessage() to have the message removed from the queue. This is a failsafe that will automatically put the message back on the queue if there is a problem with the application and the message doesn't get correctly processed.

This is a great video from the AWS re:Invent conference that explains Amazon SQS (and Amazon SNS) in detail: AWS re:Invent SVC 105: AWS Messaging