Curriculum Overview: One-Time Operations vs. Repeatable Processes in AWS

This curriculum focuses on the strategic decision-making process required to manage cloud infrastructure effectively. It explores the trade-offs between manual execution (one-time operations) and automated workflows (repeatable processes), a core competency for the AWS Certified Cloud Practitioner.

Prerequisites

Before starting this module, students should have a baseline understanding of the following:

• Cloud Fundamentals: Basic understanding of what cloud computing is (on-demand delivery, pay-as-you-go).
• AWS Management Basics: Familiarity with the existence of the AWS Management Console.
• Core Infrastructure Concepts: General awareness of what a server (EC2) and a database are.

Module Breakdown

Learning Objectives per Module

Module 1: The Management Toolkit

• Identify the primary use cases for the AWS Management Console.
• Define Infrastructure as Code (IaC) and its benefits.
• Recognize the role of programmatic access via APIs and SDKs.

Module 2: Decision Frameworks

• Determine when a task is a "one-off" (e.g., proof of concept) versus a recurring need.
• Calculate the ROI of automating a process versus manual execution.

Module 3: Risk & Reliability

• Explain how repeatable processes reduce configuration drift.
• Identify scenarios where manual intervention poses a security or stability risk.

Module 4: Implementation Strategy

• Select between AWS CloudFormation, AWS CLI, and the Console for a given architectural deployment.

Visual Decision Guide

To determine the appropriate approach, follow this logical flow:

Success Metrics

To demonstrate mastery of this curriculum, the student must be able to:

1. Scenario Analysis: Correctly categorize 5/5 architectural scenarios as either one-time or repeatable.
2. Tool Selection: Justify the choice of tool (Console vs. IaC) based on the AWS Well-Architected Framework's Operational Excellence pillar.
3. Risk Identification: List three specific risks associated with manual environment setup for production workloads.

[!IMPORTANT] Mastery is not just knowing how to use the tools, but knowing when to use them. Over-engineering a one-time test with IaC can be as wasteful as manually configuring a production cluster.

Real-World Application

In a professional setting, this skill set is critical for:

• Cloud Architects: Designing environments that are disaster-recovery ready through automation.
• DevOps Engineers: Building CI/CD pipelines that require repeatable, immutable infrastructure.
• Cost Optimizers: Avoiding the "human tax" of manual labor on tasks that can be scripted.

Examples & Case Studies

Case Study 1: The Sandbox Experiment

• Scenario: A developer wants to spend 2 hours testing a new AI service (Amazon Bedrock) to see if it fits their needs.
• Requirement: One-time operation.
• Choice: AWS Management Console.
• Reasoning: Minimal setup time; no need for version control or reuse.

Case Study 2: The Multi-Region Rollout

• Scenario: A company needs to deploy its web application across 3 AWS Regions (US-East-1, EU-West-1, AP-Southeast-1) to ensure low latency.
• Requirement: Repeatable process.
• Choice: AWS CloudFormation or Terraform (IaC).
• Reasoning: Ensures parity across regions; eliminates manual configuration errors during the multi-site setup.

Comparison Table: Efficiency vs. Complexity

[!TIP] Use the formula below to approximate if you should automate: $If (T_{manual} \times N) > (T_{script} + T_{maint}), \text{ then Automate}$ Where $T$ is time, $N is the number of repetitions, and T_{maint}$ is the time to maintain the script.