Define Methods of Deploying and Operating in the AWS Cloud
Source: Dev.to
1️⃣ Ways to Access AWS Services
AWS Management Console
The Graphical User Interface (GUI) – a web‑based interface used for interactive management.
Best for:
- Learning AWS services
- Quick checks and ad‑hoc changes
- Visually exploring resources and settings
Manual steps are harder to repeat consistently if you use the console; that’s where programmatic access comes in.
Programmatic Access
APIs
All actions in AWS are ultimately API calls.
Best for: automation and integrating AWS actions into applications and pipelines.
SDKs
Language‑specific libraries (e.g., Python, Java, JavaScript) that call AWS APIs.
Best for: building apps that directly interact with AWS services.
CLI
Command‑line tool to call AWS services.
Best for:
- Scripting repetitive tasks
- Automation from a terminal
- Faster operations than clicking through the console
2️⃣ Infrastructure as Code (IaC)
IaC means defining infrastructure (networks, servers, permissions, etc.) using templates or code instead of manual setup.
Why IaC matters:
- Repeatable deployments
- Consistent environments (dev/test/prod)
- Version control and change tracking
- Reduced configuration drift and human error
3️⃣ One‑Time Operations vs. Repeatable Processes
One‑time operations
Examples: a single quick change, a one‑off test, initial learning.
Typical tools: AWS Management Console or a simple CLI command.
Repeatable processes
Examples: launching the same environment for every project, scaling standardized deployments, enforcing consistent configuration.
Typical tools: IaC and automation (templates + pipelines, CLI scripts, SDK‑based tooling).
If you’ll do it more than once, or if consistency matters, lean toward automation/IaC.
4️⃣ Cloud Deployment Models
Cloud (Public Cloud)
All workloads run in the cloud (e.g., AWS) with minimal or no on‑prem infrastructure.
Why choose the cloud: simplicity, scalability, reduced data‑center management.
Hybrid
Some systems run in AWS, others remain on‑premises, connected via networking and identity integrations.
Why choose hybrid: regulatory or data‑residency constraints, legacy systems that can’t move yet, phased migration strategy.
Private Cloud / On‑Premises
Workloads run in a company’s own data center.
5️⃣ How to Choose the Right Deployment Method
- Speed + simplicity now? → Console
- Automation or integration with software? → API / SDK
- Scripting and repeatable commands? → CLI
- Consistent, repeatable environments with version control? → IaC
✅ Quick Exam‑Style Summary
- AWS access methods: Console, CLI, SDK, APIs, and IaC.
- Prefer IaC/automation for repeatable, standardized deployments.
- Deployment models:
- Cloud: everything in AWS
- Hybrid: mix of AWS + on‑prem
- On‑premises: everything in a private data center