Class: Aws::SQS::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::SQS::Client
- Includes:
- ClientStubs
- Defined in:
- lib/aws-sdk-sqs/client.rb
Overview
An API client for SQS. To construct a client, you need to configure a ‘:region` and `:credentials`.
client = Aws::SQS::Client.new(
region: region_name,
credentials: credentials,
# ...
)
For details on configuring region and credentials see the [developer guide](/sdk-for-ruby/v3/developer-guide/setup-config.html).
See #initialize for a full list of supported configuration options.
Class Attribute Summary collapse
- .identifier ⇒ Object readonly private
API Operations collapse
-
#add_permission(params = {}) ⇒ Struct
Adds a permission to a queue for a specific [principal].
-
#cancel_message_move_task(params = {}) ⇒ Types::CancelMessageMoveTaskResult
Cancels a specified message movement task.
-
#change_message_visibility(params = {}) ⇒ Struct
Changes the visibility timeout of a specified message in a queue to a new value.
-
#change_message_visibility_batch(params = {}) ⇒ Types::ChangeMessageVisibilityBatchResult
Changes the visibility timeout of multiple messages.
-
#create_queue(params = {}) ⇒ Types::CreateQueueResult
Creates a new standard or FIFO queue.
-
#delete_message(params = {}) ⇒ Struct
Deletes the specified message from the specified queue.
-
#delete_message_batch(params = {}) ⇒ Types::DeleteMessageBatchResult
Deletes up to ten messages from the specified queue.
-
#delete_queue(params = {}) ⇒ Struct
Deletes the queue specified by the ‘QueueUrl`, regardless of the queue’s contents.
-
#get_queue_attributes(params = {}) ⇒ Types::GetQueueAttributesResult
Gets attributes for the specified queue.
-
#get_queue_url(params = {}) ⇒ Types::GetQueueUrlResult
Returns the URL of an existing Amazon SQS queue.
-
#list_dead_letter_source_queues(params = {}) ⇒ Types::ListDeadLetterSourceQueuesResult
Returns a list of your queues that have the ‘RedrivePolicy` queue attribute configured with a dead-letter queue.
-
#list_message_move_tasks(params = {}) ⇒ Types::ListMessageMoveTasksResult
Gets the most recent message movement tasks (up to 10) under a specific source queue.
-
#list_queue_tags(params = {}) ⇒ Types::ListQueueTagsResult
List all cost allocation tags added to the specified Amazon SQS queue.
-
#list_queues(params = {}) ⇒ Types::ListQueuesResult
Returns a list of your queues in the current region.
-
#purge_queue(params = {}) ⇒ Struct
Deletes available messages in a queue (including in-flight messages) specified by the ‘QueueURL` parameter.
-
#receive_message(params = {}) ⇒ Types::ReceiveMessageResult
Retrieves one or more messages (up to 10), from the specified queue.
-
#remove_permission(params = {}) ⇒ Struct
Revokes any permissions in the queue policy that matches the specified ‘Label` parameter.
-
#send_message(params = {}) ⇒ Types::SendMessageResult
Delivers a message to the specified queue.
-
#send_message_batch(params = {}) ⇒ Types::SendMessageBatchResult
You can use ‘SendMessageBatch` to send up to 10 messages to the specified queue by assigning either identical or different values to each message (or by not assigning values at all).
-
#set_queue_attributes(params = {}) ⇒ Struct
Sets the value of one or more queue attributes, like a policy.
-
#start_message_move_task(params = {}) ⇒ Types::StartMessageMoveTaskResult
Starts an asynchronous task to move messages from a specified source queue to a specified destination queue.
-
#tag_queue(params = {}) ⇒ Struct
Add cost allocation tags to the specified Amazon SQS queue.
-
#untag_queue(params = {}) ⇒ Struct
Remove cost allocation tags from the specified Amazon SQS queue.
Class Method Summary collapse
- .errors_module ⇒ Object private
Instance Method Summary collapse
- #build_request(operation_name, params = {}) ⇒ Object private
-
#initialize(options) ⇒ Client
constructor
A new instance of Client.
- #waiter_names ⇒ Object deprecated private Deprecated.
Constructor Details
#initialize(options) ⇒ Client
Returns a new instance of Client.
461 462 463 |
# File 'lib/aws-sdk-sqs/client.rb', line 461 def initialize(*args) super end |
Class Attribute Details
.identifier ⇒ Object (readonly)
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2924 2925 2926 |
# File 'lib/aws-sdk-sqs/client.rb', line 2924 def identifier @identifier end |
Class Method Details
.errors_module ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2927 2928 2929 |
# File 'lib/aws-sdk-sqs/client.rb', line 2927 def errors_module Errors end |
Instance Method Details
#add_permission(params = {}) ⇒ Struct
Adds a permission to a queue for a specific [principal]. This allows sharing access to the queue.
When you create a queue, you have full control access rights for the queue. Only you, the owner of the queue, can grant or deny permissions to the queue. For more information about these permissions, see [Allow Developers to Write Messages to a Shared Queue] in the *Amazon SQS Developer Guide*.
<note markdown=“1”> * ‘AddPermission` generates a policy for you. You can use `
SetQueueAttributes ` to upload your policy. For more information,
see [Using Custom Policies with the Amazon SQS Access Policy
Language][3] in the *Amazon SQS Developer Guide*.
-
An Amazon SQS policy can have a maximum of seven actions per statement.
-
To remove the ability to change queue permissions, you must deny permission to the ‘AddPermission`, `RemovePermission`, and `SetQueueAttributes` actions in your IAM policy.
-
Amazon SQS ‘AddPermission` does not support adding a non-account principal.
</note>
<note markdown=“1”> Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
</note>
[1]: docs.aws.amazon.com/general/latest/gr/glos-chap.html#P [2]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-writing-an-sqs-policy.html#write-messages-to-shared-queue [3]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-creating-custom-policies.html [4]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name
561 562 563 564 |
# File 'lib/aws-sdk-sqs/client.rb', line 561 def (params = {}, = {}) req = build_request(:add_permission, params) req.send_request() end |
#build_request(operation_name, params = {}) ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 |
# File 'lib/aws-sdk-sqs/client.rb', line 2897 def build_request(operation_name, params = {}) handlers = @handlers.for(operation_name) tracer = config.telemetry_provider.tracer_provider.tracer( Aws::Telemetry.module_to_tracer_name('Aws::SQS') ) context = Seahorse::Client::RequestContext.new( operation_name: operation_name, operation: config.api.operation(operation_name), client: self, params: params, config: config, tracer: tracer ) context[:gem_name] = 'aws-sdk-sqs' context[:gem_version] = '1.86.0' Seahorse::Client::Request.new(handlers, context) end |
#cancel_message_move_task(params = {}) ⇒ Types::CancelMessageMoveTaskResult
Cancels a specified message movement task. A message movement can only be cancelled when the current status is RUNNING. Cancelling a message movement task does not revert the messages that have already been moved. It can only stop the messages that have not been moved yet.
<note markdown=“1”> * This action is currently limited to supporting message redrive from
[dead-letter queues (DLQs)][1] only. In this context, the source
queue is the dead-letter queue (DLQ), while the destination queue
can be the original source queue (from which the messages were
driven to the dead-letter-queue), or a custom destination queue.
-
Only one active message movement task is supported per queue at any given time.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html
607 608 609 610 |
# File 'lib/aws-sdk-sqs/client.rb', line 607 def (params = {}, = {}) req = build_request(:cancel_message_move_task, params) req.send_request() end |
#change_message_visibility(params = {}) ⇒ Struct
Changes the visibility timeout of a specified message in a queue to a new value. The default visibility timeout for a message is 30 seconds. The minimum is 0 seconds. The maximum is 12 hours. For more information, see [Visibility Timeout] in the *Amazon SQS Developer Guide*.
For example, if the default timeout for a queue is 60 seconds, 15 seconds have elapsed since you received the message, and you send a ChangeMessageVisibility call with ‘VisibilityTimeout` set to 10 seconds, the 10 seconds begin to count from the time that you make the `ChangeMessageVisibility` call. Thus, any attempt to change the visibility timeout or to delete that message 10 seconds after you initially change the visibility timeout (a total of 25 seconds) might result in an error.
An Amazon SQS message has three basic states:
-
Sent to a queue by a producer.
-
Received from the queue by a consumer.
-
Deleted from the queue.
A message is considered to be stored after it is sent to a queue by a producer, but not yet received from the queue by a consumer (that is, between states 1 and 2). There is no limit to the number of stored messages. A message is considered to be *in flight* after it is received from a queue by a consumer, but not yet deleted from the queue (that is, between states 2 and 3). There is a limit to the number of in flight messages.
Limits that apply to in flight messages are unrelated to the unlimited number of stored messages.
For most standard queues (depending on queue traffic and message backlog), there can be a maximum of approximately 120,000 in flight messages (received from a queue by a consumer, but not yet deleted from the queue). If you reach this limit, Amazon SQS returns the ‘OverLimit` error message. To avoid reaching the limit, you should delete messages from the queue after they’re processed. You can also increase the number of queues you use to process your messages. To request a limit increase, [file a support request].
For FIFO queues, there can be a maximum of 20,000 in flight messages (received from a queue by a consumer, but not yet deleted from the queue). If you reach this limit, Amazon SQS returns no error messages.
If you attempt to set the ‘VisibilityTimeout` to a value greater than the maximum time left, Amazon SQS returns an error. Amazon SQS doesn’t automatically recalculate and increase the timeout to the maximum remaining time.
Unlike with a queue, when you change the visibility timeout for a
specific message the timeout value is applied immediately but isn’t saved in memory for that message. If you don’t delete a message after it is received, the visibility timeout for the message reverts to the original timeout value (not to the value you set using the ‘ChangeMessageVisibility` action) the next time the message is received.
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html [2]: console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-sqs
706 707 708 709 |
# File 'lib/aws-sdk-sqs/client.rb', line 706 def (params = {}, = {}) req = build_request(:change_message_visibility, params) req.send_request() end |
#change_message_visibility_batch(params = {}) ⇒ Types::ChangeMessageVisibilityBatchResult
Changes the visibility timeout of multiple messages. This is a batch version of ‘ ChangeMessageVisibility.` The result of the action on each message is reported individually in the response. You can send up to 10 ` ChangeMessageVisibility ` requests with each `ChangeMessageVisibilityBatch` action.
Because the batch request can result in a combination of successful and unsuccessful actions, you should check for batch errors even when the call returns an HTTP status code of ‘200`.
763 764 765 766 |
# File 'lib/aws-sdk-sqs/client.rb', line 763 def (params = {}, = {}) req = build_request(:change_message_visibility_batch, params) req.send_request() end |
#create_queue(params = {}) ⇒ Types::CreateQueueResult
Creates a new standard or FIFO queue. You can pass one or more attributes in the request. Keep the following in mind:
-
If you don’t specify the ‘FifoQueue` attribute, Amazon SQS creates a standard queue.
<note markdown=“1”> You can’t change the queue type after you create it and you can’t convert an existing standard queue into a FIFO queue. You must either create a new FIFO queue for your application or delete your existing standard queue and recreate it as a FIFO queue. For more information, see [Moving From a Standard Queue to a FIFO Queue] in the *Amazon SQS Developer Guide*.
</note>
-
If you don’t provide a value for an attribute, the queue is created with the default value for the attribute.
-
If you delete a queue, you must wait at least 60 seconds before creating a queue with the same name.
To successfully create a new queue, you must provide a queue name that adheres to the [limits related to queues] and is unique within the scope of your queues.
<note markdown=“1”> After you create a queue, you must wait at least one second after the queue is created to be able to use the queue.
</note>
To get the queue URL, use the ‘ GetQueueUrl ` action. ` GetQueueUrl ` requires only the `QueueName` parameter. be aware of existing queue names:
-
If you provide the name of an existing queue along with the exact names and values of all the queue’s attributes, ‘CreateQueue` returns the queue URL for the existing queue.
-
If the queue name, attribute names, or attribute values don’t match an existing queue, ‘CreateQueue` returns an error.
<note markdown=“1”> Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html#FIFO-queues-moving [2]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/limits-queues.html [3]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name
1093 1094 1095 1096 |
# File 'lib/aws-sdk-sqs/client.rb', line 1093 def create_queue(params = {}, = {}) req = build_request(:create_queue, params) req.send_request() end |
#delete_message(params = {}) ⇒ Struct
Deletes the specified message from the specified queue. To select the message to delete, use the ‘ReceiptHandle` of the message (not the `MessageId` which you receive when you send the message). Amazon SQS can delete a message from a queue even if a visibility timeout setting causes the message to be locked by another consumer. Amazon SQS automatically deletes messages left in a queue longer than the retention period configured for the queue.
<note markdown=“1”> The ‘ReceiptHandle` is associated with a *specific instance* of receiving a message. If you receive a message more than once, the `ReceiptHandle` is different each time you receive a message. When you use the `DeleteMessage` action, you must provide the most recently received `ReceiptHandle` for the message (otherwise, the request succeeds, but the message will not be deleted).
For standard queues, it is possible to receive a message even after
you delete it. This might happen on rare occasions if one of the servers which stores a copy of the message is unavailable when you send the request to delete the message. The copy remains on the server and might be returned to you during a subsequent receive request. You should ensure that your application is idempotent, so that receiving a message more than once does not cause issues.
</note>
1144 1145 1146 1147 |
# File 'lib/aws-sdk-sqs/client.rb', line 1144 def (params = {}, = {}) req = build_request(:delete_message, params) req.send_request() end |
#delete_message_batch(params = {}) ⇒ Types::DeleteMessageBatchResult
Deletes up to ten messages from the specified queue. This is a batch version of ‘ DeleteMessage.` The result of the action on each message is reported individually in the response.
Because the batch request can result in a combination of successful and unsuccessful actions, you should check for batch errors even when the call returns an HTTP status code of ‘200`.
1196 1197 1198 1199 |
# File 'lib/aws-sdk-sqs/client.rb', line 1196 def (params = {}, = {}) req = build_request(:delete_message_batch, params) req.send_request() end |
#delete_queue(params = {}) ⇒ Struct
Deletes the queue specified by the ‘QueueUrl`, regardless of the queue’s contents.
Be careful with the ‘DeleteQueue` action: When you delete a queue, any messages in the queue are no longer available.
When you delete a queue, the deletion process takes up to 60 seconds. Requests you send involving that queue during the 60 seconds might succeed. For example, a ‘ SendMessage ` request might succeed, but after 60 seconds the queue and the message you sent no longer exist.
When you delete a queue, you must wait at least 60 seconds before creating a queue with the same name.
<note markdown=“1”> Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
The delete operation uses the HTTP `GET` verb.
</note>
1244 1245 1246 1247 |
# File 'lib/aws-sdk-sqs/client.rb', line 1244 def delete_queue(params = {}, = {}) req = build_request(:delete_queue, params) req.send_request() end |
#get_queue_attributes(params = {}) ⇒ Types::GetQueueAttributesResult
Gets attributes for the specified queue.
<note markdown=“1”> To determine whether a queue is [FIFO], you can check whether ‘QueueName` ends with the `.fifo` suffix.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html
1479 1480 1481 1482 |
# File 'lib/aws-sdk-sqs/client.rb', line 1479 def get_queue_attributes(params = {}, = {}) req = build_request(:get_queue_attributes, params) req.send_request() end |
#get_queue_url(params = {}) ⇒ Types::GetQueueUrlResult
Returns the URL of an existing Amazon SQS queue.
To access a queue that belongs to another AWS account, use the ‘QueueOwnerAWSAccountId` parameter to specify the account ID of the queue’s owner. The queue’s owner must grant you permission to access the queue. For more information about shared queue access, see ‘ AddPermission ` or see [Allow Developers to Write Messages to a Shared Queue] in the *Amazon SQS Developer Guide*.
1527 1528 1529 1530 |
# File 'lib/aws-sdk-sqs/client.rb', line 1527 def get_queue_url(params = {}, = {}) req = build_request(:get_queue_url, params) req.send_request() end |
#list_dead_letter_source_queues(params = {}) ⇒ Types::ListDeadLetterSourceQueuesResult
Returns a list of your queues that have the ‘RedrivePolicy` queue attribute configured with a dead-letter queue.
The ‘ListDeadLetterSourceQueues` methods supports pagination. Set parameter `MaxResults` in the request to specify the maximum number of results to be returned in the response. If you do not set `MaxResults`, the response includes a maximum of 1,000 results. If you set `MaxResults` and there are additional results to display, the response includes a value for `NextToken`. Use `NextToken` as a parameter in your next request to `ListDeadLetterSourceQueues` to receive the next page of results.
For more information about using dead-letter queues, see [Using Amazon SQS Dead-Letter Queues] in the *Amazon SQS Developer Guide*.
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
1589 1590 1591 1592 |
# File 'lib/aws-sdk-sqs/client.rb', line 1589 def list_dead_letter_source_queues(params = {}, = {}) req = build_request(:list_dead_letter_source_queues, params) req.send_request() end |
#list_message_move_tasks(params = {}) ⇒ Types::ListMessageMoveTasksResult
Gets the most recent message movement tasks (up to 10) under a specific source queue.
<note markdown=“1”> * This action is currently limited to supporting message redrive from
[dead-letter queues (DLQs)][1] only. In this context, the source
queue is the dead-letter queue (DLQ), while the destination queue
can be the original source queue (from which the messages were
driven to the dead-letter-queue), or a custom destination queue.
-
Only one active message movement task is supported per queue at any given time.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html
1648 1649 1650 1651 |
# File 'lib/aws-sdk-sqs/client.rb', line 1648 def (params = {}, = {}) req = build_request(:list_message_move_tasks, params) req.send_request() end |
#list_queue_tags(params = {}) ⇒ Types::ListQueueTagsResult
List all cost allocation tags added to the specified Amazon SQS queue. For an overview, see [Tagging Your Amazon SQS Queues] in the *Amazon SQS Developer Guide*.
<note markdown=“1”> Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html [2]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name
1690 1691 1692 1693 |
# File 'lib/aws-sdk-sqs/client.rb', line 1690 def (params = {}, = {}) req = build_request(:list_queue_tags, params) req.send_request() end |
#list_queues(params = {}) ⇒ Types::ListQueuesResult
Returns a list of your queues in the current region. The response includes a maximum of 1,000 results. If you specify a value for the optional ‘QueueNamePrefix` parameter, only queues with a name that begins with the specified value are returned.
The ‘listQueues` methods supports pagination. Set parameter `MaxResults` in the request to specify the maximum number of results to be returned in the response. If you do not set `MaxResults`, the response includes a maximum of 1,000 results. If you set `MaxResults` and there are additional results to display, the response includes a value for `NextToken`. Use `NextToken` as a parameter in your next request to `listQueues` to receive the next page of results.
<note markdown=“1”> Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
</note>
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
1757 1758 1759 1760 |
# File 'lib/aws-sdk-sqs/client.rb', line 1757 def list_queues(params = {}, = {}) req = build_request(:list_queues, params) req.send_request() end |
#purge_queue(params = {}) ⇒ Struct
Deletes available messages in a queue (including in-flight messages) specified by the ‘QueueURL` parameter.
When you use the ‘PurgeQueue` action, you can’t retrieve any messages deleted from a queue.
The message deletion process takes up to 60 seconds. We recommend
waiting for 60 seconds regardless of your queue’s size.
Messages sent to the queue before you call ‘PurgeQueue` might be received but are deleted within the next minute.
Messages sent to the queue after you call ‘PurgeQueue` might be deleted while the queue is being purged.
1795 1796 1797 1798 |
# File 'lib/aws-sdk-sqs/client.rb', line 1795 def purge_queue(params = {}, = {}) req = build_request(:purge_queue, params) req.send_request() end |
#receive_message(params = {}) ⇒ Types::ReceiveMessageResult
Retrieves one or more messages (up to 10), from the specified queue. Using the ‘WaitTimeSeconds` parameter enables long-poll support. For more information, see [Amazon SQS Long Polling] in the *Amazon SQS Developer Guide*.
Short poll is the default behavior where a weighted random set of machines is sampled on a ‘ReceiveMessage` call. Thus, only the messages on the sampled machines are returned. If the number of messages in the queue is small (fewer than 1,000), you most likely get fewer messages than you requested per `ReceiveMessage` call. If the number of messages in the queue is extremely small, you might not receive any messages in a particular `ReceiveMessage` response. If this happens, repeat the request.
For each message returned, the response includes the following:
-
The message body.
-
An MD5 digest of the message body. For information about MD5, see [RFC1321].
-
The ‘MessageId` you received when you sent the message to the queue.
-
The receipt handle.
-
The message attributes.
-
An MD5 digest of the message attributes.
The receipt handle is the identifier you must provide when deleting the message. For more information, see [Queue and Message Identifiers] in the *Amazon SQS Developer Guide*.
You can provide the ‘VisibilityTimeout` parameter in your request. The parameter is applied to the messages that Amazon SQS returns in the response. If you don’t include the parameter, the overall visibility timeout for the queue is used for the returned messages. For more information, see [Visibility Timeout] in the *Amazon SQS Developer Guide*.
A message that isn’t deleted or a message whose visibility isn’t extended before the visibility timeout expires counts as a failed receive. Depending on the configuration of the queue, the message might be sent to the dead-letter queue.
<note markdown=“1”> In the future, new attributes might be added. If you write code that calls this action, we recommend that you structure your code so that it can handle new attributes gracefully.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-long-polling.html [2]: www.ietf.org/rfc/rfc1321.txt [3]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-message-identifiers.html [4]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-visibility-timeout.html
2106 2107 2108 2109 |
# File 'lib/aws-sdk-sqs/client.rb', line 2106 def (params = {}, = {}) req = build_request(:receive_message, params) req.send_request() end |
#remove_permission(params = {}) ⇒ Struct
Revokes any permissions in the queue policy that matches the specified ‘Label` parameter.
<note markdown=“1”> * Only the owner of a queue can remove permissions from it.
-
Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
-
To remove the ability to change queue permissions, you must deny permission to the ‘AddPermission`, `RemovePermission`, and `SetQueueAttributes` actions in your IAM policy.
</note>
2152 2153 2154 2155 |
# File 'lib/aws-sdk-sqs/client.rb', line 2152 def (params = {}, = {}) req = build_request(:remove_permission, params) req.send_request() end |
#send_message(params = {}) ⇒ Types::SendMessageResult
Delivers a message to the specified queue.
A message can include only XML, JSON, and unformatted text. The following Unicode characters are allowed. For more information, see the [W3C specification for characters].
`#x9` \| `#xA` \| `#xD` \| `#x20` to `#xD7FF` \| `#xE000` to `#xFFFD`
| ‘#x10000` to `#x10FFFF`
Amazon SQS does not throw an exception or completely reject the
message if it contains invalid characters. Instead, it replaces those invalid characters with ‘U+FFFD` before storing the message in the queue, as long as the message body contains at least one valid character.
2377 2378 2379 2380 |
# File 'lib/aws-sdk-sqs/client.rb', line 2377 def (params = {}, = {}) req = build_request(:send_message, params) req.send_request() end |
#send_message_batch(params = {}) ⇒ Types::SendMessageBatchResult
You can use ‘SendMessageBatch` to send up to 10 messages to the specified queue by assigning either identical or different values to each message (or by not assigning values at all). This is a batch version of ` SendMessage.` For a FIFO queue, multiple messages within a single batch are enqueued in the order they are sent.
The result of sending each message is reported individually in the response. Because the batch request can result in a combination of successful and unsuccessful actions, you should check for batch errors even when the call returns an HTTP status code of ‘200`.
The maximum allowed individual message size and the maximum total payload size (the sum of the individual lengths of all of the batched messages) are both 256 KiB (262,144 bytes).
A message can include only XML, JSON, and unformatted text. The following Unicode characters are allowed. For more information, see the [W3C specification for characters].
`#x9` \| `#xA` \| `#xD` \| `#x20` to `#xD7FF` \| `#xE000` to `#xFFFD`
| ‘#x10000` to `#x10FFFF`
Amazon SQS does not throw an exception or completely reject the
message if it contains invalid characters. Instead, it replaces those invalid characters with ‘U+FFFD` before storing the message in the queue, as long as the message body contains at least one valid character.
If you don’t specify the ‘DelaySeconds` parameter for an entry, Amazon SQS uses the default value for the queue.
2482 2483 2484 2485 |
# File 'lib/aws-sdk-sqs/client.rb', line 2482 def (params = {}, = {}) req = build_request(:send_message_batch, params) req.send_request() end |
#set_queue_attributes(params = {}) ⇒ Struct
Sets the value of one or more queue attributes, like a policy. When you change a queue’s attributes, the change can take up to 60 seconds for most of the attributes to propagate throughout the Amazon SQS system. Changes made to the ‘MessageRetentionPeriod` attribute can take up to 15 minutes and will impact existing messages in the queue potentially causing them to be expired and deleted if the `MessageRetentionPeriod` is reduced below the age of existing messages.
<note markdown=“1”> * In the future, new attributes might be added. If you write code that
calls this action, we recommend that you structure your code so that
it can handle new attributes gracefully.
-
Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
-
To remove the ability to change queue permissions, you must deny permission to the ‘AddPermission`, `RemovePermission`, and `SetQueueAttributes` actions in your IAM policy.
</note>
2723 2724 2725 2726 |
# File 'lib/aws-sdk-sqs/client.rb', line 2723 def set_queue_attributes(params = {}, = {}) req = build_request(:set_queue_attributes, params) req.send_request() end |
#start_message_move_task(params = {}) ⇒ Types::StartMessageMoveTaskResult
Starts an asynchronous task to move messages from a specified source queue to a specified destination queue.
<note markdown=“1”> * This action is currently limited to supporting message redrive from
queues that are configured as [dead-letter queues (DLQs)][1] of
other Amazon SQS queues only. Non-SQS queue sources of dead-letter
queues, such as Lambda or Amazon SNS topics, are currently not
supported.
-
In dead-letter queues redrive context, the ‘StartMessageMoveTask` the source queue is the DLQ, while the destination queue can be the original source queue (from which the messages were driven to the dead-letter-queue), or a custom destination queue.
-
Only one active message movement task is supported per queue at any given time.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead-letter-queues.html
2792 2793 2794 2795 |
# File 'lib/aws-sdk-sqs/client.rb', line 2792 def (params = {}, = {}) req = build_request(:start_message_move_task, params) req.send_request() end |
#tag_queue(params = {}) ⇒ Struct
Add cost allocation tags to the specified Amazon SQS queue. For an overview, see [Tagging Your Amazon SQS Queues] in the *Amazon SQS Developer Guide*.
When you use queue tags, keep the following guidelines in mind:
-
Adding more than 50 tags to a queue isn’t recommended.
-
Tags don’t have any semantic meaning. Amazon SQS interprets tags as character strings.
-
Tags are case-sensitive.
-
A new tag with a key identical to that of an existing tag overwrites the existing tag.
For a full list of tag restrictions, see [Quotas related to queues] in the *Amazon SQS Developer Guide*.
<note markdown=“1”> Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html [2]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-limits.html#limits-queues [3]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name
2849 2850 2851 2852 |
# File 'lib/aws-sdk-sqs/client.rb', line 2849 def tag_queue(params = {}, = {}) req = build_request(:tag_queue, params) req.send_request() end |
#untag_queue(params = {}) ⇒ Struct
Remove cost allocation tags from the specified Amazon SQS queue. For an overview, see [Tagging Your Amazon SQS Queues] in the *Amazon SQS Developer Guide*.
<note markdown=“1”> Cross-account permissions don’t apply to this action. For more information, see [Grant cross-account permissions to a role and a username] in the *Amazon SQS Developer Guide*.
</note>
[1]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-queue-tags.html [2]: docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-customer-managed-policy-examples.html#grant-cross-account-permissions-to-role-and-user-name
2888 2889 2890 2891 |
# File 'lib/aws-sdk-sqs/client.rb', line 2888 def untag_queue(params = {}, = {}) req = build_request(:untag_queue, params) req.send_request() end |
#waiter_names ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
2917 2918 2919 |
# File 'lib/aws-sdk-sqs/client.rb', line 2917 def waiter_names [] end |