Learning Objectives: In this module, you will learn about the different services provided by AWS. You will be provided with an overview of important resources required for architecting an application.
Topics:
  • Cloud Computing
  • Cloud deployment and service models
  • AWS Global Infrastructure and its benefits
  • AWS Services
  • Ways to access AWS Services
Learning Objectives: In this module, you will learn about security management in AWS using Identity Access Management (IAM) and Key Management Service.
Topics:
  • User management through Identity Access Management (IAM)
  • Various access policies across AWS Services
  • API keys service access
  • Best practices for IAM
  • Key Management Service
  • Access billing and create alerts on billing
Learning Objectives: In this module, you will learn about the different Object Storage Services offered by AWS, identify when to use a specific service, how to store/transfer data using these services and optimize the storage cost.

Topics:
  • S3 bucket – Creation, Version Control, Security, Replication, Transfer Acceleration
  • Storage classes in S3
  • Life cycle policy in S3
  • Cost optimization for S3
  • CloudFront – Create and configure with S3
  • Snowball
  • Storage Gateway and its types
Learning Objectives: EC2 (Elastic Compute Cloud) is the backbone of AWS. In this module, you will learn about the concepts associated with an EC2 instance and their usage. This module covers different Amazon AMIs, a demo on launching an AWS EC2 instance, ways to connect with an instance and how to host a website on AWS EC2 instance.
Topics:
  • Start, stop and terminate an EC2 Instance
  • Security Group
  • AMI
  • VPC, ENI, Public and Private IP
  • Storage services
  • EBS and its types
  • EFS
  • Cost optimization

Learning Objectives: In this module, you will learn the concepts of Load Balancing, Auto-Scaling and Route 53 to manage traffic.

Topics:

  • Elastic Load Balancer and its types
  • Comparison of Classic, Network and Application Load Balancer
  • Auto-Scaling
  • Components of Auto-Scaling
  • Lifecycle of Auto-Scaling
  • Auto-Scaling policy
  • Working of Route 53
  • Various Routing Policies

Learning Objectives: In this module, you will learn about the different database services offered by AWS to handle structured and unstructured data. Also, learn how to analyze your data.

Topics:

  • Amazon RDS and its benefits
  • Amazon Aurora
  • Amazon DynamoDB
  • ElastiCache
  • Amazon RedShift
  • AWS Kinesis
Criteria AWS OpenStack
License Amazon proprietary Open source
Operating system Whatever the cloud administrator provides Whatever AMIs provided by AWS
Performing repeatable operations Through templates Through text files

AWS (Amazon Web Services) is a platform to provide secure cloud services, database storage, offerings to compute power, content delivery, and other services to help business level and develop.

An Elastic Load Balancer ensures that the incoming traffic is distributed optimally across various AWS instances.  A buffer will synchronize different components and makes the arrangement additionally elastic to a burst of load or traffic. The components are prone to work in an unstable way of receiving and processing requests. The buffer creates an equilibrium linking various apparatus and crafts them work at an identical rate to supply more rapid services.

Both Spot Instance and On-demand Instance are models for pricing.

Spot Instance On-demand Instance
With Spot Instance, customers can purchase compute capacity with no upfront commitment at all. With On-demand Instance, users can launch instances at any time based on the demand.
Spot Instances are spare Amazon instances that you can bid for. On-demand Instances are suitable for high-availability needs of applications.
When the bidding price exceeds the spot price, the instance is automatically launched, and the spot price fluctuates based on supply and demand for instances. On-demand Instances are launched by users only with the pay-as-you-go model.
When the bidding price is less than the spot price, the instance is immediately taken away by Amazon. On-demand Instances will remain persistent without any automatic termination from Amazon.
Spot Instances are charged on an hourly basis. On-demand Instances are charged on a per-second basis

EBS-backed instances. EBS-backed instances use EBS volume as their root volume. EBS volume consists of virtual drives that can be easily backed up and duplicated by snapshots. The biggest advantage of EBS-backed volumes is that the data can be configured to be stored for later retrieval even if the virtual machine or the instances are shut down.

Amazon Glacier. AWS Glacier is an extremely low-cost storage service offered by Amazon that is used for data archiving and backup purposes. The longer you store data in Glacier, the lesser it will cost you.

By configuring the bucket policy to provide public read access to all objects

Learning Objectives: This module introduces you to the Amazon Virtual Private Cloud. You will learn to implement networking using public and private subnets with VPC. Also, this module demonstrates how to monitor your services.

Topics:
  • VPC – Benefits and Components
  • CIDR Notations
  • Network Access Control List v/s Security Groups
  • NAT – Network Address Translation
  • VPC peering
  • AWS CloudWatch
  • AWS CloudTrail
  • Trusted Advisor
Learning Objectives: In this module, you will learn about the different Application services offered by AWS that are used for sending e-mails, notifications, and processing message queues. This module also deals with the latest trend of Serverless architecture using AWS Lambda.
 
Topics:
  • AWS Simple Email Service (SES)
  • AWS Simple Notification Service (SNS)
  • AWS Simple Queue Service (SQS)
  • AWS Simple Work Flow (SWF)
  • AWS Lambda

Learning Objectives: This module helps you learn various AWS services and tools used for configuration management and Automation.

Topics:

  • AWS CloudFormation
  • AWS OpsWorks – OpsWorks for Chef Automate, OpsWorks for Stack, OpsWorks for Puppet Enterprises
  • AWS Elastic Beanstalk
  • Differentiate between CloudFormation, OpsWorks, and Beanstalk

Learning Objectives: This module gives you an idea about the importance of AWS guidelines for Well Architected Framework. You will also learn about the Resilient and Performant architecture designs.

Topics:

  • Determine how to design high-availability and fault-tolerant architectures
  • Choose reliable/resilient storage
  • Determine how to design decoupling mechanisms using AWS services
  • Determine how to design a multi-tier architecture solution
  • Disaster Recovery Solution
  • Choose performant storage
  • Apply caching to improve performance
  • Design solutions for elasticity and scalability
Learning Objectives: Adding to Module 10, this module covers the remaining three concepts behind AWS Well-Architected Framework – Securing Applications and Architectures, Designing Cost-Optimized Architectures, Defining Operationally Excellent Architectures.

Topics:
  • Well-Architected Framework
  • Specify Secure Applications and Architectures
  • Design Cost-Optimized Architectures
  • Define Operationally-Excellent Architectures
Learning Objective: This module primarily focuses on exam questionnaires and the tips that will prepare you for ‘AWS Solution Architect Certification Exam’.
Topics:
  • AWS Solution Architect Certification Exam Guide
  • Certification Exam Questionnaires

Creating subnets means dividing a large network into smaller ones. These subnets can be created for several reasons. For example, creating and using subnets can help reduce congestion by making sure that the traffic destined for a subnet stays in that subnet. This helps in efficiently routing the traffic coming to the network that reduces the network’s load.

No, standby instances are automatically launched in different availability zones than the primary, making them physically independent infrastructures. This is because the whole purpose of standby instances is to prevent infrastructure failure. So, in case the primary goes down, the standby instance will help recover all of the data.

Amazon Snowball. AWS Snowball is the data transport solution for large amounts of data that need to be moved into and out of AWS using physical storage devices.

No, the standby DB instance cannot be used along with the primary DB instances since the standby DB instances are supposed to be used only if the primary instance goes down.

The data stored on the instance will be lost. Elastic IP is disassociated from the instance only if the instance is terminated.

A bigger RDS instance type needs to be opted for handling large amounts of traffic, creating manual or automated snapshots to recover data in case the RDS instance goes down.