Curriculum Overview: Strategic AWS Service Selection for Business Needs

This curriculum is designed to equip Cloud Practitioners with the decision-making framework required to map business requirements to the correct Amazon Web Services (AWS) solutions. It covers business applications, integration services, and developer tools as defined in the CLF-C02 exam guide.

Prerequisites

Before engaging with this module, students should possess:

• Cloud Fundamentals: Understanding of cloud computing deployment models (Public, Private, Hybrid).
• AWS Shared Responsibility Model: Knowledge of what AWS manages versus what the customer manages.
• Basic Infrastructure Concepts: Familiarity with virtual machines (EC2) and storage (S3).
• The Well-Architected Framework: A high-level understanding of the six pillars, specifically Reliability and Operational Excellence.

Module Breakdown

Visual Selection Logic

Module Objectives per Module

MOD 01: Business Applications

• Objective: Identify tools for customer engagement and mass communication.
• Key Learning: Distinguishing between Amazon Connect (Cloud contact center) and Amazon SES (Bulk email service).

MOD 02: Application Integration

• Objective: Understand how to decouple services for higher reliability.
• Key Learning: Mastering the difference between 'Push' (SNS) and 'Poll' (SQS) architectures.

[!IMPORTANT] Application integration is the key to achieving the Reliability Pillar by ensuring that failure in one component does not crash the entire system.

MOD 03: Managed Database Selection

• Objective: Choose the correct data model based on application architecture.
• Key Learning: Relational (RDS/Aurora) vs. Non-Relational (DynamoDB).

Comparison: Integration Services

Technical Architecture (TikZ)

Success Metrics

To master this curriculum, a student must be able to:

1. Differentiate between SQS and SNS in a scenario-based question (e.g., "Which service ensures messages are stored until processed?").
2. Calculate high-level cost benefits of managed services using the logic: $Total\ Cost = Service\ Fee + (Operational\ Overhead \times \text{Reduction\ Factor})$
3. Identify the correct support resource (e.g., AWS Support vs. AWS IQ) for various business sizes.
4. Select a developer tool based on the stage of the CI/CD pipeline (Build vs. Deploy).

Real-World Application

In a professional setting, these skills allow a Cloud Practitioner to assist in Cloud Financial Management. By choosing a serverless, managed service like Amazon SES instead of hosting a custom mail server on EC2, a business reduces its administrative burden ($Admin_{cost} \to 0$) and improves its scalability automatically.

Examples Section

▶Click to view: Scenario-Based Selection Examples

Scenario 1: The Newsletter

• Need: A marketing firm needs to send 10,000 emails a day to customers.
• Solution: Amazon SES. It is designed specifically for high-volume email sending with high deliverability.

Scenario 2: The Flash Sale

• Need: An e-commerce site experiences spikes in traffic that crash the database. They need a way to buffer incoming orders.
• Solution: Amazon SQS. By placing orders in a queue, the database can process them at its own pace without failing.

Scenario 3: The Global Support Team

• Need: A startup needs a call center that allows agents to work from home globally.
• Solution: Amazon Connect. It provides a virtual cloud-based contact center that can be set up in minutes.