in Resources

A Comprehensive Guide to AWS Key Terminology for Beginners

Amazon Web Services (AWS) has cemented its position as the undisputed leader in cloud computing, with a market share of over 30% according to Gartner. As enterprises accelerate their migration to the cloud, AWS skills are in huge demand. However, the wide array of services and seemingly complex terminology can overwhelm newcomers.

As a certified AWS Solutions Architect, I understand the learning challenges people face. In this detailed guide, I will explain the most important AWS concepts and terminology in simple terms to help beginners master the basics. I will also share tips, real-world examples, and best practices culled from my experience of designing cloud architectures for clients.

Let‘s start by looking at the global infrastructure that powers AWS.

Diving Deep into AWS Global Infrastructure

AWS operates the largest and most reliable cloud infrastructure platform, with 24 geographic regions across the world. Each region consists of two or more isolated locations known as Availability Zones (AZs).

AZs are effectively separate data centers, each with redundant power, cooling and networking. By deploying your applications across AZs, you can achieve high availability and fault tolerance.

Here are some interesting facts about the AWS global infrastructure:

  • AWS has 84 Availability Zones across 26 geographic regions currently. This is far more than other cloud providers like Microsoft Azure (60 zones) and Google Cloud (24 zones).

  • 5 new AWS regions and 15 more AZs are coming up in 2025 across countries like UAE, New Zealand, Spain, and Switzerland.

  • Each AZ has multiple redundant servers and networking equipment without any single point of failure. Even if an entire AZ goes down, the other AZs in the region will ensure your application remains operational.

  • Amazon has over 200 points of presence (POPs) worldwide which house edge locations for their CloudFront content delivery network (CDN). CloudFront ensures your users experience low latency no matter where they are located geographically.

So in summary, the huge investment AWS has made in building regions, AZs, and edge locations provides you the confidence and peace of mind that your critical applications will stay highly available.

Key Compute Services: EC2, Lambda, Containers

One of the most confusing parts of learning AWS is the myriad of compute options available. Let‘s evaluate the key alternatives for deploying applications on AWS:

Amazon EC2 – This is the most widely used service that provides resizable virtual machines to run applications on. You can choose from hundreds of instance types optimized for different workloads like web servers, gaming, data analytics, and graphic rendering.

Some tips on using EC2 effectively:

  • Always launch EC2s in at least two AZs for fault tolerance against AZ failures.
  • Use auto scaling groups to dynamically scale EC2 capacity up or down based on demand.
  • Optimize costs by purchasing 1 or 3 year reserved instances if you have predictable usage.

AWS Lambda – This is a serverless compute option that runs your code in response to triggers without needing to manage servers. Use Lambda when you have event-driven and intermittent compute needs.

Lambda is extremely cost-efficient as you only pay for the duration your code executes and do not have to provision resources 24/7. For example, many of my clients use Lambda for image processing, DB table updates, and IT automation.

AWS Fargate – This is used to deploy and scale containerized applications without having to manage servers or clusters. Fargate works perfectly with services like Amazon ECS and EKS.

The key is assessing workload characteristics and variable demands to pick the right compute option. Mix and match EC2, Lambda, and containers to optimize costs, performance, and scalability.

Storage Options: S3, EBS, and Glacier

AWS offers storage options that are exabyte-scale, secure, and cost-efficient for any use case:

Amazon S3 – For cloud-native apps, S3 provides any amount of durable object storage via simple APIs. You pay only for what you use. Use S3 for image storage, backups, big data analytics, static websites and so on.

Amazon EBS – EC2 instances require block storage volumes for boot volumes, local instance storage, and running databases. EBS provides flexible persistent SSD volumes to EC2.

Amazon S3 Glacier – For long-term archival storage with retrieval times ranging from minutes to hours, Glacier offers industry-leading cost savings of up to 90%.

A useful tactic is using S3 for live data, EBS for performance-sensitive workloads, and Glacier for archived data. Combine them efficiently based on access patterns and cost considerations.

Networking and Security Essentials

Let‘s cover two fundamentals for keeping your cloud environments secured and optimized for performance:

Amazon VPC – This allows you to define your own virtual network in the AWS cloud. You can launch AWS resources like EC2 instances into your VPC.

Best practices for VPC setup:

  • Launch your VPC with an IP address range like 10.0.0.0/16
  • Create public and private subnets across multiple AZs
  • Use security groups (like firewalls) to tightly control inbound and outbound traffic
  • Setup internet and NAT gateways for internet access from private subnets

AWS IAM – This service is used to set up user accounts and granular permissions policies across AWS. Follow the least privilege access rule while defining IAM policies.

For example, your application servers only need read access to S3 buckets and no need for console login access. Lock down policies to the minimum required permissions only.

VPC and IAM will enable you to create an isolated network with precisely controlled access – critical for security.

Architecting for High Availability

When migrating business-critical applications to the cloud, you must ensure they are designed for high availability across multiple failure points:

AZ deployment – Distribute application servers and databases across at least two or more AZs. This protects against AZ outages.

Elastic Load Balancing – Use ELB to distribute traffic across EC2 instances deployed in multiple AZs. ELB nodes are also distributed to provide fault tolerance.

Auto Scaling – Automatically scale-out EC2 capacity across AZs based on demand spikes. This maintains performance during traffic surges.

Multi-Region DR – Replicate databases using AWS services like RDS Cross-Region Read Replicas. Deploy select applications in a second region for disaster recovery.

Regular Backups – Automate backups of databases, message queues, object storage to S3 using lifecycle policies. Test restores regularly.

While architecting for high availability takes more planning, it is well worth the effort to gain peace of mind and minimize outage risks.

Optimizing Costs in the Cloud

With cloud, you pay only for the resources used. However, as usage scales, AWS bills can quickly spiral out of control without proper cost governance and oversight.

Here are some best practices I follow to optimize costs for clients:

  • Use auto scaling and Lambda to run infrastructure at optimal capacity without overprovisioning

  • Purchase reserved instances for steady-state workloads – offers up to 72% savings

  • Use AWS Savings Plans for committing usage at discounted rates

  • Right-size EC2 instances to avoid severely underutilized machines

  • Follow tagging standards to track resource ownership and utilization

  • Set up CloudWatch billing alerts for cost visibility and being proactive

  • Use AWS Cost Explorer to get spend visibility and identify top cost drivers

The cloud offers unlimited potential for innovation and agility. But you have to constantly assess spend and implement governance for cost-efficiency.

Key Takeaways and Next Steps

Let‘s summarize the key benefits of AWS we have discussed:

  • Global resilient infrastructure with regions, AZs and edge locations

  • Breadth of services like EC2, S3, Lambda, VPC that you can mix and match

  • Ability to achieve high availability across AZs and regions

  • Precise access control via IAM and security policies

  • Pay only for resources used and scale seamlessly

I have explained the essential AWS concepts using real-world examples derived from my experience. For next steps, I recommend:

Feel free to reach out if you need any assistance in your learning journey. I will be happy to offer guidance, best practices, and technical advice for getting started on AWS.

AlexisKestler

Written by Alexis Kestler

A female web designer and programmer - Now is a 36-year IT professional with over 15 years of experience living in NorCal. I enjoy keeping my feet wet in the world of technology through reading, working, and researching topics that pique my interest.