Hello, my name is Demetria Crawford, and in this lesson we will review AWS Systems Manager. AWS Systems Manager is a collection of capabilities to help you manage your applications and infrastructure running in the AWS Cloud. Systems Manager simplifies application and resource management, shortens time to detect and resolve operational problems, and helps you manage your AWS resources securely at scale. So if you notice on our diagram, we have several different services that we have here. So from the AWS Management Console once we open up the Systems Manager, we have various objectives that we can run. We can focus on inventory, we can focus on the state of our AWS infrastructure, we can handle patch management, we have Session Manager to manage our sessions, which is connecting back into our CLIs, and then Fleet Manager to manage our fleet of instances and services that we have running. We also have the capability to use what's called OpsCenter and Incident Management so that we can state how we are managing instances or any issues that arise within our AWS infrastructure. We can manage the building of various services to create an infrastructure. For example, we can have a actual template created that says this is how our EC2 instances will look, these are the configurations for those instances, and based off of this template, this is how you build everything. Let's go ahead and take a look at AWS Systems Manager. From the AWS Console, if you'll type in Systems Manager, it will bring up AWS Systems Manager as the first option, or if you've recently opened it, you can click on Systems Manager. From here on our left-hand side we have our Quick Setup list. You'll notice that they're broken into categories based off of what you're trying to accomplish. If we want to manage our operations, the first option we have available is Operations Management, where we have our OpsCenter. We can create customized CloudWatch dashboards to set up what we want to monitor and we can create incident management solutions here. Let's click on CloudWatch Dashboard. You'll notice that right now we don't have any, but if you click on Create Dashboard, the orange button on the right, we'll give it our name of labsdbs. Click Create Dashboard, and now you can tell it what type of widgets you want to include, such as graphs, the type of graphs, do you want a pie chart, bar chart? Are you just adding numbers that you want to see at a certain place? You can select the widget type that you want to have on your dashboard, and from there you're gonna connect it to the type of data that it's going to actually show on the dashboard. So you can build this for your actual AWS account, the infrastructure that you have set up. We're gonna click the X on this so we don't create one. Now, if you click on Incident Manager, the first thing is once we actually set up our environment we have to click the Get Prepared orange button. And this allows us to prepare for automated responses where you're going to create response plans based off of the type of incidents. Who's notified, what actions do you want to be automated as far as within your AWS infrastructure? You can create response plans, escalation plans, create contacts, and edit the settings from under the Incident Manager dropdown list. If we scroll down, we also have Application Management, where you can actually do app configuration and use what's called the parameter store. Within the parameter store, we can set specific parameters that is pulled whenever information is needed. For example, a best practice from a security perspective is we never, never, never place our username and passwords within an application. Instead, we would tell the application to pull information from the parameter store where your data is secured. We can set specific parameters such as if someone is connecting to a website from the United States use the dollar symbol. If they're connecting from the UK, use the pound symbol. Use the representation of what currency is used within that region. So we can set that within the parameter store. Next we have Node Management and this is where our Fleet Manager is. We can identify all of the resources that we have running. For example, we may wanna see how many systems are running with a specific application on it. These are different things that we can do as far as querying, the resources that we have available to us or that we're running by going into our Fleet Manager. Let's click on Fleet Manager. So once we are in Fleet Manager, we can actually streamline our node management. We can troubleshoot nodes, including our EC2 instances and Edge devices. You can complete prerequisites such as installing various clients or configurations by pushing these through Fleet Manager. We can also perform troubleshooting and monitor our fleet through Fleet Manager. If we click on the three lines, we can go back and see some of our other options. If you're looking for Session Manager, which we can use to connect to our CLIs, that is under Node Management as well. Another tool we have available to us is to Run Command. With Run Command, we can use this to actually use what we would consider Run Command onto one of our instances. And finally, Patch Manager to patch our nodes is found under Node Management as well. Stay tuned for the next lesson, where we will review Cloud Monitoring. Thanks for watching.