Content Domain 1: Cloud Concepts

Let's get started with Domain 1 covering cloud concepts such as what is AWS, the benefits of AWS, design principles, migration, and economics. Domain 1: Cloud concepts is broken into four task statements that we will discuss over the next few lessons. Task statement 1.1: Define the benefits of the AWS Cloud. Task statement 1.2: Identify design principles of the AWS Cloud. Task statement 1.3: Understand the benefits of and strategies for migration to the AWS Cloud. And task statement 1.4: Understand concepts of cloud economics. For the first task statement, we will start with AWS fundamentals. Cloud computing isn't a buzzword. It is a unique type of computing that has a formal set of definitions. We will dive deeper into what is AWS and step through what makes cloud, cloud. For the second task statement, we will focus on design principles for AWS and talk about the AWS Well-Architected Framework, best practices, and core strategies for our architecting systems in the cloud. For the third task statement, we will focus on reducing database costs and improving availability when you migrate to AWS. We will talk about the AWS storage services and ensure you understand the type of data that you have and what data store is needed. For the fourth task statement, we will focus on understanding the concepts of cloud economics and multiple ways to run a cost-optimized environment. Over the next several videos in this module, I will address each task statement individually, breaking down the knowledge and skills expected of you to be successful. Let's get started to evaluate your readiness for the exam in the next video where we will cover the first task statement from Domain 1, define the benefits of the AWS Cloud.

Content Domain 2: Security and Compliance

Let's get started with Domain 2, which covers security and compliance. This domain covers the AWS shared responsibility model, security, access management, and compliance. One key aspect of demonstrating your understanding of AWS is being able to recognize who is responsible for what, in regards to security. In AWS, some of the technical details about how services are hosted or how data is stored can be abstracted from you, but it doesn't mean that you are not responsible for security in AWS. You should be able to identify when security measures need to be put in place, and when security measures are already put in place by AWS for you. Domain 2, security and compliance, is broken into four task statements that we'll discuss over the next few lessons. Task statement 2.1: understand the AWS shared responsibility model. Task statement 2.2: understand AWS Cloud security, governance, and compliance concepts. Task statement 2.3: identify AWS access management capabilities, and task statement 2.4: identify components and resources for security. For the first task statement, we will focus on the AWS shared responsibility model. Being a cloud practitioner means you need to be able to determine when you need to secure resources within AWS and the depth to which you need to be involved for security, which can vary from service to service. For the second task statement, we will focus on understanding security, governance, and compliance concepts. For the third task statement, we will focus on access management in AWS. We just mentioned that the level of responsibility the customer assumes changes, depending on the service they're using, but you are always responsible for access management to your environment. For the fourth task statement, we will dive deeper in how to secure the different AWS services. You don't need to know the step-by-step directions on exactly how to enable security within AWS for this exam, but you do need to know generally what security features exist, and when you are responsible for enabling them. Over the next several videos in this module, I'll address each task statement individually, breaking down the knowledge and skills expected of you to be successful. Let's get started to evaluate your readiness for the exam in the next video, where we will cover the first task statement from Domain 2, which is to understand the AWS shared responsibility model.

Content Domain 3: Cloud Technology and Services

Let's get started with Domain 3 covering cloud technology and services. With cloud concepts and security and compliance already covered in earlier lessons, now we will dive deeper into the AWS services and technology and talk about types of AWS services, the infrastructure, and the operational aspects of using the AWS Cloud. Domain 3: Cloud Technology and Services is broken into 8 task statements that we will discuss over the next few lessons. Task statement 3.1: Define methods of deploying and operating in the AWS Cloud. Task statement 3.2: Define the AWS global infrastructure. Task statement 3.3: Identify AWS compute services. Task statement 3.4: Identify AWS database services. Task statement 3.5: Identify AWS network services. Task statement 3.6: Identify AWS storage services. Task statement 3.7: Identify AWS artificial and machine learning services and analytics services. And task statement 3.8: Identify services from other in-scope AWS service categories. For the first task statement, we will cover the methods of deploying and operating in AWS, focusing on types of deployment models, and connectivity options. For the second task statement, we will dive a bit deeper into the AWS global infrastructure and components that make up our global infrastructure, such as the Availability Zones, Regions, and edge locations. For the third task statement until the eighth and last task statement, we will talk all about AWS core services. I'll talk about the categories of core services, and then give some examples of each. There are 4 categories of services when discussing the core AWS services: Compute, Storage, Networking, and Database, but we will also cover artificial intelligence, machine learning, analytics, and a few other AWS services that are in scope for this exam. Ensure you know how various AWS services fit into the different categories of compute, storage, networking, and more. What makes a service compute versus database, and what does that say about the services? Is there any overlap you should be aware of? Next, be aware of why you would choose one category and service over another. When would you choose a database service over running a database on an Amazon EC2 instance? And last, pay attention to what sort of subcategories exist within each of the separate larger categories of the services. We will cover all of this. Over the next several videos in this module, I will address each task statement individually, breaking down the knowledge and skills expected of you to be successful. Let's start to evaluate your readiness for the exam in the next video where we will cover the first task statement from Domain 1: Define the methods of deploying and operating in AWS.

Content Domain 4: Billing, Pricing, and Support

Let's get started with domain 4, covering billing, pricing, and support. This domain covers how AWS billing and pricing plays out in the real world. Remember, fundamentally, cost and billing shifts in AWS from running on premises. When you run on-premises environments for technical resources like an on-premises database, that generally means you have a fixed-cost model because you purchase the hardware upfront and then pay it down over time and pay the operating expenses month to month, which are predictable and planned for. When you shift to using AWS to host technical resources, that pricing model changes. Instead of costs being generally fixed month to month, you will now be working with a variable pricing model, meaning that costs can change from month to month. Domain 4, billing, pricing, and support, is broken into three task statements that we will discuss over the next few lessons. Task statement 4.1, compare AWS pricing models, task statement 4.2, understand resources for billing, budget, and cost management, and task statement 4.3, identify AWS technical resources for AWS support options. For the first task statement, we will focus on AWS pricing models. As you probably know by now, in AWS, you only pay for what you use, and what you use may change from month to month depending on your usage patterns. This variable pricing model means a few things. First, it may be more challenging to predict why you get used to the different pricing structures within AWS, but it also means that you will have the power to influence your AWS bill month to month by changing your architectures, usage patterns, and approaches to solving problems. For the second task statement, ensure you know you can estimate, track, break down, and influence your AWS bill, and understand resources for billing, budget, and cost management. For the third task statement, ensure you can identify resources available for billing support and AWS support options. Over the next several videos in this module, I will address each task statement individually, breaking down the knowledge and skills expected of you to be successful. Let's start to evaluate your readiness for the exam in the next video, where we will cover the first task statement from domain 4 to compare AWS pricing models.