Generic Top

I just announced the new Learn Spring course, focused on the fundamentals of Spring 5 and Spring Boot 2:


In the final article, we move on to AWS Messaging Support.

1. AWS Messaging Support

1.1. SQS (Simple Queue Service)

We can send messages to an SQS queue using the QueueMessagingTemplate.

To create this bean, we can use an AmazonSQSAsync client which is available by default in the application context when using Spring Boot starters:

public QueueMessagingTemplate queueMessagingTemplate(
  AmazonSQSAsync amazonSQSAsync) {
    return new QueueMessagingTemplate(amazonSQSAsync);

Then, we can send the messages using the convertAndSend() method:

QueueMessagingTemplate messagingTemplate;
public void send(String topicName, Object message) {
    messagingTemplate.convertAndSend(topicName, message);

Since Amazon SQS only accepts String payloads, Java objects are automatically serialized to JSON.

We can also configure listeners using @SqsListener:

public void receiveMessage(String message, 
  @Header("SenderId") String senderId) {
    // ...

This method will receive messages from spring-cloud-test-queue and then process them. We can also retrieve message headers using the @Header annotation on method parameters.

If the first parameter is a custom Java object instead of String, Spring will convert the message to that type using JSON conversion.

1.2. SNS (Simple Notification Service)

Similar to SQS, we can use NotificationMessagingTemplate to publish messages to a topic.

To create it, we need an AmazonSNS client:

public NotificationMessagingTemplate notificationMessagingTemplate(
  AmazonSNS amazonSNS) {
    return new NotificationMessagingTemplate(amazonSNS);

Then, we can send notifications to the topic:

NotificationMessagingTemplate messagingTemplate;

public void send(String Object message, String subject) {
      .sendNotification("spring-cloud-test-topic", message, subject);

Out of the multiple SNS endpoints supported by AWS – SQS, HTTP(S), email and SMS, the project only supports HTTP(S).

We can configure the endpoints in an MVC controller:

public class SNSEndpointController {

    public void confirmUnsubscribeMessage(
      NotificationStatus notificationStatus) {
    public void receiveNotification(@NotificationMessage String message, 
      @NotificationSubject String subject) {
        // handle message

    public void confirmSubscriptionMessage(
      NotificationStatus notificationStatus) {

We need to add the topic name to the @RequestMapping annotation on the controller level. This controller enables an HTTP(s) endpoint – /topic-subscriber which be used by an SNS topic to create a subscription.

For example, we can subscribe to a topic by calling the URL:


The header in the request determines which of the three methods is invoked.

The method with @NotificationSubscriptionMapping annotation is invoked when the header [x-amz-sns-message-type=SubscriptionConfirmation] is present and confirms a new subscription to a topic.

Once subscribed, the topic will send notifications to the endpoint with the header [x-amz-sns-message-type=Notification]. This will invoke the method annotated with @NotificationMessageMapping.

Finally, when the endpoint unsubscribes from the topic, a confirmation request is received with the header [x-amz-sns-message-type=UnsubscribeConfirmation].

This calls the method annotated with @NotificationUnsubscribeConfirmationMapping which confirms unsubscribe action.

Please note that the value in @RequestMapping has nothing to do with the topic name to which it's subscribed.

2. Conclusion

In this final article, we explored Spring Cloud's support for AWS Messaging – which concludes this quick series about Spring Cloud and AWS.

As usual, the examples are available over on GitHub.

« Previous
Spring Cloud AWS – RDS
Generic bottom

I just announced the new Learn Spring course, focused on the fundamentals of Spring 5 and Spring Boot 2:

Newest Most Voted
Inline Feedbacks
View all comments
Rauf Agayev
Rauf Agayev
2 years ago

1. How is it possible to use Amazon SNS with Amazon SQS when you don’t want to implement a controller and receive messages with Amazon SQS?
2. @RequestMapping(“/topic-subscriber”) here “topic-subscriber” is the name of topic we create for SNS, right?
3. If you don’t want to implement REST interface what would be the possible way to implement a SNS receiver?


Loredana Crusoveanu
2 years ago
Reply to  Rauf Agayev

Hey Rauf,

The “topic-subscriber” mapping is the name of the topic – yes. For the other questions, this article presents the support that Spring Cloud provides for SNS and SQS. If you don’t want to work with these, I suggest taking a look at the Amazon AWS APIs.

Comments are closed on this article!