Step 1: Access AWS Portal

1. Go to aws.amazon.com
2. Click “Create an AWS Account” in the top right
3. Select “Create a new AWS account”

Step 2: Account Information

1. Enter your email address (which will serve as the identifier)
2. Choose a unique AWS account name
3. Create a secure password (12 characters minimum)
4. Confirm your password
5. Click “Continue”

Step 3: Contact Information

1. Select account type (Business or Personal)
2. Fill in your complete information:
   • Full name or company name
   • Complete postal address
   • Phone number with country code
3. Accept AWS terms of service
4. Click “Create account and continue”

Step 4: Payment Information

1. Enter your credit/debit card details
2. Fill in billing address (if different)
3. Click “Verify and add”

Step 5: Identity Verification

1. Choose verification method (SMS or voice call)
2. Enter your phone number
3. Enter the displayed captcha
4. Click “Send SMS” or “Call me now”
5. Enter the 4-digit verification code received
6. Click “Verify code and continue”

Step 6: Support Plan Selection

AWS offers several support plans:

• Basic (Free): Documentation and community forums
• Developer ($29/month): Technical support via email
• Business ($100/month minimum): 24/7 phone and chat support
• Enterprise ($15,000/month minimum): Dedicated support with TAM

To get started, select the “Basic” plan (free)

Multi-Factor Authentication (MFA) Setup

1. Log in to AWS Console
2. Click on your username in the top right
3. Select “My Security Credentials”
4. In the “Multi-factor authentication” section, click “Assign MFA device”
5. Choose device type:
   • Authenticator app (Google Authenticator, Authy)
   • U2F security key
   • Hardware MFA device
6. Follow instructions to configure your device
7. Test authentication with two consecutive codes

Launching Your First EC2 Instance

Step 1: Access EC2 Service

1. In AWS Console, search for “EC2” in the search bar
2. Click “EC2” under “Compute services”
3. Verify the selected region in the top right
4. Click “Launch instance”

Step 2: Instance Configuration

1. Name and tags:
   • Name: “My-First-Web-Server”
   • Add organizational tags (Environment: Production, Owner: Your-Name)
2. Application and OS Images:
   • Select “Amazon Linux 2023” (recommended for beginners)
   • Architecture: x86_64
   • Verify “Free tier eligible” is indicated
3. Instance type:
   • Select “t3.micro” (1 vCPU, 1 GB RAM)
   • This size is included in the free tier

Step 3: Key Pair Configuration

1. Click “Create new key pair”
2. Key pair name: “my-first-key”
3. Key pair type: RSA
4. Private key file format:
   • .pem for Linux/macOS
   • .ppk for Windows (PuTTY)
5. Click “Create key pair”
6. Download and securely save the private key file

Step 4: Network Configuration

1. Create a security group or use the default one
2. Security group name: “web-server-sg”
3. Description: “Security group for web server”
4. Inbound traffic rules:
   • SSH (port 22): Your IP only
   • HTTP (port 80): Everywhere (0.0.0.0/0)
   • HTTPS (port 443): Everywhere (0.0.0.0/0)

Step 5: Storage Configuration

1. Root volume size: 8 GB (free tier maximum)
2. Volume type: gp3 (General Purpose SSD)
3. Encryption: Enabled (recommended)
4. Delete on termination: Checked (to avoid costs)

Creating Your First S3 Bucket

Step 1: Access S3 Service

1. In AWS Console, search for “S3”
2. Click “S3” under “Storage services”
3. Click “Create bucket”

Step 2: General Configuration

1. Bucket name:
   • Must be globally unique
   • Example: “my-website-2024-your-name”
   • Use only lowercase letters, numbers, and hyphens
2. AWS Region:
   • Choose the region closest to your users
   • Europe (Paris) eu-west-3 for France
   • US East (N. Virginia) us-east-1 for United States

Step 3: Object Ownership Configuration

1. Object ownership: “ACLs disabled (recommended)”
2. This option simplifies permissions management

Step 4: Public Access Settings

1. Block all public access: Checked by default (secure)
2. For a static website, uncheck this option later

Step 5: Versioning and Encryption

1. Versioning: Enabled (recommended for backup)
2. Default encryption:
   • Encryption type: SSE-S3
   • Bucket key type: Disabled (to reduce costs)

Creating an RDS Database

Step 1: Access RDS Service

1. Search for “RDS” in AWS Console
2. Click “RDS” under “Database”
3. Click “Create database”

Step 2: Database Engine Selection

1. Creation method: “Standard create”
2. Engine options:
   • MySQL: Most popular, free tier available
   • PostgreSQL: Advanced features
   • MariaDB: MySQL alternative
3. Version: Use default version (latest stable)

Step 3: Templates and Settings

1. Templates: “Free tier” (to get started)
2. Settings:
   • DB instance identifier: “my-first-db”
   • Master username: “admin”
   • Master password: Auto-generated or custom

Step 4: Instance Configuration

1. DB instance classes: db.t3.micro (free tier)
2. Storage:
   • Storage type: General Purpose SSD (gp2)
   • Allocated storage: 20 GB (free tier maximum)
   • Storage autoscaling: Disabled

Creating Your First Lambda Function

Step 1: Function Creation

1. Search for “Lambda” in AWS Console
2. Click “Create function”
3. Select “Author from scratch”
4. Function name: “my-first-function”
5. Runtime: Python 3.11 (recommended for beginners)
6. Architecture: x86_64

Step 2: Permissions Configuration

1. Execution role: “Create a new role with basic Lambda permissions”
2. AWS will automatically create an IAM role with minimal permissions

Step 3: Simple Test Code

1. In the code editor, replace the content with:


import json

def lambda_handler(event, context):
return {
‘statusCode’: 200,
‘body’: json.dumps(‘Hello from AWS Lambda!’)
}

IAM User Configuration

1. User creation:
   • Access IAM service in the console
   • Click “Users” then “Add users”
   • Username: follow a convention (firstname.lastname)
   • Access type: Console and/or programmatic access
2. Permission assignment:
   • Use groups rather than direct policies
   • Apply the principle of least privilege
   • Create custom policies if necessary
3. MFA configuration:
   • Enable MFA for all users
   • Use mobile authenticator applications
   • Configure policies requiring MFA

AWS Budget Configuration

1. Budget Access:
   • Search for “Budgets” in AWS Console
   • Click “Create budget”
2. Budget Type:
   • Cost budget: To control total spending
   • Usage budget: To monitor service usage
   • Reservation budget: To optimize reserved instances
3. Alert Configuration:
   • Threshold 1: 50% of budget (preventive alert)
   • Threshold 2: 80% of budget (major alert)
   • Threshold 3: 100% of budget (critical alert)
   • Threshold 4: 120% of budget (overspending)

Complete Monitoring Setup

Essential Metrics to Monitor

Automated Alarm Configuration

1. Access CloudWatch service
2. Click “Alarms” then “Create alarm”
3. Select the metric to monitor
4. Define threshold and period
5. Configure actions (SNS, Auto Scaling, EC2)

Automated Server Maintenance

1. Patch Manager:
   • Patch group configuration
   • Automatic update scheduling
   • Defined maintenance windows
2. Session Manager:
   • Secure instance access without SSH
   • Complete audit logs
   • No need for bastion hosts
3. Run Command:
   • Remote script execution
   • Application deployment
   • System information collection

Multi-Region Strategies

Global Architecture

1. Primary region: Close to main users
2. Secondary region: Disaster recovery and compliance
3. Edge locations: CloudFront for global performance
4. Route 53: Intelligent routing based on geolocation

Example: Global E-commerce

• North America: us-east-1 (Virginia) – Primary region
• Europe: eu-west-1 (Ireland) – GDPR compliance
• Asia-Pacific: ap-southeast-1 (Singapore) – Growth
• CDN: Global CloudFront with edge locations

EC2 Instance Inaccessible

Step-by-Step Diagnosis

1. Status verification:
   • EC2 Console → Instances → Status Checks
   • System Status Check: AWS issue
   • Instance Status Check: OS issue
2. Security group:
   • Check SSH inbound rules (port 22)
   • Source: Your current public IP
   • Protocol: TCP
3. Network ACL:
   • Check subnet rules
   • Default allows everything
   • Explicit deny rules take priority
4. Route Table:
   • Check route to Internet Gateway
   • 0.0.0.0/0 → igw-xxxxxxxx

Common Solutions

• Missing public IP: Associate an Elastic IP
• Incorrect SSH key: Use EC2 Instance Connect
• OS firewall: Access via Session Manager

Recommended Certification Path

Foundation Level

1. AWS Cloud Practitioner (CLF-C01):
   • Preparation time: 2-3 months
   • Prerequisites: None
   • Cost: 100 USD
   • Validity: 3 years

Associate Level

1. Solutions Architect Associate (SAA-C03):
   • Duration: 4-6 months practical experience
   • Focus: Architecture and design
   • Cost: 150 USD
2. Developer Associate (DVA-C01):
   • Focus: Development and deployment
   • Skills: SDK, API, CI/CD
3. SysOps Administrator Associate (SOA-C02):
   • Focus: Operations and monitoring
   • Skills: Maintenance, troubleshooting

Recommended Next Steps

1. Immediate Actions (Week 1-2):
   • Set up your AWS account with all security measures
   • Create your first EC2 instance and S3 bucket
   • Configure billing alerts and budgets
   • Complete AWS Cloud Practitioner learning path
2. Short-term Goals (Month 1-3):
   • Deploy a complete 3-tier web application
   • Implement CI/CD pipeline with AWS CodePipeline
   • Set up comprehensive monitoring and alerting
   • Practice disaster recovery procedures
3. Long-term Objectives (3-12 months):
   • Achieve AWS Solutions Architect certification
   • Implement multi-region architecture
   • Explore advanced services (ML, IoT, Analytics)
   • Optimize costs through automation and governance