AWS AI Practitioner - Introduction to AWS & Cloud Computing

Traditional IT - Overview

How Websites Work:

Every website interaction involves a client (your browser) sending a request across a network to a server, which processes it and returns a response. Both sides are identified by unique IP addresses -- think of them like postal addresses that ensure data reaches the right destination.

Request-Response Flow (ASCII Diagram):

+----------+    HTTP Request     +----------+
|  CLIENT  | ------------------> |  SERVER  |
| (Browser)|                     |(Web Host)|
|          | <------------------ |          |
+----------+   HTTP Response     +----------+
     |                                 |
     v                                 v
  IP: 192.168.1.1              IP: 54.239.28.85

What a Server Contains:

• CPU - the processing brain; executes instructions and calculations
• RAM - fast, volatile memory for active data; lost when power is off
• Storage (HDD/SSD) - persistent, long-term data storage for files and databases
• Networking components - NICs, routers, switches, DNS that handle data flow
• Motherboard - the main circuit board connecting all components
• Power Supply Unit (PSU) - provides electrical power to all components

Networking Fundamentals:

• Network - interconnected devices that can communicate
• Router - directs packets between different networks (like a post office sorting hub)
• Switch - delivers packets to the correct device within the same local network
• DNS - translates human-readable domain names (google.com) into IP addresses
• Packet - small unit of data transmitted over a network
• Firewall - security device that monitors and controls incoming/outgoing network traffic
• Load Balancer - distributes incoming traffic across multiple servers

Network Topology (ASCII Diagram):

                    +-------------+
                    |   INTERNET  |
                    +------+------+
                           |
                    +------v------+
                    |   ROUTER    | <-- Connects different networks
                    +------+------+
                           |
                    +------v------+
                    |   SWITCH    | <-- Connects local devices
                    +------+------+
                           |
         +-----------------+-----------------+
         |                 |                 |
    +----v----+      +-----v-----+    +------v------+
    | Server 1|      |  Server 2 |    |   Server 3  |
    +---------+      +-----------+    +-------------+

The Problem with Traditional On-Premises IT:

Organizations historically bought and housed their own servers -- first at home or in a garage, then in dedicated data centers. This model creates significant operational burden:

• High fixed costs: rent, electricity, cooling, hardware purchase
• Slow provisioning: ordering and installing new servers takes weeks or months
• Poor scalability: can't rapidly handle unexpected traffic spikes (Black Friday scenario)
• Requires 24/7 in-house IT staff for monitoring and maintenance
• Single point of failure: a fire, flood, or power outage can bring everything down
• Stranded capacity: servers sit idle during low-traffic periods but must still be paid for
• Hardware depreciation: equipment becomes obsolete and needs replacement every 3-5 years
• Security burden: organization must handle all physical and cyber security themselves
• Disaster recovery complexity: setting up a secondary data center is extremely expensive

Traditional IT vs Cloud (Cost Comparison):

Traditional On-Prem:                         Cloud:
+---------------------+        +---------------------+
| Buy Servers ($$$)   |        | No upfront cost     |
| Buy Networking      |        | Pay per hour/second |
| Rent Data Center    |        | Scale instantly     |
| Hire IT Staff 24/7  |   vs   | AWS manages hardware|
| Pay even when idle  |        | Pay only when used  |
| 3-5 year commitment |        | No commitment       |
+---------------------+        +---------------------+
     CAPEX Model                    OPEX Model

Why This Matters for the Exam:

Understanding traditional IT pain points helps you articulate WHY cloud computing is valuable -- a common exam question angle. AWS frequently tests on matching cloud benefits to specific traditional IT problems.

Key Terms

Term	Definition
IP Address	A unique numerical label assigned to each device on a network, used to identify and locate it for communication. IPv4 uses 32-bit addresses (e.g., 192.168.1.1); IPv6 uses 128-bit addresses.
DNS (Domain Name System)	The internet's phonebook -- translates domain names like aws.amazon.com into IP addresses machines can route to.
Latency	The time delay between sending a request and receiving a response. Lower latency = faster response. Measured in milliseconds (ms).
On-Premises (On-Prem)	Infrastructure that a company owns, houses, and manages in its own physical location rather than using a cloud provider.
CAPEX (Capital Expenditure)	Upfront investment in physical assets like servers and data center equipment. High risk, slow to scale, and creates depreciation.
Throughput	The amount of data that can be transferred in a given time period. Usually measured in Mbps or Gbps. High throughput = more data transferred.
Bandwidth	The maximum rate of data transfer across a network path. Higher bandwidth capacity enables higher throughput.
Data Center	A physical facility housing computing equipment including servers, storage, and networking. Traditional IT requires companies to build or rent these.
Provisioning	The process of acquiring and setting up IT infrastructure. Traditional provisioning takes weeks; cloud provisioning takes minutes.

Practice Questions

What is Cloud Computing?

Definition:

Cloud computing is the on-demand provisioning of IT resources -- compute, storage, databases, networking, AI, and more -- over the internet, billed based on actual consumption rather than upfront ownership.

The Core Shift:

Instead of owning infrastructure, you rent capacity from a provider. You get what you need, when you need it, and stop paying the moment you stop using it.

Cloud Computing Visual Model:

    +-------------------------------------------------+
    |            THE CLOUD (Internet)                 |
    |  +---------+  +---------+  +---------+         |
    |  | Compute |  | Storage |  |Database |         |
    |  | (EC2)   |  |  (S3)   |  | (RDS)   |         |
    |  +---------+  +---------+  +---------+         |
    |  +---------+  +---------+  +---------+         |
    |  |  AI/ML  |  |Networking| |Analytics|         |
    |  |(Bedrock)|  |  (VPC)  |  |(Athena) |         |
    |  +---------+  +---------+  +---------+         |
    +---------------------+---------------------------+
                          | Internet
          +---------------+---------------+
          v               v               v
      +-------+      +-------+       +-------+
      | User 1|      | User 2|       | User 3|
      |(Laptop)|     |(Phone)|       |(Server)|
      +-------+      +-------+       +-------+

    Access from ANYWHERE using standard internet protocols

5 Essential Characteristics (NIST Definition -- exam-relevant):

• On-Demand Self-Service - spin up servers or storage in minutes through a console or API, no human from AWS required
• Broad Network Access - accessible from anywhere via internet using standard tools (browser, CLI, mobile app)
• Resource Pooling - AWS serves many customers from shared physical infrastructure using multi-tenancy; your data stays isolated and secure
• Rapid Elasticity - scale up during Black Friday traffic surge, scale down at 2am when demand drops; pay only for what you use
• Measured Service - like a utility bill; usage is tracked and you pay precisely for consumption

NIST Characteristics Visual:

+-----------------------------------------------------+
|          5 NIST CLOUD CHARACTERISTICS               |
+-----------------------------------------------------+
|  1. ON-DEMAND        | Self-service, instant access |
|     SELF-SERVICE     | No waiting, no tickets       |
+----------------------+------------------------------+
|  2. BROAD NETWORK    | Any device, anywhere         |
|     ACCESS           | Browser, CLI, mobile, SDK    |
+----------------------+------------------------------+
|  3. RESOURCE         | Multi-tenant, shared infra   |
|     POOLING          | Isolated & secure per user   |
+----------------------+------------------------------+
|  4. RAPID            | Auto-scale up and down       |
|     ELASTICITY       | Match resources to demand    |
+----------------------+------------------------------+
|  5. MEASURED         | Pay per use, like utilities  |
|     SERVICE          | Precise billing, no waste    |
+----------------------+------------------------------+

6 Advantages of Cloud Computing (Memorize These -- Exam Staple):

• Trade CAPEX for OPEX - no upfront server purchases; pay operational expenses only when consuming resources
• Benefit from Economies of Scale - AWS buys hardware at massive volume, passing savings to customers over time
• Eliminate Capacity Guessing - auto-scaling matches resource allocation to real demand automatically
• Increase Speed and Agility - new environments can be created in seconds vs. weeks with physical hardware
• Stop Spending on Running Data Centers - let AWS handle facilities management so your team focuses on business value
• Go Global in Minutes - deploy to any of AWS's global regions with a few clicks, reducing latency for international users

6 Advantages Memory Diagram:

+--------------------------------------------------------+
|        6 ADVANTAGES OF CLOUD COMPUTING                 |
+--------------------------------------------------------+
|                                                        |
|  [Money] 1. CAPEX -> OPEX        | No upfront cost           |
|                           | Pay only for usage         |
|  [Chart-Down] 2. ECONOMIES OF SCALE | AWS bulk pricing = savings |
|                           | Lower cost per unit        |
|  [Chart] 3. NO CAPACITY GUESS  | Auto-scaling handles spikes|
|                           | Never over/under provision |
|  [Lightning] 4. SPEED & AGILITY    | Deploy in minutes          |
|                           | Iterate quickly            |
|  [Building] 5. NO DATA CENTERS    | Focus on business          |
|                           | AWS handles facilities     |
|  [Globe] 6. GO GLOBAL FAST     | Deploy worldwide instantly |
|                           | Reduce global latency      |
|                                                        |
+--------------------------------------------------------+

Cloud Pricing Philosophy:

• You pay for what you consume, not what you reserve physically
• This eliminates stranded capacity -- idle servers that still cost money in traditional IT
• Enables small startups to access enterprise-grade infrastructure with zero upfront cost
• Three primary pricing dimensions: Compute (time), Storage (capacity), Data Transfer (egress)

Cloud vs. Traditional IT -- The Key Differences:

+-------------------+--------------------+--------------------+
|   DIMENSION       |  TRADITIONAL IT    |   CLOUD COMPUTING  |
+-------------------+--------------------+--------------------+
| Cost Model        | CAPEX (Buy upfront)| OPEX (Pay per use) |
| Provisioning Time | Weeks to months    | Minutes to seconds |
| Scaling           | Manual, slow       | Automatic, instant |
| Maintenance       | You manage all     | AWS manages infra  |
| Global Reach      | Build data centers | Click to deploy    |
| Risk              | High (hardware)    | Low (shared infra) |
| Idle Cost         | Pay for idle       | No idle cost       |
+-------------------+--------------------+--------------------+

Key Terms

Term	Definition
OPEX (Operational Expenditure)	Ongoing costs for running services, like a monthly cloud bill. Preferred over CAPEX because it's flexible and tied to usage.
Elasticity	The ability to automatically increase or decrease resource capacity in response to demand changes. Different from scalability -- elasticity is automatic and dynamic.
Scalability	The ability of a system to handle increased load. Can be vertical (bigger machine) or horizontal (more machines). Unlike elasticity, scaling may be manual.
Multi-Tenancy	Multiple customers sharing the same underlying physical infrastructure, with logical isolation ensuring security and privacy.
TCO (Total Cost of Ownership)	The full cost of owning and operating infrastructure over time. Cloud typically reduces TCO by eliminating hardware, maintenance, and staffing overhead.
Economies of Scale	As AWS serves more customers, its per-unit costs decrease, and it passes savings on as lower prices.
Vertical Scaling (Scale Up)	Adding more power (CPU, RAM) to an existing machine. Has physical limits and may require downtime.
Horizontal Scaling (Scale Out)	Adding more machines to distribute load. No theoretical limit and typically zero downtime. Cloud-native approach.
NIST	National Institute of Standards and Technology -- the US agency that published the official definition and 5 characteristics of cloud computing.
Pay-As-You-Go	Cloud pricing model where you pay only for resources consumed, similar to a utility bill. Core principle of cloud economics.

Practice Questions

The Different Types of Cloud Computing

Three Cloud Deployment Models:

1. Private Cloud

• Infrastructure dedicated to a single organization, managed internally or by a third party
• Greater control, customization, and security for sensitive regulated workloads
• Higher cost than public cloud -- no sharing benefits
• Use case: government agencies, financial institutions with strict compliance requirements
• Example provider: Rackspace, VMware, OpenStack
• Still uses cloud technologies (virtualization, self-service, elasticity) -- just not shared

2. Public Cloud

• Infrastructure owned and operated by a cloud provider, shared across many customers
• No capital investment required; fully managed hardware and facilities
• Pay-as-you-go; access from anywhere
• Major providers: AWS, Microsoft Azure, Google Cloud Platform (GCP)
• Most cost-effective due to economies of scale

3. Hybrid Cloud

• A deliberate combination of private (on-prem) and public cloud resources
• Sensitive or regulated data stays on-premises; burst workloads or less-sensitive systems go to public cloud
• Requires networking connectivity between environments (e.g., AWS Direct Connect or VPN)
• Use case: a bank keeps customer financial records on-prem but runs analytics in AWS
• Key AWS services: AWS Outposts (run AWS on-prem), Direct Connect, VPN, Storage Gateway

Deployment Models Visual:

+---------------------------------------------------------------+
|                  CLOUD DEPLOYMENT MODELS                      |
+-----------------+-----------------+---------------------------+
|  PRIVATE CLOUD  |  PUBLIC CLOUD   |     HYBRID CLOUD          |
+-----------------+-----------------+---------------------------+
| +-------------+ | +-------------+ | +-------+    +-------+   |
| |  Dedicated  | | |   Shared    | | |On-Prem|<-->| AWS   |   |
| |  to ONE     | | |   Multi-    | | |Private|    |Public |   |
| |  Organization| | |   Tenant    | | +-------+    +-------+   |
| +-------------+ | +-------------+ |    Connected via VPN/     |
|                 |                 |    Direct Connect         |
| You own/lease   | AWS owns all    |                           |
| Examples:       | Examples:       | Examples:                 |
| * VMware        | * AWS           | * AWS Outposts            |
| * Rackspace     | * Azure         | * Storage Gateway         |
| * OpenStack     | * GCP           | * Direct Connect          |
+-----------------+-----------------+---------------------------+

Three Cloud Service Models -- The Responsibility Pyramid:

IaaS vs PaaS vs SaaS Responsibility Diagram:

+--------------------------------------------------------------------+
|         WHAT YOU MANAGE vs WHAT AWS MANAGES                        |
+--------------------------------------------------------------------+
|                                                                    |
|   ON-PREM         IaaS           PaaS           SaaS               |
|   (Traditional)   (EC2)      (Elastic BS)    (WorkMail)            |
|                                                                    |
|  +----------+   +----------+   +----------+   +----------+        |
|  |   DATA   |   |   DATA   |   |   DATA   |   |   DATA   | <- YOU |
|  +----------+   +----------+   +----------+   +----------+        |
|  |   APP    |   |   APP    |   |   APP    |   |##########| <- AWS |
|  +----------+   +----------+   +----------+   +----------+        |
|  | RUNTIME  |   | RUNTIME  |   |##########|   |##########|        |
|  +----------+   +----------+   +----------+   +----------+        |
|  |    OS    |   |    OS    |   |##########|   |##########|        |
|  +----------+   +----------+   +----------+   +----------+        |
|  |  VIRT.   |   |##########|   |##########|   |##########|        |
|  +----------+   +----------+   +----------+   +----------+        |
|  | SERVERS  |   |##########|   |##########|   |##########|        |
|  +----------+   +----------+   +----------+   +----------+        |
|  | STORAGE  |   |##########|   |##########|   |##########|        |
|  +----------+   +----------+   +----------+   +----------+        |
|  | NETWORK  |   |##########|   |##########|   |##########|        |
|  +----------+   +----------+   +----------+   +----------+        |
|                                                                    |
|  YOU manage      ### AWS manages                                   |
|  EVERYTHING      ### shaded layers                                 |
|                                                                    |
|  MORE Control <----------------------------------> LESS Control    |
|  MORE Work                                          LESS Work      |
+--------------------------------------------------------------------+

Model	Full Name	You Manage	AWS Manages	AWS Examples
IaaS	Infrastructure as a Service	OS, Runtime, App, Data	Hardware, Networking, Virtualization	EC2, S3, VPC
PaaS	Platform as a Service	Application code, Data	OS, Runtime, Middleware, Infrastructure	Elastic Beanstalk, RDS, Lambda
SaaS	Software as a Service	Just use the app	Everything	Rekognition, WorkMail, Chime, Amazon Connect

Memory Aid for Service Models:

• IaaS = you get the land and tools, you build the house (MOST control, MOST work)
• PaaS = you get a house shell, you decorate inside (balanced control/work)
• SaaS = you move into a fully furnished hotel room (LEAST control, LEAST work)

Pizza as a Service Analogy:

+-----------------------------------------------------------------+
|                PIZZA AS A SERVICE ANALOGY                        |
+---------------+---------------+-------------+-------------------+
|  ON-PREMISES  |     IaaS      |    PaaS     |      SaaS         |
| (Make at Home)| (Take & Bake) | (Delivery)  | (Dine Out)        |
+---------------+---------------+-------------+-------------------+
| Make dough    | Dough provided| Pizza made  | Show up, eat      |
| Add sauce     | Add toppings  | You reheat  | They serve you    |
| Add toppings  | Bake it       | and serve   |                   |
| Bake it       |               |             |                   |
| Serve it      |               |             |                   |
+---------------+---------------+-------------+-------------------+
| YOU DO ALL    | YOU: Toppings | YOU: Plate  | YOU: Eat          |
|               |     + Bake    |     + Serve |                   |
+---------------+---------------+-------------+-------------------+

AWS Pricing: Three Pillars (Pay-as-you-go):

• Compute - charged per second or per hour of processing time (e.g., EC2, Lambda)
• Storage - charged per GB stored per month (e.g., S3, EBS)
• Data Transfer - data INTO AWS is free; data OUT of AWS to the internet incurs charges

Pricing Direction Visual:

     +----------------------------+
     |          AWS CLOUD         |
     |                            |
  -->| Data IN  = FREE            |
     |                            |
     | Data OUT = $$$$ (Egress)   |<--
     |                            |
     +----------------------------+
     
     INGRESS = FREE   |   EGRESS = PAID

Why Data Transfer Pricing Matters:

Architecting to minimize data leaving AWS (e.g., keeping compute and storage in the same region) directly reduces costs. This is why AWS encourages processing data where it's stored rather than downloading it.

Key Terms

Term	Definition
IaaS	Infrastructure as a Service -- you manage the OS and above; the cloud provider manages hardware, networking, and virtualization. Most control, most responsibility. Example: EC2.
PaaS	Platform as a Service -- you manage only your application and data; the provider manages everything else including the runtime and OS. Example: Elastic Beanstalk, RDS.
SaaS	Software as a Service -- a fully managed application delivered over the internet; the user just logs in and uses it. Least control, least responsibility. Example: Gmail, Salesforce, Amazon WorkMail.
Hybrid Cloud	An architecture combining on-premises infrastructure with public cloud resources, connected and orchestrated together.
Data Egress	Data leaving the cloud to the internet. AWS charges for egress but not for ingress (data coming in).
Data Ingress	Data entering the cloud from the internet. AWS does NOT charge for ingress -- uploading data to AWS is free.
AWS Outposts	AWS hardware and services deployed in your own data center. Enables a true hybrid cloud with consistent AWS APIs on-premises.
Direct Connect	A dedicated private network connection from your premises to AWS. Bypasses the public internet for consistent performance and added security.
Multi-Cloud	Using multiple cloud providers (e.g., AWS + Azure) for different workloads. Not the same as hybrid cloud.
FaaS (Function as a Service)	A subset of PaaS where you deploy individual functions that run in response to events. AWS Lambda is the primary example. Also called 'serverless compute.'

Practice Questions

AWS Cloud Overview

What is AWS?

Amazon Web Services is the world's largest and most widely adopted cloud platform, offering over 200 fully featured services from data centers globally. Launched in 2006, AWS pioneered the modern cloud industry and remains the market leader.

AWS Market Position:

• Launched 2006 (first major cloud provider)
• Market share: ~32% (largest)
• Over 200 services across compute, storage, database, AI/ML, IoT, and more
• Trusted by enterprises, startups, and government agencies worldwide

AWS Global Infrastructure -- Three Key Concepts:

AWS Global Infrastructure Hierarchy:

+-----------------------------------------------------------------+
|                    AWS GLOBAL INFRASTRUCTURE                    |
+-----------------------------------------------------------------+
                              |
         +--------------------+--------------------+
         v                    v                    v
+-----------------+  +-----------------+  +-----------------+
|   REGION 1      |  |   REGION 2      |  |   REGION 3      |
|  (us-east-1)    |  |  (eu-west-1)    |  |  (ap-south-1)   |
|   N. Virginia   |  |    Ireland      |  |     Mumbai      |
+--------+--------+  +-----------------+  +-----------------+
         |
    +----+----+------------+
    v         v            v
+-------+ +-------+   +-------+
|  AZ 1 | |  AZ 2 |   |  AZ 3 |   <-- Availability Zones
| (1a)  | | (1b)  |   | (1c)  |       (2-6 per Region)
+---+---+ +---+---+   +---+---+
    |         |           |
    v         v           v
  +---+     +---+       +---+
  |DC |     |DC |       |DC |      <-- Data Centers
  |DC |     |DC |       |DC |          (Multiple per AZ)
  +---+     +---+       +---+

+-----------------------------------------------------------------+
|                       EDGE LOCATIONS                            |
|              (400+ worldwide, for CloudFront CDN)               |
|  +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+  |
|  | E | | E | | E | | E | | E | | E | | E | | E | | E | | E |  |
|  +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +---+  |
|              More Edge Locations than Regions!                  |
+-----------------------------------------------------------------+

1. Regions

• A Region is a physically separate geographic area containing multiple data centers
• Currently 30+ Regions worldwide (and growing)
• Each Region is completely independent -- a failure in one does not affect others
• Services and data deployed in a Region stay in that Region unless you explicitly move them
• Examples: us-east-1 (N. Virginia), eu-west-1 (Ireland), ap-southeast-1 (Singapore)
• Naming convention: continent-direction-number (e.g., us-west-2 = US West, 2nd region)

How to Choose a Region (4 Factors -- Memorize!):

+----------------------------------------------------------------+
|            4 FACTORS FOR CHOOSING AN AWS REGION                |
+----------------------------------------------------------------+
|                                                                |
|  1. LATENCY (Proximity)                                        |
|     * Choose region closest to your users                      |
|     * Lower latency = faster response times                    |
|                                                                |
|  2. COMPLIANCE (Data Residency)                                |
|     * Some laws require data to stay in specific countries     |
|     * GDPR, HIPAA, government regulations                      |
|                                                                |
|  3. SERVICE AVAILABILITY                                       |
|     * Not all services exist in all regions                    |
|     * New services launch in us-east-1 first                   |
|                                                                |
|  4. PRICING                                                    |
|     * Prices vary slightly between regions                     |
|     * us-east-1 is often cheapest                              |
|                                                                |
+----------------------------------------------------------------+

2. Availability Zones (AZs)

• Each Region contains 2-6 AZs (usually 3)
• Each AZ is one or more discrete data centers with independent power, cooling, and networking
• AZs within a Region are connected via high-speed, low-latency private fiber links (<2ms latency)
• Deploying across multiple AZs = high availability and fault tolerance
• If one AZ goes down, your application keeps running from the others
• AZs are physically separate but close enough for synchronous replication

3. Edge Locations (Points of Presence)

• 400+ Edge Locations worldwide -- far more than Regions
• Used by Amazon CloudFront (CDN) to cache and deliver content closer to end users
• Reduces latency for global users by serving content from a nearby edge node
• Also used by Route 53 (DNS), AWS Shield, and AWS WAF
• Regional Edge Caches provide an additional caching layer between edge locations and origin

Global vs. Regional Services:

+-----------------------------------------------------------------+
|              GLOBAL vs REGIONAL SERVICES                        |
+------------------------+----------------------------------------+
|    GLOBAL SERVICES     |       REGIONAL SERVICES                |
|  (No region selection) |   (Must select a region)               |
+------------------------+----------------------------------------+
| * IAM                  | * EC2                                  |
| * Route 53 (DNS)       | * S3 (buckets are regional)            |
| * CloudFront (CDN)     | * RDS                                  |
| * WAF (can be global)  | * Lambda                               |
| * AWS Organizations    | * VPC                                  |
| * Billing Dashboard    | * DynamoDB                             |
|                        | * SageMaker                            |
+------------------------+----------------------------------------+
         Shows 'Global'             Shows region name
        in console header           in console header

AWS Service Categories (Key Ones for Exam):

• Compute: EC2, Lambda, ECS, EKS, Elastic Beanstalk, Fargate, Lightsail
• Storage: S3, EBS, EFS, FSx, Glacier, Storage Gateway
• Database: RDS, DynamoDB, ElastiCache, Aurora, Redshift, Neptune, DocumentDB
• Networking: VPC, Route 53, CloudFront, Direct Connect, API Gateway, Transit Gateway
• Security: IAM, KMS, Shield, WAF, GuardDuty, Inspector, Macie, Secrets Manager
• AI/ML: SageMaker, Rekognition, Comprehend, Bedrock, Polly, Transcribe, Lex, Textract

AI/ML Services Hierarchy:

+-----------------------------------------------------------------+
|               AWS AI/ML SERVICES STACK                          |
+-----------------------------------------------------------------+
|                                                                 |
|  +---------------------------------------------------------+   |
|  |  AI SERVICES (No ML expertise needed - just API calls)  |   |
|  |  Rekognition | Comprehend | Polly | Lex | Textract      |   |
|  |  Transcribe | Translate | Personalize | Forecast        |   |
|  +---------------------------------------------------------+   |
|                          ^                                      |
|  +---------------------------------------------------------+   |
|  |  ML SERVICES (Build/train custom models)                |   |
|  |  Amazon SageMaker | SageMaker Studio                    |   |
|  |  Built-in algorithms | Custom training                  |   |
|  +---------------------------------------------------------+   |
|                          ^                                      |
|  +---------------------------------------------------------+   |
|  |  ML FRAMEWORKS (Deep learning on EC2)                   |   |
|  |  TensorFlow | PyTorch | MXNet | Deep Learning AMIs      |   |
|  +---------------------------------------------------------+   |
|                          ^                                      |
|  +---------------------------------------------------------+   |
|  |  GENERATIVE AI (Foundation Models)                      |   |
|  |  Amazon Bedrock | Amazon Q | PartyRock                  |   |
|  |  Claude | Titan | Llama | Stable Diffusion              |   |
|  +---------------------------------------------------------+   |
|                                                                 |
|  HIGHER = Easier to use, less customization                    |
|  LOWER  = More control, more expertise required                |
+-----------------------------------------------------------------+

Key Terms

Term	Definition
Region	A geographically distinct area hosting multiple Availability Zones. Data in a Region stays in that Region unless explicitly moved. Currently 30+ worldwide.
Availability Zone (AZ)	One or more physically separate data centers within a Region, each with independent power and networking. Deploying across AZs enables high availability. 2-6 AZs per Region.
Edge Location	A site used by CloudFront and other services to cache content closer to end users, reducing latency. There are 400+ edge locations -- far more than Regions.
High Availability	System design that minimizes downtime by distributing resources across multiple AZs or Regions so that no single failure causes a full outage.
Fault Tolerance	The ability of a system to continue operating correctly even when one or more components fail.
CloudFront	AWS's Content Delivery Network (CDN). Uses edge locations to serve content from the location closest to the user.
Points of Presence (PoP)	The network of edge locations and Regional Edge Caches used by CloudFront, Route 53, and other global services.
Data Residency	Legal requirements specifying where data must be physically stored. A key factor when choosing AWS Regions.
Low Latency Links	High-speed, private fiber connections between AZs in the same Region. Typically <2ms latency, enabling synchronous replication.
Regional Edge Cache	A larger cache layer between edge locations and the origin server. Provides better cache hit ratios for less frequently accessed content.

Practice Questions

Creating an AWS Account

Account Creation Steps:

• Visit aws.amazon.com -> Create an AWS Account
• Enter a valid email address and create a root account password
• Provide contact details (name, address, phone number)
• Enter a valid credit/debit card -- AWS requires this even for free tier (charged only if you exceed limits)
• Complete phone identity verification
• Select a Support Plan -- choose Basic (free) for learning purposes

Account Setup Flow:

+-----------------------------------------------------------------+
|                  AWS ACCOUNT CREATION FLOW                      |
+-----------------------------------------------------------------+
                              |
     +------------------------+------------------------+
     v                        v                        v
+----------+           +----------+           +----------+
| 1. Email |---------->|2. Payment|---------->|3. Verify |
| + Password|           |   Info   |           |  Phone   |
+----------+           +----------+           +----------+
                              |
     +------------------------+------------------------+
     v                        v                        v
+----------+           +----------+           +----------+
|4. Support|---------->|5. Account|---------->|6. Secure |
|   Plan   |           | Activated|           | the Root |
+----------+           +----------+           +----------+
                                                    |
                                                    v
                                            Enable MFA!

The Root Account -- Handle With Extreme Care:

The root account is created with your email at sign-up. It has UNLIMITED access to everything in your AWS account with no restrictions.

• Never use the root account for everyday tasks
• Enable MFA (Multi-Factor Authentication) on the root account immediately after creation
• Store root credentials securely and use them only for account-level tasks
• Root tasks include: closing the account, changing billing info, changing support plan, restoring IAM permissions

Root Account Security Visual:

+-----------------------------------------------------------------+
|                    ROOT ACCOUNT RULES                           |
+-----------------------------------------------------------------+
|                                                                 |
|   [check] DO                           [x] DON'T                       |
|   --------------------           --------------------           |
|   * Enable MFA immediately       * Use for daily work          |
|   * Store creds securely         * Share credentials           |
|   * Create IAM admin user        * Create access keys          |
|   * Use only for root tasks      * Ignore the warnings         |
|                                                                 |
|   ROOT-ONLY TASKS:                                              |
|   * Close the account            * Change support plan          |
|   * Modify account settings      * View certain reports        |
|   * Restore IAM permissions      * Enable MFA for root         |
|                                                                 |
+-----------------------------------------------------------------+

AWS Free Tier -- Three Types:

Type	Duration	Example
12-Month Free	First 12 months only	750 hrs/month EC2 t2.micro, 5 GB S3
Always Free	Never expires	1M Lambda requests/month, 25 GB DynamoDB
Free Trials	Short-term trial	90-day free trial of Amazon Inspector

Free Tier Details:

+-----------------------------------------------------------------+
|                    AWS FREE TIER TYPES                          |
+-----------------------------------------------------------------+
|                                                                 |
|  12-MONTH FREE                   ALWAYS FREE                    |
|  (Expires after 1 year)          (Never expires)                |
|  --------------------            ----------------                |
|  * 750 hrs EC2 t2.micro          * 1M Lambda requests           |
|  * 5 GB S3 standard              * 25 GB DynamoDB               |
|  * 750 hrs RDS db.t2.micro       * 1M SNS requests              |
|  * 30 GB EBS storage             * 10 custom CloudWatch metrics |
|                                  * 25 GB SageMaker Studio Lab   |
|                                                                 |
|  FREE TRIALS                                                    |
|  (Short-term)                                                   |
|  ----------------                                               |
|  * 90-day Inspector trial                                       |
|  * 30-day GuardDuty trial                                       |
|  * 60-day Lightsail trial                                       |
|                                                                 |
+-----------------------------------------------------------------+

Post-Creation Security Best Practices:

• Enable MFA on root account -- use an authenticator app (Google Authenticator, Authy, Microsoft Authenticator)
• Create an IAM Admin user for daily use -- never log in as root routinely
• Set up a billing alarm in CloudWatch to alert you before charges accumulate
• Enable AWS Cost Explorer to monitor spending trends
• Review IAM Password Policy to enforce strong passwords for all users
• Enable AWS CloudTrail to log all API activity for auditing
• Consider enabling AWS Organizations for multi-account management

Security Setup Checklist:

+-----------------------------------------------------------------+
|         POST-CREATION SECURITY CHECKLIST                        |
+-----------------------------------------------------------------+
|                                                                 |
|  [ ] 1. Enable MFA on root account (FIRST PRIORITY!)            |
|  [ ] 2. Create IAM admin user with MFA                          |
|  [ ] 3. Set up billing alarm (CloudWatch)                       |
|  [ ] 4. Enable Cost Explorer                                    |
|  [ ] 5. Configure IAM password policy                           |
|  [ ] 6. Enable CloudTrail logging                               |
|  [ ] 7. Review and remove unused credentials                    |
|  [ ] 8. Set up AWS Budgets for cost control                     |
|                                                                 |
+-----------------------------------------------------------------+

Account Activation:

New accounts may take up to 24 hours to fully activate, particularly for phone verification. Email confirmation is immediate.

Support Plans Overview:

+------------------------------------------------------------------+
|                    AWS SUPPORT PLANS                             |
+--------------+--------------+---------------+-------------------+
|    BASIC     |  DEVELOPER   |   BUSINESS    |    ENTERPRISE     |
|    (Free)    |   ($29/mo)   | ($100/mo min) |  ($15,000/mo min) |
+--------------+--------------+---------------+-------------------+
| Docs, forums | Email support| 24/7 phone    | TAM assigned      |
| Trusted Adv  | 12-24hr resp | 1hr urgent    | 15min critical    |
| (7 checks)   | 1 contact    | Unlimited     | Concierge team    |
|              |              | contacts      | All TA checks     |
+--------------+--------------+---------------+-------------------+

Key Terms

Term	Definition
Root Account	The original AWS account created with your email address. Has unrestricted access to all AWS services and account settings. Should be protected with MFA and used sparingly.
MFA (Multi-Factor Authentication)	An extra layer of login security requiring a second factor (like a code from an authenticator app) in addition to a password. Can be virtual (app) or hardware (key fob).
IAM (Identity and Access Management)	AWS service for creating and managing users, groups, and roles with specific permissions. Use IAM users instead of root for day-to-day access.
AWS Free Tier	A set of AWS service allowances available at no charge, including 12-month free offers, always-free services, and short-term trials.
Billing Alarm	A CloudWatch alarm that notifies you when your estimated AWS charges exceed a threshold you set -- critical for avoiding surprise bills.
CloudTrail	AWS service that logs all API calls made in your account for security auditing, compliance, and troubleshooting. Records who did what, when, and from where.
AWS Organizations	Service for centrally managing multiple AWS accounts. Enables consolidated billing, service control policies, and organizational units.
Trusted Advisor	AWS service that provides real-time recommendations for cost optimization, security, fault tolerance, performance, and service limits.
AWS Budgets	Service for setting custom budgets and receiving alerts when costs or usage exceed thresholds. More flexible than basic billing alarms.
Technical Account Manager (TAM)	A dedicated AWS expert assigned to Enterprise Support customers who provides proactive guidance and advocacy.

Practice Questions

Tour of the Console & Services in AWS

AWS Management Console:

A browser-based graphical interface for managing all AWS services. It is the primary entry point for beginners before graduating to the CLI or SDK.

URL: console.aws.amazon.com

Console Layout -- Key Areas:

+-------------------------------------------------------------------------+
|  AWS    [Services v]    [Search] Search...              v Region   [*] Account |
+-------------------------------------------------------------------------+
|                                                                         |
|  [Star] Favorites: EC2 | S3 | Lambda | CloudWatch | IAM                     |
|                                                                         |
+---------------------------------------------------+---------------------+
|                                                   |                     |
|   RECENTLY VISITED                                |  AWS HEALTH         |
|   -----------------                               |  ------------       |
|   * Amazon EC2                                    |  All systems        |
|   * Amazon S3                                     |  operational [check]      |
|   * AWS Lambda                                    |                     |
|                                                   |                     |
|   BUILD A SOLUTION                                |  COST & USAGE       |
|   -----------------                               |  -------------      |
|   * Launch a VM                                   |  $XX.XX MTD        |
|   * Store files                                   |                     |
|   * Create a database                             |                     |
|                                                   |                     |
+---------------------------------------------------+---------------------+

Console Layout -- Key Areas:

• Top Navigation Bar - search bar, services menu, region selector, account menu, notifications
• Region Selector (top right) - sets which AWS region you're working in; CRITICAL to get right
• Search Bar - fastest way to find a service; also returns features, documentation, blog posts
• Services Menu (top left) - browse all 200+ services by name or by category
• Recently Visited - quick access to services you've used recently
• Home Dashboard - shows health status, cost and usage summary, and tutorials
• Favorites Bar - pin frequently used services for one-click access

Finding Services -- Three Ways:

• Search bar: type the service name (fastest method)
• Services menu: browse by category (Compute, Storage, Database, etc.)
• Favorites bar: pin frequently used services to the top nav bar

Region Selector -- Why It Matters:

+-----------------------------------------------------------------+
|                    REGION SELECTOR                              |
+-----------------------------------------------------------------+
|                                                                 |
|   +-----------------------------------------+                   |
|   | Current Region: US East (N. Virginia) v | <-- CHECK THIS!   |
|   +-----------------------------------------+                   |
|                                                                 |
|   COMMON MISTAKE:                                               |
|   "Where did my EC2 instance go?!"                              |
|   Answer: You're looking in the wrong region.                   |
|                                                                 |
|   REGIONAL SERVICES:          GLOBAL SERVICES:                  |
|   -----------------           ----------------                  |
|   * EC2 instances             * IAM                             |
|   * S3 buckets                * Route 53                        |
|   * RDS databases             * CloudFront                      |
|   * Lambda functions          * AWS Organizations               |
|   * VPCs                      * Billing                         |
|                                                                 |
|   Shows: "US East (N. Virginia)"   Shows: "Global"              |
|                                                                 |
+-----------------------------------------------------------------+

Region Selector -- Why It Matters:

• Most AWS services are regional -- resources created in one region do NOT appear in another
• Always confirm your region before creating resources
• Switching regions mid-session is a common source of confusion ('Where did my EC2 instance go?')
• Recommended: choose the region nearest to you for lowest latency during practice

Global vs. Regional Service Behavior in Console:

• Global services (IAM, Route 53, CloudFront) display 'Global' in the region selector -- no region choice needed
• Regional services (EC2, S3 console, RDS) display your current region -- different resources per region

Three Ways to Access AWS:

+-----------------------------------------------------------------+
|               THREE WAYS TO ACCESS AWS                          |
+-------------------+-------------------+-------------------------+
|      CONSOLE      |       CLI         |         SDK             |
|  (Web Browser)    |  (Command Line)   |   (Application Code)    |
+-------------------+-------------------+-------------------------+
|                   |                   |                         |
|  +-----------+    |  $ aws s3 ls     |  import boto3           |
|  | [*]? GUI    |    |  $ aws ec2 run..|  s3 = boto3.client('s3')|
|  | Point and |    |                   |  s3.list_buckets()      |
|  |   Click   |    |  Terminal/Shell   |                         |
|  +-----------+    |                   |  Python, Java, JS,      |
|                   |                   |  .NET, Go, Ruby...      |
|                   |                   |                         |
|  Best for:        |  Best for:        |  Best for:              |
|  * Learning       |  * Automation     |  * Applications         |
|  * Exploration    |  * Scripts        |  * Integration          |
|  * Ad-hoc tasks   |  * DevOps         |  * Custom tools         |
|                   |                   |                         |
+-------------------+-------------------+-------------------------+
                        |
                        v
            ALL USE THE SAME AWS APIs
           (Equal capability, different UX)

AWS CLI and SDK -- Beyond the Console:

• AWS CLI - command-line tool to interact with AWS services via terminal; great for automation
• Install on Windows, Mac, Linux
• Requires access keys (create in IAM)
• Example: aws s3 ls lists all your S3 buckets
• AWS SDKs - libraries for Python (boto3), Java, JavaScript, .NET, Go, Ruby, PHP, C++
• Embed AWS calls directly in application code
• Example: boto3.client('s3').list_buckets() in Python
• Both use the same underlying AWS APIs as the console -- equal power, different interfaces

AWS CloudShell:

• Browser-based shell environment pre-configured with AWS CLI
• No installation required -- access from the console
• 1 GB persistent storage per region
• Great for quick CLI operations without local setup

AWS Documentation and Support:

• docs.aws.amazon.com - official service documentation
• AWS Regional Services List - check which services are available in which region
• AWS Health Dashboard - check for service disruptions affecting your account
• AWS Knowledge Center - frequently asked questions and solutions
• re:Post - AWS community forum for questions and answers

Key Terms

Term	Definition
AWS Management Console	The web-based GUI for accessing and configuring AWS services. Beginner-friendly but less efficient than CLI for repetitive tasks.
AWS CLI (Command Line Interface)	A tool that lets you control AWS services through terminal commands. Useful for scripting and automation. Requires access keys for authentication.
AWS SDK	Software Development Kits for various programming languages that allow developers to call AWS APIs programmatically from application code.
AWS Region Selector	The dropdown in the top-right of the console that sets which geographic region your resources are created and viewed in.
AWS Health Dashboard	A console page showing the current status and any disruptions of AWS services globally and for your specific account.
AWS CloudShell	A browser-based terminal environment with AWS CLI pre-installed. Accessible from the console with no setup required.
Access Keys	Credentials (Access Key ID + Secret Access Key) used to authenticate programmatic access via CLI and SDKs. Never share or commit to code repositories.
AWS API	Application Programming Interface -- the underlying programmatic interface that all access methods (Console, CLI, SDK) use to interact with AWS services.
Resource Tags	Key-value pairs you attach to AWS resources for organization, cost allocation, and automation. Example: Environment=Production.

Practice Questions

Shared Responsibility Model & AWS Acceptable Use Policy

What is the Shared Responsibility Model?

A foundational AWS security framework that clearly divides who is accountable for what in a cloud environment. AWS secures the platform; you secure what you build on it.

The Core Principle:

• AWS = Security OF the Cloud (the physical and virtual infrastructure)
• Customer = Security IN the Cloud (what you deploy and configure)

Shared Responsibility Model Diagram:

+-----------------------------------------------------------------+
|            AWS SHARED RESPONSIBILITY MODEL                      |
+-----------------------------------------------------------------+
|                                                                 |
|  +-----------------------------------------------------------+  |
|  |            CUSTOMER RESPONSIBILITY                        |  |
|  |          "Security IN the Cloud"                          |  |
|  |                                                           |  |
|  |  +-----------------------------------------------------+  |  |
|  |  | Customer Data                                       |  |  |
|  |  +-----------------------------------------------------+  |  |
|  |  | Platform, Applications, Identity & Access (IAM)     |  |  |
|  |  +-----------------------------------------------------+  |  |
|  |  | Operating System, Network & Firewall Configuration  |  |  |
|  |  +-----------------------------------------------------+  |  |
|  |  | Client-Side Encryption | Server-Side Encryption     |  |  |
|  |  | Network Traffic Protection                          |  |  |
|  |  +-----------------------------------------------------+  |  |
|  +-----------------------------------------------------------+  |
|                          |                                      |
|                          v                                      |
|  +-----------------------------------------------------------+  |
|  |              AWS RESPONSIBILITY                           |  |
|  |           "Security OF the Cloud"                         |  |
|  |                                                           |  |
|  |  +-----------------------------------------------------+  |  |
|  |  | Software: Compute, Storage, Database, Networking    |  |  |
|  |  +-----------------------------------------------------+  |  |
|  |  | Hardware/AWS Global Infrastructure                  |  |  |
|  |  | Regions, Availability Zones, Edge Locations         |  |  |
|  |  +-----------------------------------------------------+  |  |
|  |  | Physical Security: Guards, Biometrics, Cameras      |  |  |
|  |  +-----------------------------------------------------+  |  |
|  +-----------------------------------------------------------+  |
|                                                                 |
+-----------------------------------------------------------------+

AWS Responsibilities (Security OF the Cloud):

• Physical security of all global data centers (guards, biometrics, surveillance, 24/7 monitoring)
• Hardware lifecycle management (servers, networking equipment, storage devices)
• Global network infrastructure and its protection (fiber, networking, DDoS mitigation)
• Hypervisor and virtualization layer security
• Managed service software (e.g., the database engine in RDS, the runtime in Lambda)
• Compliance certifications for the underlying infrastructure (SOC, ISO, PCI DSS at the hardware level)
• Decommissioning of hardware (secure disk wiping/destruction)

Customer Responsibilities (Security IN the Cloud):

• Data classification, encryption of data at rest and in transit
• IAM -- who has access to what (users, roles, permissions, MFA)
• Operating system patching and updates (for EC2/IaaS -- you own the OS)
• Application-level security and code vulnerabilities
• Network and firewall configuration (Security Groups, NACLs, VPC settings)
• Client-side encryption and authentication
• Logging and monitoring setup (CloudTrail, CloudWatch Logs)

Responsibility by Service Type:

+-----------------------------------------------------------------+
|        RESPONSIBILITY SHIFTS BY SERVICE MODEL                   |
+---------------------------------------------------------------+ |
|                                                               | |
|     IaaS (EC2)           PaaS (RDS/Lambda)      SaaS          | |
|   +---------------+    +---------------+    +---------------+ | |
|   | Customer Data |    | Customer Data |    | Customer Data | | |
| C |---------------|  C |---------------|  C |---------------| | |
| U | Application   |  U | Application   |    |###############| | |
| S |---------------|  S |---------------|  A |###Application#| | |
| T | OS Patching   |  T |###############|  W |###############| | |
| O |---------------|    |#OS Patching###|  S |##OS Patching##| | |
| M | Runtime Config|  A |###############|    |###############| | |
| E |---------------|  W |#Runtime#######|    |##Runtime######| | |
| R |###############|  S |###############|    |###############| | |
|   |# Hardware ####|    |##Hardware#####|    |###Hardware####| | |
| A |###############|    |###############|    |###############| | |
| W |#Data Centers##|    |#Data Centers##|    |#Data Centers##| | |
| S |###############|    |###############|    |###############| | |
|   +---------------+    +---------------+    +---------------+ | |
|                                                               | |
|   ### = AWS manages     Blank = Customer manages              | |
|                                                               | |
|   MORE MANAGED SERVICE ----------------------> LESS CUSTOMER  | |
|                                                  RESPONSIBILITY| |
+---------------------------------------------------------------+ |

How Responsibility Shifts by Service Model:

Layer	IaaS (EC2)	PaaS (Elastic Beanstalk/RDS)	SaaS (Rekognition)
Physical infrastructure	AWS	AWS	AWS
Hypervisor / Virtualization	AWS	AWS	AWS
Operating System	Customer	AWS	AWS
Runtime / Middleware	Customer	AWS	AWS
Application Code	Customer	Customer	AWS
Data	Customer	Customer	Customer

Key Insight: The more managed the service, the more AWS takes responsibility. With SaaS, AWS manages almost everything except your data.

Common Exam Scenarios:

+-----------------------------------------------------------------+
|              WHO IS RESPONSIBLE? (EXAM SCENARIOS)               |
+-----------------------------------------------------------------+
|                                                                 |
|  SCENARIO                              | RESPONSIBLE            |
|  ------------------------------------  | ------------           |
|  Patching EC2 instance OS              | CUSTOMER               |
|  Patching RDS database engine          | AWS                    |
|  Physical security of data center      | AWS                    |
|  Configuring Security Groups           | CUSTOMER               |
|  Enabling S3 encryption                | CUSTOMER               |
|  Providing encryption option in S3     | AWS                    |
|  Managing the hypervisor               | AWS                    |
|  Setting up IAM users and permissions  | CUSTOMER               |
|  Protecting networking infrastructure  | AWS                    |
|  Application-level firewall rules      | CUSTOMER               |
|  Hardware decommissioning/wiping       | AWS                    |
|  Compliance of physical infrastructure | AWS                    |
|  Compliance of customer workloads      | CUSTOMER               |
|                                                                 |
+-----------------------------------------------------------------+

AWS Acceptable Use Policy (AUP):

All AWS users agree to the AUP by creating an account. Prohibited activities include:

• Illegal content, services, or activities
• Security attacks (port scanning, DDoS, unauthorized access attempts)
• Network abuse (spam, phishing, email harvesting)
• Distributing malware or harmful code
• Mining cryptocurrency in violation of AWS terms
• Penetration testing without prior approval (approval required for certain tests)

Violation Consequences:

• Warning or account suspension
• Termination of services
• Legal action in severe cases

Penetration Testing Policy:

• AWS permits certain penetration testing without prior approval (for services you own)
• Permitted: EC2, RDS, CloudFront, API Gateway, Lambda, Lightsail, Elastic Beanstalk
• Prohibited without approval: DNS zone walking, DDoS simulation, port/protocol flooding
• Always check the latest AWS Customer Support Policy for Penetration Testing

Key Terms

Term	Definition
Shared Responsibility Model	AWS's framework dividing security duties: AWS secures the cloud infrastructure; customers secure their data and configurations within it.
Security OF the Cloud	AWS's portion of responsibility -- physical facilities, hardware, global network, hypervisor, and managed service software layers.
Security IN the Cloud	The customer's portion -- data, identity management, OS configuration, application security, network settings, and encryption.
Security Group	A virtual firewall at the instance level in AWS that controls inbound and outbound traffic. This is the customer's responsibility to configure.
Encryption at Rest	Encrypting data while it is stored (e.g., in S3 or EBS). The customer chooses whether to enable this -- it is their responsibility.
Acceptable Use Policy (AUP)	AWS's terms governing legal and ethical use of its services. Users agree to this on account creation. Violations can result in account suspension.
NACL (Network Access Control List)	A firewall at the subnet level in a VPC. Stateless rules that control traffic in and out of subnets. Customer's responsibility to configure.
Encryption in Transit	Encrypting data while it moves across networks (e.g., HTTPS, TLS). Customer's responsibility to implement using AWS-provided tools.
Compliance	AWS provides compliance certifications for infrastructure (SOC, ISO, PCI). Customers are responsible for their own workload compliance on top of AWS.
Penetration Testing	Security testing of your AWS resources. Permitted for certain services without approval, but DDoS simulation and some tests require prior authorization.

Practice Questions

AWS AI Practitioner - Table of Contents

Master all exam topics with comprehensive study guides and practice questions.

AWS AI Practitioner - Practice Tests Real Time Practice Tests AWS AI Practitioner Preparation Topics Cover all exam domains Introduction to AWS & Cloud Computing AWS basics, cloud models, pricing Amazon Bedrock and Generative AI Foundation Models, Bedrock, GenAI Prompt Engineering Prompt techniques, optimization Amazon Q - Deep Dive Q Business, Q Developer, Q Apps AI & Machine Learning Fundamentals AI/ML hierarchy, training, learning types AWS Managed AI Services Comprehend, Translate, Transcribe, more Amazon SageMaker - Deep Dive End-to-end ML platform deep dive AI Challenges and Responsibilities Responsible AI, bias, governance AWS Security Services IAM, S3, encryption, compliance