Sudharshan Mutalik’s Post

🚀 Excited to share my latest blog! Let's dive deep into the realm of Amazon S3 with our step-by-step guide on mastering AWS Console. From creating buckets to organizing folders, discover the keys to seamless data management in the cloud! 💼💾 #AWS #AmazonS3 #CloudStorage #DataManagement

I'm thrilled to announce that #MagicBus has now implemented AWS Lambda. AWS Lambda is a serverless computing service provided by Amazon Web Services (AWS). It allows you to run code without provisioning or managing servers. With Lambda, you can upload your code and AWS handles the infrastructure, scaling, and availability. Here's how it typically works: 1. Upload Code: You upload your function code to AWS Lambda, either directly or through tools like the AWS Management Console, AWS CLI (Command Line Interface). 2. Trigger: You define an event source, like an HTTP request, a file upload to an S3 bucket, or a message from an AWS service like SNS (Simple Notification Service). 3. Execution: AWS Lambda runs your function code in a containerized environment, isolating it from other functions. It manages all resources, including CPU, memory, and networking. 4.Scaling: When an event occurs, AWS Lambda automatically triggers your function. It then manages the infrastructure needed to run your function, scaling it up or down based on the incoming workload. Special Thanks to Jaswanth Nukala Sir 🙏 #AWS Lambda #Serverless and Containers #AWS #MAGICBUS

"Saving on AWS? If not, what are you waiting for?" At last year's reInvent, our CTO Rahul Subramaniam gave a session at reInvent with that title. Some crazy quotes from Rahul about AWS usage: > "The average utilization of EC2 instances is just about 6%." > "Over 90% of objects stored in S3 are accessed just once in their entire lifetime." > "Default networking configurations are at least 300% more expensive than optimized setups." > "Managing your own database instances can cost twice as much as using serverless options." > "Modernizing to the latest EC2 generation can significantly reduce costs." There are just a few of the surprising hard truths in AWS usage. The great thing? These are fixable problems! https://lnkd.in/gTju4Zm6

Free AWS Live Virtual & Interactive Training: Cost Optimization for Compute Workshop - Are you looking to cost optimize your workloads? Consider using AWS Graviton-based Amazon EC2 instances and Amazon EC2 Spot instances. Join us virtually at Cost Optimization for Compute Workshop on April 15th, 2024 from 3PM to 6PM CET. This is a free live virtual hands-on 3-hour workshop where AWS experts deliver and assist attendees with technically focused AWS Graviton and Spot training. Our experts will also provide insights into best practices and key factors to consider when migrating workloads to AWS Graviton and spot. Space is limited, so learn more and sign up today. https://lnkd.in/gJPDRgwU #aws #ec2 #graviton #cloud #compute #cloudcomputing #cloudmigration #developer #spot

As a launch partner for Amazon Web Services (AWS) new Resource Control Policies, Rapid7 Exposure Command further extends its capabilities, helping organizations set precise, scalable guardrails within their AWS environments. Learn more 👉 https://r-7.co/4eMSlP6 Interested in learning more about RCPs and our expanded AWS support? Be sure to swing by booth #697 at #AWSreInvent to see the Command Platform in action!

𝐒𝐞𝐫𝐯𝐞𝐫𝐥𝐞𝐬𝐬 𝐦𝐨𝐦𝐞𝐧𝐭𝐬 𝐰𝐢𝐭𝐡 𝐀𝐖𝐒 𝐋𝐚𝐦𝐛𝐝𝐚 𝐚𝐧𝐝 𝐀𝐦𝐚𝐳𝐨𝐧 𝐄𝐂𝐒 🎉 This video is part of a larger 10th anniversary plan for AWS Lambda and Amazon ECS to feature Serverless Heroes sharing their "𝒂𝒉𝒂" moments with Lambda and Amazon ECS. They discuss their first, most impactful, or most unforgettable projects, highlighting the builder experience and how these services empower them to innovate faster and build adaptable systems for the future. Amazon Web Services (AWS) #AWS #Lambda #ECS #Serverless https://lnkd.in/gfaSMiE7 Also, I wrote a blog post about my experience with AWS Lambda and Amazon ECS. You can read it here: https://lnkd.in/gP6DygeA

Day 5 of #30DaysAWSCloudChallenge is done and today’s focus was Amazon S3 (Simple Storage Service)—an incredibly scalable, durable, and secure object storage solution from AWS! 🚀 Here’s a snapshot of today’s journey: 1. Accessed the S3 Console: Logged in to AWS and explored the S3 console. 2. Bucket Creation: Created a new S3 bucket, selecting configurations for region and access settings. 3.Uploading Objects: Uploaded files to my bucket, using various storage classes to manage costs. 4. Setting Permissions: Configured access control policies to manage who can access and edit my files. 5. Exploring S3 Features: Explored versioning, logging, and lifecycle management to enhance data protection and optimize storage costs. Amazon S3’s flexibility and extensive features are helping me understand scalable storage solutions better, and I’m excited to apply these in real-world projects! A big shoutout to Nandan S, Latchiya Raman, and my peers at the AWS Cloud Club St.Joseph's Group of Institutions Cloud Club for their continued guidance and support. #AWS #CloudComputing #AmazonS3 #AWSChallenge #DataStorage #AWSCloudClub #StJosephsGroup

🚀 Exciting news! Just published a new blog post on implementing hardware resiliency in your training infrastructure for AWS Neuron nodes within Amazon EKS clusters. Learn how to create a fault-tolerant environment for handling hardware failures during model training. Check out the comprehensive guide and solution overview here: [Node Problem Detection and Recovery for AWS Neuron Nodes within Amazon EKS Clusters](https://ift.tt/9jfgVU3). #AWS #AmazonEKS #MachineLearning #NeuronNodes

If I had to pick one AWS service to shut down (and it can’t be Chime), I’d go with AWS OpsWorks Stacks. Here’s why: 1. It’s Already on the Chopping Block 👇🏼 AWS has already said they’re discontinuing OpsWorks Stacks on May 26, 2024. They stopped taking new customers last year, so it’s pretty clear they’re phasing it out. 2. Time to Move On 👇🏼 AWS is actually recommending that users switch over to AWS Systems Manager. It’s a more modern tool that works better with other AWS services. 3. Keeping Things Simple 👇🏼 Getting rid of OpsWorks Stacks makes sense since AWS is trying to streamline its offerings. Focusing on newer, better services means a smoother experience for everyone. 4. Better Features 👇🏼 AWS Systems Manager not only replaces OpsWorks Stacks but also comes with some cool features that make managing your apps easier. So, yeah, shutting down OpsWorks Stacks would help AWS clean things up and guide users toward a more effective solution. It’s a win-win! 🏆 What’ll you choose?