Understand why to set up a dedicated AWS account for testing and learning AWS monitoring. Be reminded of key practices including using a non-root IAM account, setting up a billing alert, and others.
- [Instructor] So, in this section, we're going to actually start doing monitoring. So we're going to monitor core AWS services. We're going to start with the foundational services, S3 for files, and EC2 for compute. And then we're going to look at other commonly used services, such as Elastic Beanstalk, Elastic Container Service posting for Docker, and AWS Lambda for compute, and for database, we're going to look at RDS, or Relational Database Service. Probably use mySQL there. And Redshift, which is a data warehousing solution.
We're going to look, also, at specialty AWS services, like Kinesis, which is a data pipeline, and Elastic MapReduce, which is Hadoop. Now, if all this sounded like jargon to you, because you're new to AWS, I'll mention again, you may want to take a look at other foundational AWS courses in the LinkedIn learning library. Now, to setup for monitoring, you're going to want to create a test AWS account, so a unique account. You can use a Free Tier for some services for a new account. Some of the other services though, most notably, Elastic MapReduce or a managed Hadoop on AWS does not have a Free Tier, and I'll try to call these out, because I am going to be showing some things at load.
If you replicate this, you want to make sure that you understand what the costs are. You want to use AWS best practices, especially if you're doing this at work. You want to access your account as a Nonroot user, so you want to create a user that is different than the user who created the account, and give them the appropriate level of permissions. You want to create an AWS billing alert, so that you are notified if you forget to turn services off, or if services are getting into a pricing level that you don't anticipate, and you want to turn services off, and/or delete them when you are done testing.
- Understanding approaches to monitoring
- Matching business application priorities to monitoring approaches
- Tools for monitoring and logging
- Monitoring core AWS Services
- Using CloudFormation templates
- Monitoring S3, EC2, Lambda, RDS, Kinesis, and EMR
- Using core AWS tools for metrics and logging
- Using AWS services for advanced monitoring