0% found this document useful (0 votes)
17 views9 pages

Essential AWS Services for Interviews

The document outlines major AWS services relevant for interview preparation, categorized into Compute, Storage, Database, Networking, Security, and Management services. Each service includes a brief description, key concepts, use cases, benefits, integrations, comparisons, best practices, and troubleshooting tips. This structured approach aims to help candidates articulate their knowledge effectively during AWS interviews.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views9 pages

Essential AWS Services for Interviews

The document outlines major AWS services relevant for interview preparation, categorized into Compute, Storage, Database, Networking, Security, and Management services. Each service includes a brief description, key concepts, use cases, benefits, integrations, comparisons, best practices, and troubleshooting tips. This structured approach aims to help candidates articulate their knowledge effectively during AWS interviews.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Major AWS Services for Interview Preparation

I. Compute Services

These are fundamental for running applications and code in the cloud.

• Amazon EC2 (Elastic Compute Cloud)

o What it is: Virtual servers (instances) in the cloud. You provision and
manage them.

o Key Concepts/Notes:

▪ Instance Types: Understand different families (e.g., General


Purpose, Compute Optimized, Memory Optimized) and when to
use each.

▪ AMIs (Amazon Machine Images): Templates for launching


instances.

▪ EBS (Elastic Block Store): Persistent block storage for EC2


instances.

▪ Security Groups: Virtual firewalls for instances (stateful).

▪ Key Pairs: For secure SSH access to Linux instances.

▪ Pricing Models: On-Demand, Reserved Instances, Spot Instances


(understand use cases for each).

▪ Lifecycle: Stopping vs. Terminating an instance.

• AWS Lambda

o What it is: Serverless compute service that runs your code in response to
events without provisioning or managing servers.

o Key Concepts/Notes:

▪ Event-driven: Triggered by various AWS services (S3, DynamoDB,


API Gateway, etc.).

▪ Function as a Service (FaaS): You only pay for compute time


when your code is running.

▪ Cold Starts: Understand what they are and strategies to mitigate


them.

▪ Integrations: How Lambda integrates with other AWS services.

• AWS Auto Scaling


o What it is: Automatically adjusts compute capacity (EC2 instances) to
maintain application availability and performance.

o Key Concepts/Notes:

▪ Scaling Policies: Dynamic, Scheduled, Predictive.

▪ Launch Configurations/Templates: Defines how new instances


are launched.

▪ Target Tracking, Simple, Step Scaling: Different types of dynamic


scaling.

• Elastic Load Balancing (ELB)

o What it is: Distributes incoming application traffic across multiple


targets, such as EC2 instances, in multiple Availability Zones.

o Key Concepts/Notes:

▪ Types: Application Load Balancer (ALB), Network Load Balancer


(NLB), Gateway Load Balancer (GLB), Classic Load Balancer (CLB
- older). Focus on ALB and NLB.

▪ High Availability & Fault Tolerance: How ELB contributes to


these.

▪ Health Checks: How ELB monitors the health of registered


targets.

• AWS Elastic Beanstalk

o What it is: Platform as a Service (PaaS) that simplifies deploying and


scaling web applications and services.

o Key Concepts/Notes:

▪ Managed Service: Handles infrastructure provisioning and


management.

▪ Use Cases: Rapid deployment for developers who want to focus


on code.

II. Storage Services

Essential for storing and managing data in the cloud.

• Amazon S3 (Simple Storage Service)

o What it is: Object storage service, highly scalable, durable, and secure.
o Key Concepts/Notes:

▪ Buckets & Objects: Fundamental concepts.

▪ Storage Classes: Standard, Intelligent-Tiering, Standard-IA, One


Zone-IA, Glacier, Glacier Deep Archive (understand their cost and
access patterns).

▪ Versioning: Keeping multiple versions of an object.

▪ Lifecycle Policies: Automating object transitions between storage


classes or deletion.

▪ Access Control: Bucket Policies, ACLs, IAM Policies.

▪ Static Website Hosting: A common use case.

• Amazon EBS (Elastic Block Store)

o What it is: Persistent block storage for EC2 instances.

o Key Concepts/Notes:

▪ Volume Types: General Purpose SSD (gp2/gp3), Provisioned IOPS


SSD (io1/io2), Throughput Optimized HDD (st1), Cold HDD (sc1).
Understand when to use each.

▪ Snapshots: Point-in-time backups of EBS volumes.

▪ Encryption: How to encrypt EBS volumes.

• Amazon EFS (Elastic File System)

o What it is: Scalable, elastic file storage that can be shared across
multiple EC2 instances.

o Key Concepts/Notes:

▪ Shared File System: NFSv4 protocol.

▪ Scalability: Automatically grows and shrinks.

▪ Use Cases: Content management, web serving.

• Amazon Glacier / S3 Glacier Deep Archive

o What it is: Extremely low-cost storage for data archiving and long-term
backup.

o Key Concepts/Notes:

▪ Retrieval Times: Can range from minutes to hours.


▪ Cost-Effectiveness: Ideal for infrequently accessed data.

III. Database Services

Various options for different database needs.

• Amazon RDS (Relational Database Service)

o What it is: Managed relational database service. Supports various


engines (MySQL, PostgreSQL, Oracle, SQL Server, Aurora).

o Key Concepts/Notes:

▪ Managed Service Benefits: AWS handles patching, backups,


scaling, etc.

▪ Multi-AZ Deployments: For high availability and disaster recovery.

▪ Read Replicas: For read scaling.

▪ Aurora: AWS's highly performant, MySQL/PostgreSQL compatible


relational database.

• Amazon DynamoDB

o What it is: Fully managed, serverless NoSQL key-value and document


database.

o Key Concepts/Notes:

▪ Scalability & Performance: Single-digit millisecond latency at any


scale.

▪ Provisioned Throughput vs. On-Demand: Understanding pricing


models.

▪ Global Tables: For multi-region replication.

▪ Streams: For real-time data processing (e.g., with Lambda).

• Amazon Redshift

o What it is: Fully managed, petabyte-scale data warehousing service.

o Key Concepts/Notes:

▪ Analytics & Business Intelligence: Optimized for large-scale data


analytics.

▪ Columnar Storage: How it differs from row-based.

▪ Integration with S3: For data loading.


IV. Networking & Content Delivery

How resources communicate and are accessed.

• Amazon VPC (Virtual Private Cloud)

o What it is: Allows you to provision a logically isolated section of the AWS
Cloud where you can launch AWS resources in a virtual network that you
define.

o Key Concepts/Notes:

▪ Subnets (Public/Private): Understanding network segmentation.

▪ Route Tables: Control where network traffic is directed.

▪ Internet Gateway (IGW): Allows communication between your


VPC and the internet.

▪ NAT Gateway/Instances: Enable instances in private subnets to


connect to the internet.

▪ Security Groups vs. Network ACLs (NACLs): Critical difference


(stateful vs. stateless, instance vs. subnet level).

▪ VPC Peering: Connecting two VPCs.

• Amazon Route 53

o What it is: Highly available and scalable Domain Name System (DNS)
web service.

o Key Concepts/Notes:

▪ DNS Resolution: How it maps domain names to IP addresses.

▪ Routing Policies: Simple, Weighted, Latency-based, Geolocation,


Failover, Multivalue Answer.

▪ Health Checks: For failover routing.

• Amazon CloudFront

o What it is: Content Delivery Network (CDN) service that securely delivers
data, videos, applications, and APIs to customers globally with low
latency.

o Key Concepts/Notes:

▪ Edge Locations: Caching content closer to users.

▪ Reduced Latency & Bandwidth: Benefits of using a CDN.


V. Security, Identity & Compliance

Crucial for securing your AWS environment.

• AWS IAM (Identity and Access Management)

o What it is: Manages access to AWS services and resources securely.

o Key Concepts/Notes:

▪ Users, Groups, Roles, Policies: Understand each component and


how they interact.

▪ Least Privilege Principle: Granting only necessary permissions.

▪ MFA (Multi-Factor Authentication): For enhanced security.

▪ Access Keys vs. IAM Roles: When to use each for


applications/services.

• AWS Key Management Service (KMS)

o What it is: Manages encryption keys.

o Key Concepts/Notes:

▪ Encryption at Rest & In Transit: How KMS helps.

▪ Integration with other AWS services: S3, EBS, RDS, etc.

• AWS Shield / AWS WAF (Web Application Firewall)

o What it is:

▪ Shield: DDoS protection service.

▪ WAF: Protects web applications from common web exploits.

o Key Concepts/Notes:

▪ Layer 7 Protection (WAF): Against SQL injection, cross-site


scripting.

▪ DDoS Protection (Shield): Standard (automatic) vs. Advanced


(enhanced).

VI. Management & Governance

Tools for operating and monitoring your AWS resources.

• Amazon CloudWatch
o What it is: Monitoring and observability service that provides data and
actionable insights to monitor applications, respond to system-wide
performance changes, and optimize resource utilization.

o Key Concepts/Notes:

▪ Metrics, Logs, Events: The core components.

▪ Alarms: Triggering actions based on metric thresholds.

▪ Dashboards: Visualizing metrics.

• AWS CloudTrail

o What it is: Records API calls and related events made in your AWS
account and delivers log files to an S3 bucket.

o Key Concepts/Notes:

▪ Auditing & Compliance: Tracking who did what, when, and from
where.

▪ Security Analysis: Identifying suspicious activity.

• AWS CloudFormation

o What it is: Infrastructure as Code (IaC) service that allows you to model
and provision AWS and third-party resources.

o Key Concepts/Notes:

▪ Templates (JSON/YAML): Defines your infrastructure.

▪ Stacks: The deployed instance of a CloudFormation template.

▪ Automation & Consistency: Benefits of IaC.

Interview-Oriented Study Notes Structure

For each service, you should be able to articulate:

1. What it is: A concise definition.

2. Key Features: List 2-3 important features.

3. Use Cases: When would you use this service? Provide concrete examples.

4. Benefits: What problems does it solve? (e.g., scalability, cost-effectiveness,


security, high availability, reduced operational overhead).
5. How it integrates with other services: (e.g., Lambda triggered by S3, EC2 using
EBS, CloudWatch monitoring EC2).

6. Comparison (if applicable): How does it differ from a similar service? (e.g., EC2
vs. Lambda, S3 vs. EBS vs. EFS, Security Group vs. Network ACL, RDS vs.
DynamoDB).

7. Best Practices: (e.g., for EC2: choose the right instance type; for S3: use
lifecycle policies for cost optimization; for IAM: follow least privilege).

8. Troubleshooting: Basic ideas on how to troubleshoot issues related to the


service.

Example for EC2 (as a study note):

Service: Amazon EC2 (Elastic Compute Cloud)

• What it is: Virtual servers in the AWS cloud. Provides resizable compute
capacity.

• Key Features:

o Scalable: Easily scale up/down instances.

o Flexible: Various instance types (CPU, memory, storage optimized).

o Secure: Integrated with VPC and IAM.

• Use Cases:

o Hosting web servers and applications.

o Running batch jobs.

o Hosting databases (though RDS is often preferred for managed relational


DBs).

o Development and testing environments.

• Benefits:

o Scalability & Elasticity: Quickly adjust resources.

o Cost-Effective: Pay-as-you-go, various pricing models to optimize.

o Reliability: High availability with multiple AZs.

• Integration:

o Uses EBS for persistent storage.

o Protected by Security Groups.


o Monitored by CloudWatch.

o Managed by Auto Scaling and ELB.

o Accessed via VPC.

• Comparisons:

o vs. Lambda: EC2 gives you more control over the server OS, but you
manage it. Lambda is serverless, less control but less operational
overhead, event-driven.

• Best Practices:

o Right-sizing instances to meet demand.

o Using Auto Scaling for fluctuating workloads.

o Implementing Security Groups and Network ACLs for network security.

o Utilizing Reserved Instances for predictable, long-term workloads for cost


savings.

• Troubleshooting:

o Check instance status checks (system and instance).

o Review CloudWatch metrics (CPU utilization, network I/O).

o Verify Security Group and NACL rules.

o Check system logs.

By thoroughly understanding these services and practicing articulating your knowledge


with this structured approach, you'll be well-prepared for any AWS interview. Good luck!

Common questions

Powered by AI

Amazon RDS and Amazon DynamoDB serve different database needs. RDS is a managed relational database service supporting multiple engines like MySQL, PostgreSQL, Oracle, SQL Server, and Aurora, designed for complex querying and transaction handling with ACID compliance . It features Multi-AZ deployments for high availability and supports read replicas for scale-out . In contrast, DynamoDB is a fully managed NoSQL database designed for key-value and document data models, offering single-digit millisecond latency at any scale . It scales automatically and seamlessly accommodates unpredictable workloads through its on-demand capacity mode . While RDS requires some level of database administrator intervention for tasks like patch management and backups, DynamoDB operates with less operational complexity, handling capacity and scaling automatically without manual setup . Ultimately, RDS is suited to structured, transactional requirements, while DynamoDB is ideal for fast, scalable access to unstructured data, leaving operational concerns to AWS.

Amazon EC2 integrates with several AWS services to deliver enhanced functionality. It uses EBS for persistent block storage, allowing data persistence beyond the lifecycle of an EC2 instance . Security is enforced via Security Groups, which act as a virtual firewall . Auto Scaling can automatically add or remove instances based on demand, thus maintaining performance and cost-efficiency . ELB (Elastic Load Balancing) is often used to distribute incoming application traffic across multiple instances, improving availability and fault tolerance . EC2 instances can be monitored with CloudWatch for performance insights and alerts . Finally, VPC (Virtual Private Cloud) allows secure networking by launching EC2 instances in a logically isolated network that you define .

Amazon S3 offers several storage classes designed to optimize cost and access efficiency: Standard, Intelligent-Tiering, Standard-IA (Infrequent Access), One Zone-IA, Glacier, and Glacier Deep Archive . Standard is ideal for frequently accessed data, providing high availability and performance. Intelligent-Tiering automatically moves data between two access tiers when access patterns change, optimizing costs while ensuring availability . Standard-IA and One Zone-IA are for data that is less frequently accessed but requires rapid access when needed, with the latter being cheaper as it stores data in a single availability zone . Glacier and Glacier Deep Archive provide extremely low-cost storage intended for archival data with retrieval times ranging from minutes to hours . Decision-making involves balancing the frequency of data access, criticality, and storage costs, aligning with business requirements for availability and budget constraints.

AWS Elastic Beanstalk simplifies application deployment and scalability by providing a fully managed platform as a service (PaaS) where developers can focus solely on writing code without worrying about underlying infrastructure. It automatically handles the application deployment, load balancing, auto-scaling, and monitoring of resources . Developers simply upload their code, and Elastic Beanstalk manages the deployment processes like the provisioning of resources such as EC2 instances, load balancers, and auto-scaling groups, removing the complexities of infrastructure setup . This managed service streamlines the development process by minimizing manual configurations and accelerates scaling operations in response to traffic demands, thus ensuring high availability and performance without developer intervention .

Optimizing Amazon EC2 instance costs involves leveraging various pricing models to align with workload requirements and priorities. The On-Demand pricing model is suitable for users who prefer no long-term commitment but can be costly if used continuously . Reserved Instances, purchased for a term of one or three years, offer significant savings for steady-state, predictable workloads . To further minimize costs, Spot Instances can be employed for applications with flexible start and end times, such as batch processing and data analytics, due to their cheaper rates by utilizing unused EC2 capacity . Combining these models based on workloads — using Reserved Instances for baseline capacity, On-Demand for spikes, and Spot Instances for opportunistic jobs — allows for cost-effective resource allocation without compromising performance.

Amazon CloudWatch provides several benefits by offering comprehensive monitoring solutions for AWS resources and applications. It collects metrics, logs, and events, allowing users to gain transparent insights into their systems' health and performance . Through metrics collection, CloudWatch provides real-time data on resource utilization, application performance, and operational health, which aids in system maintenance by enabling timely detection and resolution of issues . Moreover, it supports the creation of alarms that trigger automated responses to specific conditions, thus optimizing resource management and cost-efficiency . CloudWatch dashboards provide a platform for visualizing operational data, assisting in trend analysis, and supporting proactive decision-making for infrastructure optimization.

AWS Auto Scaling enhances an application's availability and performance by automatically adjusting the compute capacity of Amazon EC2 instances in response to demand changes. This process is achieved through scaling policies which can be dynamic, scheduled, or predictive . By automatically scaling out when demand increases and scaling in when demand decreases, Auto Scaling ensures that applications maintain an optimal level of performance without unnecessary resource expenditure . This adaptability helps to prevent resource overuse and underuse, thus ensuring high availability by maintaining the right number of running instances to fulfill current user demands . As traffic surges are efficiently managed, application performance remains steady, preventing bottlenecks and outages.

AWS Lambda would be preferred over EC2 in scenarios where operational overhead needs to be minimized. Lambda offers a serverless architecture, meaning you don't need to manage any servers that your code runs on, unlike EC2 where you have full server control, but also maintenance responsibilities . It's particularly advantageous for event-driven applications or workloads with unpredictable scaling requirements, as Lambda scales automatically in response to incoming requests . For applications that only need compute resources for short amounts of time and have intermittent workloads, Lambda's pricing model is cost-effective since you only pay for the compute time consumed .

AWS IAM plays a critical role in securing access to AWS resources by enabling detailed access control mechanisms. It allows you to create and manage AWS users, groups, and roles, and assign specific permissions to them via policies . The principle IAM should adhere to for effective security management is the Principle of Least Privilege, which dictates that users, processes, or systems should only have the minimum level of access necessary to perform their functions . This approach minimizes the potential attack surface by reducing unnecessary permissions that could be exploited if a security breach occurs. By implementing fine-grained access controls and regularly auditing permissions, IAM ensures secure usage and compliance across AWS environments.

AWS Lambda operates under a serverless compute model, meaning users can execute code in response to various events without provisioning or managing servers. This model is advantageous for specific workloads due to its automatic scaling features, only charging users for the compute time consumed . Lambda is particularly effective for event-driven architectures, such as image processing from S3 events or real-time file transformation via API calls . It eliminates infrastructure management tasks, reducing operational overhead. Compared to traditional compute services like EC2, Lambda offers simplicity and cost reductions for irregular and spontaneous workloads, enabling developers to focus more on application logic rather than server maintenance .

You might also like