AWS cost and support concepts are important CLF-C02 topics.
Pricing Concepts
AWS generally follows pay-as-you-go pricing. You usually pay for actual compute, storage, data transfer, and managed service usage.
Cost factors include:
- Running time
- Resource size
- Storage capacity
- Request count
- Data transfer
- Region
- Purchase model
Support Plans
AWS Support plans provide different response times and coverage.
Common tiers include Basic, Developer, Business, Enterprise On-Ramp, and Enterprise.
Higher tiers provide faster responses and broader support.
AWS Marketplace
AWS Marketplace is a marketplace for third-party software, images, and services.
It is useful for buying security tools, database tools, developer tools, and SaaS products.
AWS Partner Network
APN is the AWS Partner Network. It includes consulting, technology, managed service, and software partners.
Organizations can use APN to find AWS experts and solutions.
Well-Architected Framework
The Well-Architected Framework helps evaluate cloud architecture quality.
Core pillars:
- Operational Excellence
- Security
- Reliability
- Performance Efficiency
- Cost Optimization
- Sustainability
When reviewing a question, map it to the relevant pillar: security questions to Security, cost questions to Cost Optimization, and so on.
Deeper Notes
When reviewing this topic, do not memorize names only. Focus on pricing models, support plans, Marketplace, partner network, and the Well-Architected pillars. If this stays at the definition level, it becomes hard to explain in interviews or apply in projects. A stronger way to study it is to place it in a concrete scenario: who calls it, where the input comes from, what happens on failure, and whether data or state can be processed twice.
- AWS review should connect services into architecture: entry point, compute, networking, storage, permissions, monitoring, and cost.
- For each service, ask what problem it solves, who operates it, and what the blast radius is when it fails.
- Both exams and real projects care about boundaries: Region vs AZ, managed vs self-managed, stateful vs stateless resources.
In a real project, use it as a decision framework: identify inputs, constraints, failure modes, and observability before choosing a specific tool or pattern. If a solution looks simple, keep asking whether it still works when scale grows, permissions change, recovery matters, and more people collaborate on it.
Practical Checklist
- Identify where this concept sits in the system: development-time constraint, runtime behavior, infrastructure capability, or collaboration workflow.
- Write one minimal working example and one failure example; only knowing the happy path is usually not enough.
- Record common misuses: edge cases, permission assumptions, performance assumptions, sync/async differences, or environment differences.
- Connect the concept to a project experience so that an interview answer can be grounded in real tradeoffs.
- End with one sentence about tradeoff: what it gives up and what it buys.
Self-Check Questions
- What core problem does this topic solve?
- What alternatives exist, and what are their costs?
- Where are the most likely edge cases?
- How would code, tests, or monitoring prove that it is reliable?
Applied Scenario
A practical way to study this topic is to place it inside a small SaaS deployment: users enter through a domain, CloudFront or a load balancer receives traffic, the app runs on EC2, ECS, or Lambda, databases and caches live in private subnets, logs go to CloudWatch, permissions are controlled by IAM, and static assets are stored in S3. For every AWS service, ask where it sits in this chain: entry, compute, network, storage, security, monitoring, or cost control.
Common Pitfalls:
- Memorizing service names without being able to draw the request path.
- Ignoring network boundaries and exposing databases publicly.
- Not estimating cost or failure blast radius.