The developer endpoint also supports showing invisible and delayed messages via the query arguments ShowInvisible
and ShowDelayed
.
This will also include messages that currently have an active visibility timeout or were delayed and are not actually in the queue yet.
+Here’s an example:
[
+ {
+ "MessageId": "1c4187cc-f2c9-4f1c-9702-4a3bfaaa4817",
+ "MD5OfBody": "a06498de7fb4bd539c8895748f03175d",
+ "Body": "message-3",
+ "Attribute": [
+ {"Name": "SenderId", "Value": "000000000000"},
+ {"Name": "SentTimestamp", "Value": "1697494407799"},
+ {"Name": "ApproximateReceiveCount", "Value": "0"},
+ {"Name": "ApproximateFirstReceiveTimestamp", "Value": "0"},
+ {"Name": "IsVisible", "Value": "true"}, <--
+ {"Name": "IsDelayed", "Value": "false"}, <--
+ ],
+ "ReceiptHandle": "SQS/BACKDOOR/ACCESS",
+ },
+ ...
+]
The LocalStack Web Application provides a Resource Browser for managing SQS queues.
-You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the Resources section, and then clicking on SQS under the App Integration section.
The following code snippets and sample applications provide practical examples of how to use SQS in LocalStack for various use cases:
Last modified September 13, 2023:
fix queue names (#820) (df7c0b048)
+You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the The following code snippets and sample applications provide practical examples of how to use SQS in LocalStack for various use cases:
\ No newline at end of file