Skip to content
This repository was archived by the owner on Feb 2, 2018. It is now read-only.

Conversation

Jason-Crowe
Copy link

we found that the latest aws sqs api does not return an empty Messages[] block when there are no messages in the queue. instead it returns no message body with http response code 200. we were getting errors in the log as such:
2015-04-02 21:22:37,574 [ERROR] Failed to retrieve messages from queue https://sqs.us-east-1.amazonaws.com/01234567890/AbcQueue-1ABCDEFQ with status_code 200: {'ResponseMetadata': {'HTTPStatusCode': 200, 'RequestId': '3b3ca2a8-5f14-5ac1-8b1f-ef3fea5dc376'}}

we validated the differences by querying via the aws cli v1.1.0:
AWS_DEFAULT_REGION=us-east-1 aws sqs receive-message --queue-url https://sqs.us-east-1.amazonaws.com/01234567890/AbcQueue-1ABCDEFQ --wait-time-seconds 2 --max-number-of-messages 1 --output json
{
"Messages": []
}

for comparison here is part of the debug response from the latest aws cli (v1.7.18):
AWS_DEFAULT_REGION=us-east-1 aws sqs receive-message --queue-url https://sqs.us-east-1.amazonaws.com/01234567890/AbcQueue-1ABCDEFQ --wait-time-seconds 2 --max-number-of-messages 1 --output json --debug
...
2015-04-03 22:52:55,722 - MainThread - botocore.parsers - DEBUG - Response body:

99c90e95-aa76-5c97-9983-430cb6736cf6

...

our propsed change is just to remove the additional check, the code should proceed normally and return an empty result.

@edsplunk
Copy link

edsplunk commented Aug 7, 2015

+1

@hyandell
Copy link
Contributor

hyandell commented Feb 1, 2018

This project has been archived. Please use CloudFormation’s native support for Custom Resources as documented at https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-custom-resources.html

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants