Book Image

AWS Certified Developer - Associate Guide

By : Vipul Tankariya, Bhavin Parmar
Book Image

AWS Certified Developer - Associate Guide

By: Vipul Tankariya, Bhavin Parmar

Overview of this book

AWS Certified Developer - Associate Guide starts with a quick introduction to AWS and the prerequisites to get you started. Then, this book gives you a fair understanding of core AWS services and basic architecture. Next, this book will describe about getting familiar with Identity and Access Management (IAM) along with Virtual private cloud (VPC). Moving ahead you will learn about Elastic Compute cloud (EC2) and handling application traffic with Elastic Load Balancing (ELB). Going ahead you we will talk about Monitoring with CloudWatch, Simple storage service (S3) and Glacier and CloudFront along with other AWS storage options. Next we will take you through AWS DynamoDB – A NoSQL Database Service, Amazon Simple Queue Service (SQS) and CloudFormation Overview. Finally, this book covers understanding Elastic Beanstalk and overview of AWS lambda. At the end of this book, we will cover enough topics, tips and tricks along with mock tests for you to be able to pass the AWS Certified Developer - Associate exam and develop as well as manage your applications on the AWS platform.
Table of Contents (29 chapters)
Title Page
Credits
About the Author
Acknowledgments
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
Index

Chapter 13. Simple Notification Service

AWS Simple Notification Service (SNS) works based on push technology. It is also called a server push. In this mechanism, the message or transaction is initiated by the publisher or a central server and the AWS SNS delivers it to the subscribers. It is the opposite of the pull mechanism. The pull mechanism is also called a client pull, where the client raises a request to fetch or pull data from the server. As a side note, unlike SNS, AWS SQS works on a pull mechanism.

In enterprise architecture, we often need to send notifications to the subscribers. Some of the following real-time notification use cases can help us to understand how and where they are used:

  • When an EC2 instance is under- or over-utilized for a specific time frame, it should send a notification to the system administrators and stack holders. For example, at any given time, when the average CPU usage is above 70% or below 30% for a specific time frame, it sends a notification to the...