Welcome to Pizza Time!
Deploying the First Iteration of Our Business Application
Adding Analysis, Monitoring and Cost Management
Pizza Time is Going Global!
In this Group of lectures we will introduce you to the Pizza Time business and system requirements. Pizza Time requires a simple ordering solution that can be implemented quickly and with minimal cost, so we will do a hands deployment of version 1.0 of our solution. To achieve that we are going to use a single region and deploy application using AWS Elastric Beanstalk. We will implement a simple database layer that will be capable of delivering on these initial requirements for Pizza Time.
It turns out that the Pizza Time business is a success and the business now wants to target a global audience. We discuss and design how we can increase the availability of our initial Pizza Time application, then begin to deploy V2 of Pizza Time - a highly available, fault tolerant business application.
Hi and welcome to this lecture.
We are going to dedicate this entire lecture to talk about costs monitoring with CloudWatch. I don't really have much to say or show using the slides so let's go directly to the AWS console and learn how to monitor costs with CloudWatch.
Here, the AWS console. Let's click on CloudWatch. I said that in the first lecture of the monitoring section, we need to go to the Northern Virginia region in order to see billing metrics. If we click in here, for example, AWS says exactly that.
We need to switch region. Here, at the right region, we can see that we have a new name space in here, which is called “Billing”. In here, we can see the “Estimated Charges” per services or we can see the “Estimated Charges” for other services within our account.
To monitor costs, it is a best practice that we create a few billing alarms. For example, if you have a budget of $100 per month. You can select the “Estimated Charges” metric and you can click in here to create an alarm. You don't want to be notified once you exceed $100. It's better to be notified if you exceed, for example, $70 because you have a way to stop your charges to control your expenses before reach your budget. You can set a series of billing alarms and you'll be notified as you expend more money in your account. I will create 3 alarms in here. I will create $70 $85 and $100. With these alarms, I can control better my expenses because I'll be notified when I reach 70%, for example, 70% of my budget in this case, 85% and 100%.
I won't be surprised with a single alarm saying that I already blow my whole budget.
About the Author
Eric Magalhães has a strong background as a Systems Engineer for both Windows and Linux systems and, currently, work as a DevOps Consultant for Embratel. Lazy by nature, he is passionate about automation and anything that can make his job painless, thus his interest in topics like coding, configuration management, containers, CI/CD and cloud computing went from a hobby to an obsession. Currently, he holds multiple AWS certifications and, as a DevOps Consultant, helps clients to understand and implement the DevOps culture in their environments, besides that, he play a key role in the company developing pieces of automation using tools such as Ansible, Chef, Packer, Jenkins and Docker.