Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 6 · Lesson 2 of 4
Deployment tools and cloud deployment models
1 min read
AWS CloudFormation is infrastructure as code. A template is a text file describing resources, and CloudFormation creates them together as a stack. The same template builds identical environments across Regions and accounts, and keeping it in version control records every change.
Deleting the stack deletes the resources it created, unless a resource is set to be retained, while deleting only the template file changes nothing that is running.
- AWS Elastic Beanstalk: upload application code and it handles capacity, health monitoring and scaling.
- AWS Systems Manager: operate resources that already exist, such as running one command across many instances.
- AWS Outposts: AWS-managed infrastructure placed on the customer's own site, with the same APIs and tools, for very low latency or local data processing.
Deployment models describe where an application runs. In a cloud deployment, all parts run in the cloud, whether built there or migrated. A hybrid deployment connects cloud resources with resources kept outside the cloud, for example an on-site data center linked to AWS with AWS Direct Connect.
An on-premises deployment keeps everything in the company's own facilities. Example: a school district moves its grading system to Amazon EC2 but keeps student records in its own server room, joined by a private link. That is hybrid.
Check yourself
1. A retailer keeps its own data center for its ordering system, runs analytics on AWS, and connects the two with AWS Direct Connect. Which deployment model does this describe?
2. A company must create identical test, staging and production environments in three Regions, and auditors want every infrastructure change tracked. Which approach best meets these needs?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, AWS Global Infrastructure: Regions and Availability Zones, AWS CloudFormation User Guide
AWS Cloud Practitioner cheat sheet: every key fact on one page →