amazon-sqs

I have a small set of messages in an SQS queue, that are not deleted even though a deletion request sent to the AWS endpoint returns with a 200 response. The messages are processed by my application fine, and the deletion request is sent fine too. I'm using the Java AWS SDK 1.3.6. Has anyone else experienced this problem? Whoops - the queue was accidentally set to defaultVisibilityTimeout=0 . Changing this to a positive value fixed the problem. This still raises a few questions though: Why did this only affect some messages? Perhaps some took longer to process? Why did Amazon return a 200 for

I have a cloudwatch alarm configured : Threshold : "GreaterThan 0" for 1 consecutive period, Period : 1 minute, Statistic : Sum The alarm is configured on top of AWS SQS NumberOfMessagesSent. The queue was empty and no messages were being published to it. I sent a message manually. I could see the spike in metric but state of alarm was still OK. I am a bit confused why this alarm is not changing its state even though all the conditions to trigger this are met. I just overcame this problem with the help of AWS support. You need to set the period on your alarm to ~15 minutes. It's got to do with

I am looking for a sample .Net application that continuously checks Amazon SQS for new messages and when one is found, perform an action and remove it from the queue. My goal is to have an app running on EC2 that watches my SQS queue for new messages. When one is found, a call will be made to one of several web based APIs and the message will be deleted from the queue. Can someone point me to an example of something similar ? edit Would this type of application best be created as a windows service? The AWS SDK for .NET features samples for several Amazon Web Services , including an Amazon SQS

I'm currently working on a website developed with Symfony2 and I need to send messages in an Amazon SQS. In order to do that I added to my composer.json : "aws/aws-sdk-php": "2.4.*" Then when I try to create a queue or list queues I've got a 403 error saying: Access to the resource https://sqs.us-west-2.amazonaws.com/ is denied. EDIT: added the full error message AWS Error Code: AccessDenied, Status Code: 403, AWS Request ID: 2fe34c11-7af8-5445-a768-070159a0953e, AWS Error Type: client, AWS Error Message: Access to the resource https://sqs.us-west-2.amazonaws.com/ is denied., User-Agent: aws

I am new to Celery and SQS , and would like to use it to periodically check messages stored in SQS and then fire a consumer. The consumer and Celery both live on EC2 , while the messages are sent from GAE using boto library. Currently, I am confused about: In the message body of creating_msg_gae.py , what task information I should put here? I assume this information would be the name of my celery task ? In the message body of creating_msg_gae.py , is url considered as the argument to be processed by my consumer ( function do_something_url(url) in tasks.py )? Currently, I am running celery with

I'm looking for help with an architectural design decision I'm making with a product. We've got multiple producers (initiated by API Gateway calls into Lambda) that put messages on a SQS queue (the request queue). There can be multiple simultaneous calls, so there would be multiple Lambda instances running in parallel. Then we have consumers (lets say twenty EC2 instances) who long-poll on the SQS for the message to process them. They take about 30-45 seconds to process a message each. I would then ideally like to send the response back to the producer that issued the request - and this is the

I've observed an abnormal (well, in my POV) feature, where when I setup SQS to trigger a Lambda, when new messages arrive, lambdas get triggered with more than 1 record/message inside its event body. Full setup is S3 (PutObjectEvent) -> SNS topic -> SQS -> Lambda. The abnormal behaviour is that for example, let's say I put 15 objects inside S3, which then forwards an event to SNS per each object, which then I can observe, SQS gets populated with 15 messages. However, when Lambdas start triggering, out of those 15 messages, only 11 Lambdas trigger, some of them containing more than 1 record