Hi everyone👋, My name is Zandile. I live in Johannesburg, South Africa and I am junior cloud engineer and I am currently studying towards my SSA-CO3 certification. I plan on becoming an AWS DevOps Engineer by February 2025. I want to get these 3 things from the community: 1.  Learn more deeply about AWS. 2. Create projects to enhance my skillset 3. Meet amazing likeminded people. For fun I like to do these 3 things: 1.  Nap 2. Read 3. Do some adventures like quad biking and skydiving. Looking forward to meeting all of you!😁

Hi guys, It’s been a while, and trust me, I’ve been really trying to get back on this space. However, juggling a new job and a home move has been quite the challenge—a tough combination to manage at the same time! I’ve been keeping up with the posts and messages, but I just haven’t had the time to properly engage with them. Most of our meeting times have found me either on the road or busy with something related to the new job or the move. I’m optimistic that things will settle down in the next two weeks (or sooner), and I’ll be able to fully reconnect. My mind has always been here, even though time and circumstances haven’t allowed me to be as present as I’d like. Looking forward to catching up properly soon! Yours in Edge Location 🤣 Adebayo

Hi everyone I run the script Fernando asked us to run to reduce cost but looks like the there was an error and I have been incurring cost since. See error screenshot below

As a service I’m already familiar with, I easily set up a $5 spending cap for the new AWS account and configured two threshold alerts: 1. 90% Forecasted Alert: This alert triggers an SNS (Simple Notification Service) notification to my predefined email address when projected spending exceeds 90% of the budget cap. This means you receive a notification when you’re likely to incur around $4.50 in charges based on the services you’ve activated, allowing you to make adjustments proactively and safeguard against unexpected costs. 2. 80% Actual Cost Alert: This alert notifies you when you’ve actually spent 80% of your budget. You can then filter through the Cost and Billing Management Console to get a clear understanding of what’s driving your expenses. Additionally, you can configure actions to be triggered when these alerts are activated. For example, you could set up an automatic EC2 termination or similar actions. However, since we don’t have any services running at the moment, we can’t explore this option yet. Thanks for attending my Ted Talk!

In today’s landscape, the choice between Cloud and On-Premise infrastructure is no longer up for debate, especially considering the cost advantages in terms of both CapEx (Capital Expenditures) and OpEx (Operating Expenses). However, a pressing question for startups is, which cloud provider to choose. For a startup, AWS (Amazon Web Services) stands out as an ideal choice for several compelling reasons: 1. Breadth of Services and Ecosystem Integration: AWS offers the widest range of services compared to other cloud providers, such as Azure and Google Cloud (GCP). While all three providers offer similar services—like AWS Lambda vs. Azure Functions, Amazon S3 vs. Azure Blob Storage, or Amazon EKS vs. Azure Kubernetes Service (AKS)—AWS consistently provides greater depth and flexibility in its offerings. For instance, AWS Lambda integrates seamlessly with a comprehensive suite of AWS services, including S3 for storage, API Gateway, DynamoDB for NoSQL databases, CloudWatch for monitoring, and Step Functions for managing complex workflows. While Azure Functions offers similar integrations, AWS’s extensive service catalogue and interconnectedness provide developers with more flexibility and options, making it easier to scale and optimize according to evolving business needs. 2. Superior Containerization and Serverless Offering: AWS offers two fully managed container orchestration services—Amazon ECS (Elastic Container Service) for users preferring AWS’s simpler, proprietary orchestration, and Amazon EKS (Elastic Kubernetes Service) for those who prefer Kubernetes. This dual offering provides more choices based on your startup’s unique needs. In contrast, Azure primarily focuses on AKS for Kubernetes users, offering less flexibility in container orchestration. Moreover, AWS Fargate further enhances AWS’s container strategy by enabling serverless containers, which can run on either ECS or EKS without needing to manage the underlying infrastructure. While Azure Container Instances (ACI) offers similar serverless container functionality, AWS Fargate integrates more deeply into AWS’s container ecosystem, allowing for smoother and more automated scaling.