AWS SQS Resource

SQS (Simple Queue Service) is a fully managed message queuing service provided by Amazon Web Services (AWS). It allows developers to asynchronously send, store, and receive messages between distributed application components. SQS is highly scalable and fault tolerant, ensuring that messages are processed reliably and in an orderly manner. Producers send messages to queues and consumers retrieve them for processing. SQS offers two types of queues: Standard Queue and FIFO Queue, which differ in their message delivery and ordering capabilities. The SQS service is flexible and can be easily integrated with other AWS services such as EC2, Lambda, and SNS. It is particularly used in distributed scenarios, microservices, batch processing, email notifications, and other use cases where asynchronous and reliable communication between components is required. With the fully managed nature of the service, developers can focus on business logic without worrying about the underlying message queue infrastructure.

How to monitor SQS on One Platform

1 – In the side menu, click on Services Hub


2 – In the Queue category, click on the  SQS(AWS) card


3 – You will be directed to the SQS configuration form, fill in the fields


4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings


5 – Click on CREATE MONITORING 

SQS (Simple Queue Service) is a fully managed message queuing service provided by Amazon Web Services (AWS). It allows developers to asynchronously send, store, and receive messages between distributed application components. SQS is highly scalable and fault tolerant, ensuring that messages are processed reliably and in an orderly manner. Producers send messages to queues and consumers retrieve them for processing. SQS offers two types of queues: Standard Queue and FIFO Queue, which differ in their message delivery and ordering capabilities. The SQS service is flexible and can be easily integrated with other AWS services such as EC2, Lambda, and SNS. It is particularly used in distributed scenarios, microservices, batch processing, email notifications, and other use cases where asynchronous and reliable communication between components is required. With the fully managed nature of the service, developers can focus on business logic without worrying about the underlying message queue infrastructure.

How to monitor SQS on One Platform

1 – In the side menu, click on Services Hub


2 – In the Queue category, click on the  SQS(AWS) card


3 – You will be directed to the SQS configuration form, fill in the fields


4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

  • Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
  • Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
  • Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
  • Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
  • Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
  • Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button  for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings


5 – Click on CREATE MONITORING