amazon-sqs

问题 Folks, I believe I've encountered a minor bug on the newest AWS FIFO SQS, does anyone have a solution for the following error I am getting? I've created a FIFO queue on AWS SQS Management Console (us-west-2 region). To create a FIFO queue, SQS mgmt console requires that you insert a ".fifo" suffix on the queue's name (which is unusual -- "." is not recommended for naming anything on AWS). I've set the appropriate permissions on this queue to receive notifications from a bucket I own on the

问题 We have an SNS queue with multiple subscribers (2 * SQS, 1 * email, etc.). However, we only get the notification for the last subscriber. I.e. when each of them is registered alone we get to notification. So as far as I understand each of them alone is configured all right. I didn't find any relevant AWS documentation about it (limit of subscribers, policies, etc.) Would love to hear any hint about it. Thanks in advance. Solution: the issue was the order in which the SQS permission

问题 Here's my situation: I have a script that gets raw data, saves it in the database, get the item id then posts it to an amazon SQS queue. I have another script (written in PHP) that retrieves the raw data from the db and processes it. (it takes a couple of minutes usually. The missing part is how to retrieve the messages from SQS to be processed. The frequency of new data to process varies, it can go from a few items per hours to dozens of items per minute. One way would be to have a cron job

问题 I have put together these commands to autoscale EC2 instances based on SQS queue size. I have run all commands and my queue is at 10 messages and a single instance hasn't been launched. I am trying to figure out, what SQS queue my cloudwatch alarms are listening to? Also any help to indentify the issus is appreciated! ### Create Autoscaling Policy ### aws autoscaling create-launch-configuration --launch-configuration-name my-lc --image-id ami-551c6d30 --instance-type m1.small aws autoscaling

问题 We can send/receive messages to/from AWS SQS Queue, But Can we update message content which is already in SQS Queue ? If possible , How ? 回答1: Once a message has been sent to an SQS queue (standard or FIFO), the message is immutable. Additionally, it isn't possible to ask SQS for a specific message by its ID. The message is essentially inaccessible until received by a consumer. (Viewing messages in the AWS console might seem to be an exception, but it isn't -- the console acts as a consumer,

问题 I want to be able to process more than 10 SQS messages at a time using a Spring Integration Workflow. From this question, the recommendation was to use an ExecutorChannel . I updated my code but still have the same symptoms. How execute Spring integration flow in multiple threads to consume more Amazon SQS queue messages in parallel? After making this update, my application requests 10 messages, processes those, and only after I make the call to amazonSQSClient.deleteMessage near the end of

问题 Hello and thanks in advance for your time. In my code I am making various requests to AWSSQS which all return AWSTask. I have found working with these AWSTask objects to be very difficult while also trying to keep all the logic specific to AWS in a single class so I can easily switch to a different cloud service if need be. Ideally, what I would like to do is execute a series of AWS tasks asynchronously in a serial fashion. Normally I would just add tasks to a custom Serial Dispatch Queue but

问题 Folks, I would like to set up a message queue between our Java API and NodeJS API. After reading several examples of using aws-sdk , I am not sure how to make the service watch the queue. For instance, this article Using SQS with Node: Receiving Messages Example Code tells me to use the sqs.receiveMessage() to receive and sqs.deleteMessage() to delete a message. What I am not clear about, is how to wrap this into a service that runs continuously, which constantly takes the messages off the

问题 There is reference to a project that creates a channel transport for WCF based on the AWS SQS service. All references end in dead url's. Based on the fact that there were these references I assume it is technically feasible and viable to use SQS as a WCF transport channel with or without security. Is this a valid assumption, and/or does anyone have source or assemblies for such a channel? If no such source exists is it worthwhile to create such a channel for binding .NET WCF in a loose

问题 I am configuring a beanstalk worker environment to deal with periodic tasks When the requested URL is not responding with status 200 Elastic Beanstalk will put the task again in the queue. How can I configure the number or retries? I know the explanation is somewhere hidden behind ErrorVisibilityTimeout , InactivityTimeout , Dead Letter Queues ... but these concepts are still not growing green in my inefficient mind. For example I just want to configure maximum number of retries 0 so there is