Methods of Deploying and Operating in AWS
Define methods of deploying and operating in the AWS Cloud
What you will learn
- Name the four core ways of interacting with AWS resources.
- Explain the benefit of infrastructure as code (IaC) via CloudFormation compared to manual setup.
- Describe how Elastic Beanstalk simplifies a full application's deployment cycle.
- Pick the right tool (console or IaC) based on team size and how often the task repeats.
"Using AWS" is not one action — there are four different ways, ranging from best-suited to manual exploration to best-suited for reliable, automated repetition. Picking the wrong tool doesn't stop the work, but it makes repeating it later slower and more error-prone.
The four methods
| AWS Management Console | A graphical web interface — best for exploration, learning, and infrequent tasks. |
|---|---|
| AWS CLI | A command-line interface performing the same console operations through scriptable, automatable commands. |
| AWS SDK | Software libraries (in languages like Python and JavaScript) that call AWS services directly from within the application's own code. |
| Infrastructure as Code (CloudFormation) | Describing the entire required infrastructure in a single text template, run consistently and repeatably every time. |
Manual setup vs. infrastructure as code
| The console (manually) | CloudFormation (code) | |
|---|---|---|
| Consistency across environments | Prone to human error that differs between environments | The same template produces the exact same setup every time |
| Documentation | Relies on separate documentation that may be neglected | The template itself is living documentation of the actual infrastructure |
A deployment cycle via Elastic Beanstalk
Upload the code package
No need to manually provision any resource beforehand.
Beanstalk automatically provisions the infrastructure
EC2 instances, a load balancer, an Auto Scaling group.
Automatic health monitoring
Replacing any unhealthy instance without manual intervention.
What matters on the exam
- "The same result every time" or "no difference between test and production environments" points to CloudFormation (IaC).
- "Calling an AWS service directly from the application's code" points to an SDK, not the CLI.
The four aren't necessarily mutually exclusive
A realistic team uses the console for initial exploration, the CLI for recurring manual tasks, an SDK inside the application's own code, and CloudFormation for infrastructure that must stay consistent across multiple environments — the choice depends on the task, not on one tool being "best overall."
Quick check
Answer in your head first, then reveal.
Which tool describes infrastructure as a rerunnable text template?Reveal the answer
AWS CloudFormation.
What is the difference between the CLI and an SDK?Reveal the answer
The CLI is standalone terminal commands; an SDK is libraries called from within the application's own code.
What does Elastic Beanstalk automatically manage on your behalf?Reveal the answer
Instance provisioning, load balancing, auto scaling, and health monitoring.
Sign in to track your progress on this topic.
Your next step
Read the lesson, then mark it complete
Sources
Used to verify the facts. The writing is original to Passuit.