CertVector

Exam topics

AWS Cloud Practitioner: 20 services you should recognize

A beginner-friendly list of AWS service categories to practice before taking Cloud Practitioner, with guidance on how to avoid pure memorization.

Updated 2026-05-25 · 11 min read

Sign in

Compute and containers

Start with EC2, Lambda, Elastic Beanstalk, ECS, and EKS. Practice the difference between virtual machines, serverless functions, managed application deployment, and container orchestration instead of memorizing service names in isolation.

A real-world example helps: if a company wants full control of the operating system and installed software, EC2 is closer to that need. If it wants to run code in response to events without managing servers, Lambda is a better fit. If it wants managed deployment for a web application, Elastic Beanstalk may simplify the operational work.

For containers, focus on the management model. ECS is AWS container orchestration, while EKS is managed Kubernetes. You do not need to become a Kubernetes engineer for Cloud Practitioner, but you should recognize why a team might choose managed container orchestration instead of individual virtual machines.

Storage and databases

Recognize S3, EBS, EFS, RDS, DynamoDB, and Redshift. A good practice question should ask which service fits a workload, data pattern, durability need, or analytics scenario.

S3 is object storage, which makes it useful for files, static assets, backups, logs, and data lakes. EBS is block storage attached to EC2 instances. EFS is shared file storage. Those names are easier to remember when you connect them to the shape of the data: object, block, or file.

For databases, think about access pattern. RDS supports managed relational databases. DynamoDB supports key-value and document-style access at scale. Redshift is associated with data warehousing and analytics. In practice questions, the scenario should tell you whether the workload needs transactions, low-latency key access, or analytical queries.

Networking and delivery

Know the purpose of VPC, Route 53, CloudFront, Elastic Load Balancing, and Direct Connect. These topics often appear as scenario questions about connectivity, routing, global delivery, and hybrid access.

A VPC is the private networking space where many AWS resources run. Route 53 handles DNS and routing policies. CloudFront is a content delivery network. Elastic Load Balancing distributes traffic across targets. Direct Connect is used when an organization needs a dedicated network connection between its environment and AWS.

In real projects, these services are often combined. A public application might use Route 53 for DNS, CloudFront for global delivery, a load balancer for traffic distribution, and resources inside a VPC. Practice should help you understand each role so you do not pick the CDN when the question is really asking about DNS.

Security, identity, and monitoring

Focus on IAM, CloudTrail, CloudWatch, AWS Organizations, and KMS. Practice should make you choose the right service for permissions, audit logging, metrics, account governance, or encryption key management.

IAM controls who can access AWS resources and what they can do. CloudTrail records API activity for auditing. CloudWatch is used for metrics, logs, and alarms. AWS Organizations helps manage multiple accounts. KMS manages encryption keys. These services appear frequently because they support governance and operational visibility.

A common mistake is choosing a monitoring service for an audit question or an audit service for a metrics question. Read the verb in the scenario: monitor performance, record account activity, restrict permission, organize accounts, or manage encryption keys.

Cost and support

Cloud Practitioner also expects cost awareness. Review AWS Budgets, Cost Explorer, Trusted Advisor, and support plan concepts so you can answer questions about tracking spend and improving account posture.

In real cloud work, technical choices affect cost. Over-provisioned compute, unused storage, broad data transfer, and forgotten test environments can create avoidable spend. Cost tools help teams see usage, forecast bills, set alerts, and identify optimization opportunities.

When practicing cost questions, look for the task: alert before spending crosses a threshold, analyze historical costs, estimate a future workload, get architectural recommendations, or choose a support path. Each task points to a different tool or concept.

Learner discussion

Ask clarifying questions or share study notes. Comments are not reviewed CertVector explanations.

0 comments

No discussion yet. Start with a specific question or clarification.