Most likely,
just like the other services and systems we've seen
in previous labs in this course,
cloud monitoring will be built into your management console.
What are you looking for with your cloud‑monitoring architecture?
You're looking for inordinate data flows,
so things that do not look normal,
based off of what normally is consumed in your distributed application systems.
Your cloud monitoring system will be able to show you what
makes sense of a large quantity of data in the form of metrics
and logs from previous services.
Also,
you'll be able to check out various services that cross the SPI stack of SaaS,
PaaS, and IaaS, including containers and microservices.
It's an excellent way to be effective in meeting the goals of environmental
visibility and getting insight into services and statuses.
This is especially true in multi‑cloud environments.
The main component that is utilized is the API.
We're going to move into a demo,
where we will log into the AWS Management Console again and configuring
monitoring by using both CloudTrail and CloudWatch.
It's important to understand that all the API accesses are
monitored by your cloud service provider.
You can then take those and set up different alerts and alarms and ways
of being able to manage accesses to your resources.
So let's head over there.
So here we are back in the management console,
and the first place we're going to go to is CloudTrail.
CloudTrail tracks all of the user activity when it comes to accessing APIs,
so every time there is consumption of an API,
CloudTrail automatically audits that and then puts it inside of the
Event history without you having to do anything.
So, just scrolling through here,
you can see the times that I stopped/started sessions,
I updated instance information,
or that I modified some other configuration setting.
What we want to do is go to the Dashboard and create a trail for ourselves.
Let's just name it the CCSPOPERATIONS as the trail name.
Now, it gets stored in object storage,
that's where the data that comes out of the trail goes to,
and automatically it wants to encrypt it,
which is a good idea, but we're not going to do that right now,
and you can also make it so that it goes to CloudWatch.
Now CloudWatch in the AWS world is an ingestion point for CloudTrail,
that's where we can configure rules for certain types of events
and then get notifications of those events.
So let's step to the process, and we're going to name it the role,
CCSPOPERATIONS, and go ahead and select Next.
What we're interested in is Management events,
and go ahead and select Next, and then we're going to create the trail.
So now, go back to our Dashboard.
We'll actually see that that trail will be alive and working for us.
So there's our trail.
We can see it up and running and already logging.
If we go check it out,
we can see all the configuration options that we set up are now functional.
Next, what we want to do is create a CloudWatch rule.
Recall that CloudTrail will take its data and push it to CloudWatch,
which is the native logging tool that is in use in the AWS Management Console.
So, let's go to CloudWatch, select that.
And what we will do here is head over to the Events,
open that up, and select Rules.
And we want the traditional CloudWatch rules, and we can select create.
And here,
you can be very specific about the type of event that
you're concerned being notified about.
So,
let's say that we had EC2 as our focus and the event start, maybe it is
EBS Snapshot Notification since we created a snapshot, and the next
thing that it wants to do is to add a target.
Now over here,
what we could do is to set up a target that is part of what's called a topic.
I would have had to create a topic.
And really, what that is, is an enunciation of an event.
If I had created that topic and associated it with my email,
then all I'd simply have to do is add the topic here,
and whenever anything changes with the snapshot,
I would get an email for it.
So that's an example,
just a very brief and surface example of what it would take to create a
notification that is going to have someone take action,
based off of the monitoring that's going on in the system.