AWS has 200+ services. You only need about 10 to start
Ignore the 200+ service list. To build and run a real product on AWS you mainly need: EC2 or Lambda (compute), S3 (storage), RDS (database), VPC (networking), IAM (access), CloudWatch (monitoring), Route 53 (DNS), and CloudFront (CDN). Master these and the rest is detail.
The first time you open the AWS console, the sheer number of services is paralysing. Two hundred of them, with names that explain nothing. The secret every experienced engineer knows is that you can build almost anything with a small, stable core. Learn that core, and AWS stops being scary.
Compute: EC2 and Lambda
EC2 gives you virtual servers you control fully, you choose the size, the operating system, and what runs on them. It is the workhorse for traditional applications. Lambda runs your code on demand without any server to manage, you are billed only while your function runs.
Rule of thumb: use Lambda for small, event-driven tasks and EC2 for long-running applications. Many products use both.
Storage and databases: S3 and RDS
S3 stores files, images, backups, documents, static website assets, durably and cheaply, with no capacity to manage. It is one of the most-used services on all of AWS. RDS runs managed relational databases (PostgreSQL, MySQL) so you get a real database without patching or backing it up by hand.
Between S3 for files and RDS for structured data, you cover the storage needs of most applications.
Networking and access: VPC and IAM
VPC is your private network inside AWS, it controls what can talk to what, and what is exposed to the internet. IAM controls who can do what in your account: users, roles, and permissions.
These two are less glamorous but essential. Good VPC and IAM setup is the difference between a secure account and a breach waiting to happen.
Delivery and visibility: Route 53, CloudFront, CloudWatch
Route 53 is DNS, it points your domain name at your AWS resources. CloudFront is the CDN that caches your content at edge locations worldwide, including near African users, for speed.
CloudWatch is monitoring and logging, it tells you how your systems are performing and alerts you when something breaks. Without it, you are flying blind.
A realistic first architecture
A typical small product: a domain in Route 53, pointing to CloudFront, serving a site whose files live in S3 and whose application runs on EC2 or Lambda, backed by an RDS database, all inside a VPC, with access controlled by IAM and health watched by CloudWatch.
That is a complete, production-grade setup using fewer than ten services. Everything else AWS offers is an optimisation or a specialised tool you adopt only when a real need appears.
Key takeaways
- You can build a complete product on AWS with under ten services, ignore the overwhelming full catalogue at first.
- Compute (EC2/Lambda), storage (S3), and database (RDS) are the core building blocks of almost any application.
- VPC and IAM are unglamorous but essential, they decide whether your account is secure.
- Route 53, CloudFront, and CloudWatch handle naming, speed, and visibility, the finishing layer of a real system.
Frequently asked questions
Use Lambda for short, event-driven tasks (processing an upload, responding to a webhook) where you do not want to manage a server. Use EC2 for applications that run continuously or need full control of the environment. Many real systems combine both.
AWS has the largest ecosystem, the most learning resources, and the most job demand, which makes it a strong first choice. Google Cloud and Azure are also excellent. The concepts transfer between them, so starting with any of the three is a good decision.
Stay within the free tier, use the smallest instance sizes, set a billing alarm, and delete resources the moment you finish an exercise. Most beginner bills come from a forgotten EC2 instance or RDS database left running.
Sources
- Amazon Web Services, 2026. "AWS Products and Services."
- Amazon Web Services, 2026. "AWS Well-Architected Framework."
- Amazon Web Services, 2026. "Getting started with AWS."
Want a clean AWS setup without the guesswork? Kaevor designs and builds production AWS environments for African teams. Message us on WhatsApp, we respond same day.
Chat on WhatsApp →