What is Security Hub & AWS Identity?

SQS, shorthand for Simple Queue Service is a service that is provided by Amazon. It offers security, durability, and a highlyavailable hosted queue, which can be used to integrate and disintegrate software systems and their components (software which is distributed in nature). It offers common operations like dead-letter queues, and cost-allocation tags.

Dead-letter queues refers to queues which can be used to debug applications or messaging system since they give the user the ability to separate messages that cause problems and determine the cause behind this. This dead-letter queues can be used by other source queues to target messages which can’t be processed/consumed properly.

Cost-allocation tags can be used to organize and identify the queue’s purpose, its owner and environment. This comes in handy when there are many queues which need to be handled.

In addition to the above-mentioned services, SQS offers generic web services API which can be accessed by many programming languages (those languages which are supported by AWS SDK).

It comes with support for standard as well as FIFO queues.

Features of Amazon SQS

• The user has control over who sends messages and these messages are received via an SQS queue.
• SSE (Server-side encryption) allows users to transmit sensitive and highly-confidential data by providing protection to the contents of the message present in the queues with the help of keys which are managed by AWS Key Management Service (KMS).
• SQS ensures that the messages sent over the queue are safe and are not lost, hence stores them on multiple servers. Standard queues support at-least-once message delivery whereas FIFO queues support exactly-once message processing.
• SQS uses a redundant infrastructure model, which ensures the provision of highly-concurrent access to the messages, as well as high-availability to produce and consume these messages.
• Every buffered request in the SQS is handled and processed independently, which means every request is scaled transparently so that it can handle any increase in load without explicitly requiring instructions to handle the same.
• It provides high-reliability, wherein SQS locks the user messages when it is being processed. This way multiple producers gain the ability to send messages to multiple receivers, as well as receive messages from multiple recipients at the same time.
• SQS can be used to customize queues- all queues don’t have to be the same, a default delay can be set on the queue. Larger messages (256 KB and above) can be stored in Amazon S3 or DynamoDB, and SQS can hold a pointer that points to the data present in S3 or DynamoDB.
• A larger message can also be split into chunks of smaller messages and can be stored without the need to store it in S3 or DynamoDB.
• Amazon SQS holding a pointer to the Amazon S3 object, or you can split a large message into smaller messages.

Conclusion 

We understood how SQS can be used to efficiently manage messages that flow through queues.