AWS Full Course 2025 | AWS Training | AWS Tutorial for Beginners | Intellipaat

Main ideas & lessons from the subtitles

1) Why AWS / cloud matters

• Modern apps (e.g., Netflix, Zomato, Amazon, Swiggy, etc.) handle massive scale without crashing by using cloud computing.
• AWS (Amazon Web Services) is positioned as the core platform powering a large share of the global cloud market.
• AWS is presented as an engine for businesses worldwide and a major source of career opportunities in India (cloud engineer, solutions architect, DevOps, security, machine learning roles).
• The roadmap emphasizes mastering AWS in a practical, job-ready order—not memorizing every service.

2) AWS Full Course roadmap (a “no BS” 7-step path)

Step 1: Core technical skills (2–3 weeks)

• Learn Linux commands (most AWS workloads run on Linux).
• Learn networking fundamentals:
  • IPs, DNS, request/response cycles, security groups
• Learn basic Python for scripting/automation.
• Learn virtualization (foundation of cloud).
• Goal: make AWS troubleshooting and interviews easier.

Step 2: Cloud & AWS fundamentals (2–3 weeks)

• Understand what cloud computing is and why companies use it:
  • cost savings, scalability, speed
• Learn cloud basics:
  • virtualization in the cloud
  • cloud types: public, private, hybrid
  • service models: IaaS, PaaS, SaaS
• Learn AWS infrastructure concepts:
  • regions, availability zones, edge locations
• Set up an AWS free tier account, explore the AWS console, dashboards (e.g., EC2, S3, IAM), and understand account vocabulary.

Step 3: Core AWS service domains (Compute, Storage, Networking, Security) (4–5 weeks)

• The “four pillars”:

  • Compute: execution engine (EC2, Lambda, ECS, EKS, Elastic Beanstalk)
  • Storage: file/data storage (S3, EBS, EFS, S3 Glacier, etc.)
  • Networking: connectivity + delivery (VPC, subnets, security groups, Route 53, CloudFront)
  • Security: IAM roles, encryption, logging, threat detection (IAM, KMS, CloudTrail, GuardDuty, Security Hub), plus shared responsibility model and Well-Architected Framework

• Example project ideas:

  • Deploy a blog app on EC2 with files in S3
  • Build security practices using IAM roles, KMS encryption, CloudTrail monitoring
• Goal: understand what each service does and how they interact.

Step 4: Databases & Serverless architectures (2–3 weeks)

• Learn:
  • RDS (relational SQL databases)
  • DynamoDB (NoSQL)
  • Lambda + API Gateway for serverless compute
• Example project:
  • A serverless photo uploader using Lambda, API Gateway, S3, and DynamoDB.
• Certifications preparation:
  • ready for Cloud Practitioner
  • optionally start Solutions Architect Associate / Developer Associate depending on focus

Step 5: Infrastructure as Code & monitoring (DevOps thinking)

• Learn CloudFormation:
  • define infrastructure as templates
  • recreate infrastructure anywhere
• Learn CloudWatch:
  • monitor metrics, logs, alarms
• Learn AWS Config:
  • compliance tracking
• Example practice:
  • automate an application setup with CloudFormation
  • monitor via CloudWatch alarms

Step 6: Advanced architectures & CI/CD

• Learn multi-tier / production-grade architecture concepts.
• Learn CI/CD pipelines using:
  • CodePipeline, CodeBuild, CodeDeploy
• Learn hybrid setups:
  • connect on-premise systems to AWS
• Example project:
  • deploy a three-tier web app fully automated with CI/CD
• Goal: position for solutions architect & DevOps engineer certifications and readiness.

Step 7: Specialization paths

• Choose based on interest:
  • DevOps automation → DevOps path
  • Security → Security specialization
  • Data analytics → data analytics roles
  • AI → Machine Learning specialty certification

3) Practical beginner fundamentals shown (EC2, S3, RDS, IAM, networking, etc.)

A) AWS account & console navigation

• AWS free tier credit changes are mentioned:
  • free tier duration described as shorter, plus $1000 credits and possible extra credits
• Console overview:
  • services by category (compute, storage, security/identity, networking, analytics, etc.)
• Region importance:
  • resources are created within a region
  • switching regions can cause confusion and unexpected costs
  • tracking via billing and cost management is recommended

B) Billing control with Budgets

• Method described to create a budget alert:
  1. Billing & Cost Management → Budgets → Create budget
  2. Choose a cost budget type (recommended)
  3. Customize budget (example: “zero budget” style)
  4. Set period to monthly / recurring
  5. Add alert threshold (example triggers when actual cost exceeds budget)
  6. Add notification email
  7. Review and create

C) IAM basics (Users, Groups, Roles)

• IAM is explained as the system for:
  • authentication (who you are)
  • authorization (what you can do)
• Key IAM concepts:
  • Default behavior: IAM denies everything unless explicitly allowed (explicit allow model)
  • Users: individual identities
  • Groups: sets of users with shared permissions
  • Policies: JSON documents defining allowed/denied actions
  • Roles: temporary permissions assigned to AWS resources/users/services
  • MFA recommended:
    • add MFA device (authenticator app / hardware token)
    • login requires password + OTP
• Practical flow demonstrated:
  • create IAM user and group
  • attach policies like EC2 full access / VPC full access
  • create roles for EC2 to access S3 using IAM role permissions

D) EC2 fundamentals (launch instance, connect, host a website)

• EC2 presented as compute offering:
  • instance types (CPU/memory/storage/network)
  • AMI selection (OS templates)
  • key pairs for SSH/RDP access
  • security groups to open needed ports
• Example:
  • Launch a Linux EC2 instance
  • Install Apache (httpd) using commands
  • Enable and verify service status
  • Create an index page and verify in browser using public IP
• Reminder: terminate instances after practice to avoid ongoing cost.

E) S3 fundamentals (static website hosting)

• S3 described as object storage:
  • stores files/assets/backups
  • can host static websites
• Practical steps shown for hosting a static site:
  • Create bucket (bucket name must be lowercase / unique)
  • Ensure public access settings appropriate for website hosting
  • Enable bucket versioning
  • Choose server-side encryption options (S3-managed keys or KMS)
  • Upload static website files (index.html, CSS/JS assets, images)
  • Enable static website hosting in bucket properties:
    • index document = index.html
  • Update bucket policy to allow public read access
  • Verify website loads via S3 website endpoint
• Versioning concept shown:
  • previous uploads remain accessible even after deletion (delete markers)

F) RDS fundamentals (managed relational DB)

• RDS used when you don’t want to manage database installation/backups/scaling manually on EC2.
• Practical RDS flow:
  • create RDS instance
  • choose engine (example MySQL)
  • set instance settings (free tier/testing templates)
  • create credentials (master username/password)
  • choose storage and connectivity settings
  • connect to EC2 via networking/security group where required
• Emphasis:
  • use endpoint for connectivity
  • default database ports mentioned for interview relevance (e.g., MySQL)

4) Networking concepts taught (Region/AZ, Subnets, Route Tables, IGW, NAT, Peering)

A) Regions and Availability Zones

• Region = geographic grouping of AWS data centers.
• Availability Zones (AZs) = multiple isolated data centers within a region.
• Fault tolerance idea:
  • if one AZ fails, other AZs can keep service running
• Low-latency reasoning:
  • choose region closest to customers

B) Subnets

• Subnet = smaller IP range inside a VPC, aligned to a specific AZ.
• Public vs private subnets:
  • public subnet gets public access via internet gateway routing
  • private subnet does not directly reach the internet gateway
• CIDR/IP math concept taught:
  • how prefix length affects number of IPs
  • AWS reserves 5 IPs in each subnet (network address, router, DNS, reserved, broadcast)
• Converting private subnet to public behavior:
  • enable “auto-assign public IPv4” on the subnet

C) Internet Gateway, NAT Gateway, Route tables

• Internet Gateway (IGW):
  • allows public subnets to access the internet
  • must be added via route table entry: 0.0.0.0/0 → IGW
• NAT Gateway:
  • lets private subnets access internet without making them public
  • alternative path for outbound access from private networks
• Route tables:
  • contain destination/target rules
  • associated with subnets; router uses route table to forward traffic

D) VPC peering

• Peering connects two VPCs with private connectivity.
• Requirements emphasized:
  • VPCs must be in compatible conditions (e.g., non-overlapping CIDR)
  • overlapping CIDR leads to “overlapping IP” errors
• After peering creation:
  • update route tables in each VPC to point traffic to the other VPC via peering connection ID
• Scaling warning:
  • peering count grows rapidly with number of VPCs → complex beyond small setups

5) Load balancing, autoscaling, CI/CD, and DevOps concepts (covered in subtitles)

• Load balancers:
  • described conceptually and types (ALB/NLB/GLB; CLB deprecated)
  • target groups used for health checks and routing
• Autoscaling group:
  • scales EC2 instances based on load (add/remove servers)
  • uses launch templates to define instance configuration
  • includes min/desired/max capacity and placement across AZs
  • dependency on other services (e.g., load balancer, monitoring)
• CI/CD:
  • CodePipeline/CodeBuild/CodeDeploy mentioned as pipeline components

6) Building an AWS portfolio with S3 + GitHub Actions CI/CD (project walkthrough)

Architecture / flow (concept)

• User pushes updates to GitHub repository → GitHub Actions workflow triggers.
• Workflow syncs website files to an AWS S3 bucket.
• S3 hosts the static portfolio site.
• Changes appear on the live portfolio automatically (no manual uploads).

Detailed step-by-step workflow (as described)

Frontend / repo setup

• Create a GitHub repo (with README).
• Upload portfolio website folder contents (HTML/CSS/JS/assets).
• Commit changes.

Add GitHub Actions workflow

• Create a workflow YAML file.
• Ensure source directory name in workflow matches the uploaded folder name.
• Trigger on pushes to the main branch.
• Jobs/steps include:
  • checkout repository
  • sync website files to S3 using an S3 sync action
  • set ACL public-read (so site assets are accessible)
  • remove obsolete files from S3 when they no longer exist in GitHub
  • use environment variables / secrets for AWS authentication

AWS setup

• Create an S3 bucket for the portfolio.
• Configure:
  • public access settings (block public access off as required)
  • versioning enabled
  • static website hosting (index document index.html)

IAM setup for GitHub Actions

• Create an IAM user (e.g., I GitHub) with S3 access.
• Generate access key + secret access key.

GitHub secrets

• Add repository secrets in GitHub Actions:
  • bucket name
  • AWS access key ID
  • AWS secret access key

Bucket policy

• Generate and set a bucket policy allowing the IAM principal actions needed (public read for site assets as required).

Verify

• Confirm portfolio loads via the S3 website endpoint.
• Push a change to GitHub and confirm GitHub Actions redeploys and the site updates automatically.

---

Speakers / sources featured

• Intellipaat / Intellipath (course source/brand) — referenced throughout as the video/course provider.
• AWS (Amazon Web Services) — referenced as the platform, documentation, and services provider.
• “Industry expert trainers” — mentioned as guiding viewers later in the course (no individual name given).
• No named individuals/speakers (subtitles do not provide a clear person’s name).