My Learning Experience with AWS SNS & SQS Recently, I spent time learning about Amazon SNS (Simple Notification Service) and Amazon SQS (Simple Queue Service), and I want to share my key takeaways A) Amazon SQS (Queue-based Messaging) When I first tried SQS, it felt like a simple yet powerful way to decouple applications. A producer sends a message → SQS stores it safely → one consumer picks it up. What I liked: Messages don’t get lost, and consumers can process them at their own pace. Use case I visualized: Order → Billing → Delivery, each step independent but connected through the queue. B) Amazon SNS (Publish/Subscribe Messaging) Then I explored SNS, and it clicked instantly — it’s like making an announcement . You publish one message → SNS fans it out to multiple subscribers (Email, Lambda, SQS, etc). What I liked: The flexibility to notify many systems at once. Use case I practiced: A new user signup → Notify Email service + Analytics + Logging simultaneously. SQS = Great for point-to-point reliable processing. SNS = Great for broadcasting events to multiple services. The most powerful pattern I learned: SNS + SQS together → reliable, scalable event-driven architecture. -> Learning these services gave me a clearer understanding of how event-driven systems are built in AWS. -> If you’re starting with AWS, I highly recommend practising both — you’ll quickly see how they solve different real-world problems. #AWS #CloudComputing #LearningJourney #SNS #SQS #EventDriven
Learning AWS SNS & SQS: Key Takeaways
More Relevant Posts
-
🚀 Amazon Web Services (AWS) #Day14 – Amazon SNS & Amazon SQS 🚀 Today, I explored two important messaging services in AWS: Amazon Simple Notification Service (SNS) and Amazon Simple Queue Service (SQS). Both play a key role in building event-driven and decoupled architectures. 🔹 Amazon SNS (Simple Notification Service) A pub/sub (publish-subscribe) messaging service. Publisher sends a message → SNS Topic → delivers to multiple subscribers. Supports delivery to: SQS queues, Lambda functions, Email, SMS, HTTP endpoints, etc. Use Cases: Alerts & notifications, event broadcasting, fan-out architecture. 🔹 Amazon SQS (Simple Queue Service) A fully managed message queue for decoupling applications. Producer sends messages → stored in a queue → Consumer pulls them. Two types: Standard Queue → unlimited throughput, at-least-once delivery. FIFO Queue → exactly-once processing, preserves order. Use Cases: Order processing, decoupling microservices, buffering requests, async jobs. ⚡ SNS + SQS Together SNS can push messages to SQS, enabling fan-out with reliable delivery. Great for scalable event-driven systems.
To view or add a comment, sign in
-
-
Day 46 of #90DaysOfDevOps Challenge : Setting up CloudWatch Alarms & SNS in AWS Ever wondered what happens if an AWS service silently keeps charging you until your wallet feels the burn? That’s why today’s focus is on proactive monitoring. A while ago, when I was just starting out on AWS, I once created a service and completely forgot to delete it after practicing. By the next day, I noticed I had been charged a few dollars. I panicked and had to call my colleague in fear about the charges. From that experience, I learned the importance of billing alerts — and since then, I never forget to set up notifications! What I learned today: • Amazon CloudWatch helps monitor AWS resources and applications in real time. • Amazon SNS (Simple Notification Service) allows us to send automated notifications via email, SMS, or other endpoints. How this is done: Enable billing alerts - From the Billing dashboard. Create an SNS topic Set up a CloudWatch alarm - Choose Billing - EstimatedCharges, set threshold to $2, and link it to your SNS topic. Test the SNS notification Clean up- Delete the alarm and SNS topic when done. This simple workflow ensures you’ll never be surprised by unexpected AWS charges. #AWS #CloudWatch #SNS #DevOps #Monitoring
To view or add a comment, sign in
-
Amazon OpenSearch Ingestion now supports cross-account ingestion - Amazon OpenSearch Ingestion now supports cross-account ingestion for push-based sources such as HTTP and OpenTelemetry (OTel). With this launch, customers can easily share OpenSearch Ingestion pipelines across AWS accounts without relying on additional configurations like VPC peering or AWS Transit… https://lnkd.in/erC7H4kE
To view or add a comment, sign in
-
🚀 Scaling PyTorch models beyond local dev? TorchServe is great for quick deployments, but production demands more: ✅ Kubernetes orchestration ✅ Autoscaling & resilience ✅ Proper observability ✅ Secure access & controlled rollouts I found this AWS blog on running TorchServe on Amazon EKS really useful as a starting point. It’s a hands-on guide to deploying TorchServe in Kubernetes, setting up inference endpoints, and integrating with AWS services. It won’t solve everything (versioning, A/B testing, monitoring at scale still need extra layers), but it’s a solid foundation to understand how TorchServe + Kubernetes work together. https://lnkd.in/gxSNBgkn
To view or add a comment, sign in
-
Day 52/100 – Messaging & Queuing in Amazon Web Services (AWS) ☕📩 Today I dug into how AWS handles communication between services and prevents apps from breaking when one part slows down. Here’s the breakdown: 1. Tightly Coupled : in this services depend directly on each other (if one fails, others fail too). 2. Loosely coupled : We do have a mediator mostly in between which manages interaction or use a queue/buffer between them so each works independently. 3. Amazon SQS (Simple Queue Service) : If system is too busy getting more requests ,messages (payloads) wait in a queue until the service is ready. It ensures reliability, no messages lost, and scales automatically. 4. Amazon SNS (Simple Notification Service) : It publishes or notifiess the same message to ALL systems instantly. Perfect for fan-out notifications (email, SMS, Lambda, analytics). 5. Amazon EventBridge : This is where SNS gets smarter , Routes or messages or events are forwareded based on rules and content. Not the usual dumb message as with SNS. 6. Microservices Architecture : Instead of one big monolith, apps are split into smaller independent services. ----Messaging + Queuing (SQS, SNS, EventBridge) help these microservices talk to each other reliably, keeping the system resilient and scalable. #AWS #Cloud #CloudComputing #AWSCloud #100DaysOfCode #100DaysOfCloud #BuildInPublic #LearningInPublic #CloudSecurity #DevOps #CloudEngineer #SoftwareEngineering #Serverless #Developers #CloudNative #InfrastructureAsCode #CloudJourney #TechJourney #TechCommunity #DataEngineer #SRE #SystemDesign #FullStack #Backend #Frontend #AI #ML #BigData #Programming #Coding #Engineer #DeveloperJourney #CloudDev #CloudDevelopment #StudyInPublic #CloudServices #Innovation #Scalability #CostEfficiency #CloudLife #LearnToCode #LearnInPublic #SecurityInCloud #AWSLearning #TechLife #EventDriven #Microservices #EventBridge #SNS #SQS #MessageQueue #AsyncProcessing
To view or add a comment, sign in
-
-
𝗗𝗮𝘆 𝟰𝟰/𝟵𝟬 – 𝗠𝘆 𝗗𝗲𝗩𝗢𝗣𝗦 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝗤𝗦 – 𝗧𝗵𝗲 𝗠𝗲𝘀𝘀𝗮𝗴𝗲 𝗕𝗿𝗶𝗱𝗴𝗲 𝗼𝗳 𝗖𝗹𝗼𝘂𝗱 ⚡📩 Imagine you’re building a system where multiple applications need to talk to each other. Without a buffer, if one app slows down, the entire system may crash like dominoes. That’s where Amazon SQS (Simple Queue Service) becomes the hero. 🎯 Why SQS Matters: It acts as a queue between services, ensuring no message is lost. Decouples microservices so each works independently. Handles millions of messages per second reliably. ⚙ How It Works: Applications send messages to an SQS Queue. Messages stay safe until another service retrieves them. Supports Standard Queues (high throughput) & FIFO Queues (exact order, once-only processing). 🚀 Key Benefits: -Ensures high availability & fault tolerance -Scales automatically – no infrastructure to manage -Keeps systems loosely coupled but highly reliable -Reduces complexity in distributed applications -Pay only for what you use (serverless advantage!) Takeaway: Amazon SQS is not “just a queue” – it’s the backbone of reliable, asynchronous communication in the cloud. It makes complex architectures simpler, scalable, and resilient. Acknowledgment: A huge thank you to ravindra bagale Sir for explaining the importance of proactive monitoring. Special shoutout to my friends Shivam Garud & Bhushan Tayade for helping me test and understand these concepts in real-time. Reflection: In DevOps & Cloud, resilience is not about avoiding failure—it’s about designing systems that continue gracefully when failure happens. And SQS is one of those silent guardians that keep the flow uninterrupted. #AWS #AmazonSQS #CloudComputing #Serverless #DevOps #MessageQueue #CloudArchitecture #TechJourney #LearningByDoing #KnowledgeSharing
To view or add a comment, sign in
-
-
You don’t need Kubernetes to ship v1. Use managed services: API Gateway + Lambda + DynamoDB scales from 1 to 100k requests with near-zero ops. Learn by building it end-to-end. https://lnkd.in/eQxQxQ5d #Serverless #DynamoDB #APIGateway #Lambda #BuildInPublic
To view or add a comment, sign in
-
🚀 Day 19 of learning and exploring AWS with Devops ----Getting Started with AWS: Dashboard Tour ---- If you’re stepping into the world of Amazon Web Services (AWS), the first thing you’ll interact with is the AWS Management Console Dashboard – your central hub to explore, manage, and deploy cloud resources. 🔎 What you’ll see in the AWS Dashboard: • Search Bar – Quickly find any AWS service without scrolling. • Pinned Services – Access your most-used services right from the top. • Recently Visited Services – Saves you time by showing what you accessed last. • Service Categories – Compute, Storage, Networking, Databases, Security, AI/ML, and more – neatly grouped. • Resource Groups & Tags – Organize resources logically across projects. • Account Info & Regions – Easily switch between regions (global infrastructure at your fingertips ). • Support & Documentation – Direct access to help, billing, and training resources. # Pro Tip: If you’re new to AWS, start by pinning commonly used services like EC2, S3, IAM, and CloudWatch to your dashboard for quick access. The AWS Dashboard is designed to make cloud navigation intuitive and efficient – whether you’re a beginner experimenting with services or a pro managing enterprise workloads. Q. Have you explored the AWS dashboard yet? Which service do you use most often? #AWS #CloudComputing #AWSDashboard #CloudJourney #AmazonWebServices #LearningCloud
To view or add a comment, sign in
-
Serverless and Containers 177-[JAWS]-Lab - [Challenge] AWS Lambda Exercise In this challenge lab, I created an AWS Lambda function to automatically count the number of words in a text file. The workflow integrated Amazon S3 and Amazon SNS to build a simple yet powerful serverless solution. I learned how to: Create a Lambda function to count the number of words in a text file Configure an S3 bucket to trigger the Lambda function whenever a text file is uploaded Use Amazon SNS to send the word count result via email This challenge helped me strengthen my practical understanding of event-driven architectures on AWS, and how different services can seamlessly integrate to automate tasks. I really enjoyed this hands-on experience and look forward to applying these skills to more advanced serverless projects. I’m always open to learning and improving, so if you notice anything I could do better, your feedback would mean a lot to me. #AWS #AmazonWebServices #Lambda #Serverless #S3 #SNS #CloudComputing #HandsOnLab #LearningByDoing #LearningJourney
To view or add a comment, sign in
-
𝗘𝗖𝗦 𝗧𝗮𝘀𝗸𝘀 𝗦𝘁𝘂𝗰𝗸? 𝗧𝗵𝗲 𝗖𝗮𝗽𝗮𝗰𝗶𝘁𝘆 𝗣𝗿𝗼𝘃𝗶𝗱𝗲𝗿 𝗧𝗿𝗮𝗽 𝗘𝘅𝗽𝗹𝗮𝗶𝗻𝗲𝗱 My ECS task fail in Airflow yesterday: I hit an error while triggering an ECS task from Airflow: 𝘐𝘯𝘷𝘢𝘭𝘪𝘥𝘗𝘢𝘳𝘢𝘮𝘦𝘵𝘦𝘳𝘌𝘹𝘤𝘦𝘱𝘵𝘪𝘰𝘯: 𝘛𝘩𝘦 𝘴𝘱𝘦𝘤𝘪𝘧𝘪𝘦𝘥 𝘤𝘢𝘱𝘢𝘤𝘪𝘵𝘺 𝘱𝘳𝘰𝘷𝘪𝘥𝘦𝘳 𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺 𝘤𝘢𝘯𝘯𝘰𝘵 𝘤𝘰𝘯𝘵𝘢𝘪𝘯 𝘢 𝘤𝘢𝘱𝘢𝘤𝘪𝘵𝘺 𝘱𝘳𝘰𝘷𝘪𝘥𝘦𝘳 𝘵𝘩𝘢𝘵 𝘪𝘴 𝘯𝘰𝘵 𝘢𝘴𝘴𝘰𝘤𝘪𝘢𝘵𝘦𝘥 𝘸𝘪𝘵𝘩 𝘵𝘩𝘦 𝘤𝘭𝘶𝘴𝘵𝘦𝘳. At first, I thought Airflow was the problem. But the real issue was with ECS capacity providers. 𝗪𝗵𝗮𝘁 𝘄𝗮𝘀 𝗵𝗮𝗽𝗽𝗲𝗻𝗶𝗻𝗴 Imagine your ECS cluster as a bus station. - Every station has certain buses that operate there in ECS terms, these are the capacity providers (like FARGATE or FARGATE_SPOT). - If you ask for a bus that doesn’t run from that station, the station manager will say, “Sorry, that bus isn’t available here.” That’s exactly what ECS was telling me. The task requested a provider that wasn’t connected to the cluster. 𝗛𝗼𝘄 𝗜 𝗰𝗵𝗲𝗰𝗸𝗲𝗱 𝗶𝘁 I used this command to confirm which capacity providers my cluster supported: 𝙖𝙬𝙨 𝙚𝙘𝙨 𝙙𝙚𝙨𝙘𝙧𝙞𝙗𝙚-𝙘𝙡𝙪𝙨𝙩𝙚𝙧𝙨 \ --𝙘𝙡𝙪𝙨𝙩𝙚𝙧𝙨 𝙞𝙣𝙛𝙚𝙧𝙚𝙣𝙘𝙞𝙣𝙜-𝙘𝙡𝙪𝙨𝙩𝙚𝙧 \ --𝙦𝙪𝙚𝙧𝙮 "𝙘𝙡𝙪𝙨𝙩𝙚𝙧𝙨[0].𝙘𝙖𝙥𝙖𝙘𝙞𝙩𝙮𝙋𝙧𝙤𝙫𝙞𝙙𝙚𝙧𝙨" 𝗛𝗼𝘄 𝗜 𝗳𝗶𝘅𝗲𝗱 𝗶𝘁 I associated the correct capacity providers with the cluster: 𝙖𝙬𝙨 𝙚𝙘𝙨 𝙥𝙪𝙩-𝙘𝙡𝙪𝙨𝙩𝙚𝙧-𝙘𝙖𝙥𝙖𝙘𝙞𝙩𝙮-𝙥𝙧𝙤𝙫𝙞𝙙𝙚𝙧𝙨 \ --𝙘𝙡𝙪𝙨𝙩𝙚𝙧 𝙞𝙣𝙛𝙚𝙧𝙚𝙣𝙘𝙞𝙣𝙜-𝙘𝙡𝙪𝙨𝙩𝙚𝙧 \ --𝙘𝙖𝙥𝙖𝙘𝙞𝙩𝙮-𝙥𝙧𝙤𝙫𝙞𝙙𝙚𝙧𝙨 𝙁𝘼𝙍𝙂𝘼𝙏𝙀 𝙁𝘼𝙍𝙂𝘼𝙏𝙀_𝙎𝙋𝙊𝙏 \ --𝙙𝙚𝙛𝙖𝙪𝙡𝙩-𝙘𝙖𝙥𝙖𝙘𝙞𝙩𝙮-𝙥𝙧𝙤𝙫𝙞𝙙𝙚𝙧-𝙨𝙩𝙧𝙖𝙩𝙚𝙜𝙮 𝙘𝙖𝙥𝙖𝙘𝙞𝙩𝙮𝙋𝙧𝙤𝙫𝙞𝙙𝙚𝙧=𝙁𝘼𝙍𝙂𝘼𝙏𝙀,𝙬𝙚𝙞𝙜𝙝𝙩=1 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 𝗳𝗼𝗿 𝘀𝗰𝗮𝗹𝗶𝗻𝗴 Capacity providers are how ECS decides which resources to use when scaling. For example, you can say, “Run most tasks on FARGATE, but when demand spikes, also use FARGATE_SPOT.” ECS will then scale up and down automatically, without you needing to manage it manually. Takeaway: This wasn’t an Airflow issue at all. The ECS cluster simply didn’t have the right provider attached. Once I linked the correct capacity providers, the tasks started running smoothly. Happy & Fun Learning Chetan Mohod #AWSCommunity Amazon Web Services (AWS) #ECS #Airflow #Autoscaling
To view or add a comment, sign in
-
Fellow at NxtWave’s CCBP 4.0 Academy | Knows Python || SQL || MERN || Full Stack Developer || Looking for internships
2wGreat to see your work 😁