LEARN BUILD GROW TOGETHER
DEVELOPER LEARNING HUB
Learn. Build. Grow Together.

Practical tutorials, real-world examples and interview preparation.

.NETC#SQL SERVERANGULAR
Home /.NET /AWS Interview Questions and Answers – 150 Questions for .NET Developers

AWS Interview Questions and Answers – 150 Questions for .NET Developers

AMAZON WEB SERVICES INTERVIEW PREPARATION

AWS Interview Questions

Prepare for AWS interviews with 150 questions and detailed answers for .NET Full Stack Developers. Cover AWS fundamentals, application hosting, Lambda, databases, storage, security, networking, messaging, CI/CD, monitoring, distributed systems, cloud architecture and production troubleshooting.

50 Questions · Beginner Level

1. AWS Fundamentals

01What is Amazon Web Services (AWS), and why do organizations use it for application development?

AWS is Amazon’s cloud platform offering compute, storage, databases, networking, security and developer services on demand. Teams use it to avoid managing physical data centres, scale capacity, deploy globally and pay for measured usage. A .NET solution might run APIs on ECS or App Runner, store files in S3 and use RDS for SQL Server.

02What is cloud computing? Explain IaaS, PaaS and SaaS with real-world AWS examples.

IaaS provides virtual machines and networks that you manage (EC2); PaaS provides a managed runtime/platform (Elastic Beanstalk or App Runner); SaaS is a finished application delivered over the internet. The key difference is how much infrastructure and software the customer must operate.

03What is the difference between public, private and hybrid cloud?

A public cloud uses a provider’s shared infrastructure with tenant isolation; a private cloud is dedicated to one organization; a hybrid cloud combines public cloud with private or on-premises systems. Hybrid is useful when data, legacy systems or compliance requirements mean some workloads must remain on-premises.

04What is an AWS Account, and why is it required?

An AWS account is the primary boundary for resources, billing, quotas and access controls. It provides an isolated environment in which services are created and usage is charged. Organizations commonly separate production, development and security workloads into multiple accounts.

05What is an AWS Region, and how does it differ from an Availability Zone?

A Region is a separate geographic area containing multiple Availability Zones. An Availability Zone is an isolated location within a Region, designed with independent power, cooling and networking. Deploying across AZs improves resilience to a single data-centre failure.

06What is an Amazon VPC, and why is it required?

A VPC is a logically isolated virtual network in which AWS resources run. You define its IP address ranges, subnets, route tables and network controls. It lets an application place public entry points separately from private APIs and databases.

07What is the difference between a public subnet and a private subnet in AWS?

A public subnet has a route to an Internet Gateway and can host resources that need direct internet reachability, subject to public IPs and security rules. A private subnet has no direct inbound internet route; outbound access may use a NAT Gateway. Databases and internal services normally belong in private subnets.

08What is the AWS Management Console, and how is it different from AWS CLI?

The AWS Management Console is a browser-based graphical interface for operating services. AWS CLI is a command-line tool suited to repeatable scripts, automation and terminal workflows. Both call AWS APIs, so permissions determine what either can do.

09What is AWS CloudFormation, and why is Infrastructure as Code important?

CloudFormation describes AWS infrastructure in templates and provisions it consistently. Infrastructure as Code makes environments repeatable, reviewable, version-controlled and easier to recreate. Templates can define resources, parameters, outputs and dependencies.

10What is AWS IAM, and how does it control access to AWS resources?

IAM manages identities and permissions for AWS resources. Policies specify allowed or denied actions on resources; users, groups and roles receive permissions through policy evaluation. Apply least privilege and prefer temporary role credentials over long-lived keys.

2. AWS Application Hosting and .NET Applications

11What is Amazon EC2, and how can you host an ASP.NET Core Web API on an EC2 instance?

EC2 provides virtual servers. To host an ASP.NET Core API, launch a suitable Windows or Linux instance, install the .NET hosting runtime if needed, deploy the published application, configure a service or web server such as IIS/Nginx, open only required ports, add TLS through a load balancer and configure monitoring.

12What is an EC2 instance type, and how do instance families differ?

EC2 instance families are optimized for different workloads: general purpose balances CPU and memory, compute optimized suits CPU-heavy work, memory optimized suits large in-memory workloads, and storage or accelerated-computing families target specialized needs. Choose based on measured utilization and test performance.

13What is an Amazon Machine Image (AMI)?

An AMI is a reusable image containing the operating system and configuration needed to launch EC2 instances. It can include software and settings, and is used by Auto Scaling and repeatable deployments. Keep images patched and versioned.

14How do you deploy an ASP.NET Core application to an Amazon EC2 instance running Windows or Linux?

Publish the .NET app for the target runtime, provision EC2, install the required .NET runtime/hosting bundle, copy the artifact, configure IIS on Windows or systemd plus Nginx on Linux, set environment variables and secrets, configure security groups and TLS, then test health and logs. Automate repeat deployments with CI/CD rather than manual copying.

15What is AWS Elastic Beanstalk, and how can you deploy a .NET application using it?

Elastic Beanstalk is a managed application deployment service that provisions resources such as EC2, load balancing and Auto Scaling. Package the .NET application in a supported deployment format, create an environment, deploy the version and configure environment properties. It reduces infrastructure setup while still allowing access to underlying resources.

16What is AWS App Runner, and how is it used to host containerized web applications?

App Runner is a managed service for building and running web applications and APIs from source code or container images. Connect a repository or ECR image, configure build/runtime settings, port, environment variables and instance sizing; App Runner manages deployment, TLS endpoint, scaling and health checks.

17What is Amazon ECS, and how does it help deploy containerized .NET applications?

ECS is AWS’s container orchestration service. Define a cluster, task definition with the .NET container image, IAM task roles, networking and resource limits, then run a service with desired task count and optional load balancer. ECS manages task placement and service health.

18What is Amazon ECR, and why is it used with Docker-based .NET applications?

ECR is a managed private container image registry. A CI pipeline builds the .NET Docker image, authenticates to ECR, tags and pushes it; ECS or App Runner then pulls the approved image. Use immutable tags/digests and scan images for vulnerabilities.

19What is an Application Load Balancer (ALB), and why is it useful for ASP.NET Core applications?

An Application Load Balancer distributes HTTP/HTTPS traffic to healthy targets such as EC2 instances or ECS tasks. It supports host/path routing, TLS termination and health checks. It allows multiple stateless .NET API instances to share traffic and recover from an unhealthy target.

20What is Amazon CloudFront, and how can it be used to deliver an Angular application?

CloudFront is a content delivery network that caches content at edge locations close to users. Build Angular into static files, store them in S3 or an origin, put CloudFront in front, configure HTTPS and SPA fallback routing, and invalidate or version assets during releases.

3. AWS Lambda and Serverless

21What is AWS Lambda, and how is it different from hosting an ASP.NET Core Web API on EC2?

Lambda runs code in response to events without requiring you to manage servers. EC2 gives persistent virtual-machine control and is suitable for continuously running services; Lambda is event-driven, automatically scales within quotas and charges by execution/resources. Lambda has runtime, duration and execution-environment constraints.

22What is serverless computing in AWS?

Serverless means AWS manages server provisioning and much of the scaling and availability work while code runs on demand or in response to events. It does not mean there are no servers. Developers still design for timeouts, retries, concurrency, permissions, observability and cost.

23What are Lambda triggers and event sources?

Triggers connect Lambda to events such as API Gateway requests, S3 object events, EventBridge schedules, SQS messages or DynamoDB streams. The event source invokes the function with an event payload. Configure permissions, batching, retry behavior and dead-letter handling for the source.

24What is Amazon API Gateway, and how can it expose AWS Lambda functions as REST APIs?

API Gateway creates and manages HTTP API endpoints and routes requests to Lambda or other backends. Configure routes, integrations, authorization, throttling, validation and stages; grant API Gateway permission to invoke the function. The Lambda handler processes the request and returns the expected response shape.

25What is the difference between AWS Lambda and Amazon ECS?

Lambda is suited to event-driven, short-lived functions with managed scaling; ECS runs containerized services or workers with more control over runtime, networking and long-running processes. Choose Lambda for discrete event handlers and ECS for continuously running APIs, workers or workloads needing container control.

4. AWS Database and Storage

26What is Amazon RDS, and how is it different from installing SQL Server on an EC2 instance?

RDS is a managed relational database service that handles tasks such as provisioning, backups and patching. SQL Server on EC2 gives more OS and instance control but you manage the database installation, backups, patching and high availability. Choose RDS to reduce operations where its engine features meet requirements.

27Which database engines are supported by Amazon RDS?

Amazon RDS supports Amazon Aurora, PostgreSQL, MySQL, MariaDB, Oracle and Microsoft SQL Server. Engine availability, versions, editions and features vary by Region and deployment option, so verify current support before designing a migration.

28What is Amazon RDS for SQL Server, and how can an ASP.NET Core application connect to it?

RDS for SQL Server is a managed SQL Server database. Create the DB instance in private subnets, allow inbound SQL traffic only from the API’s security group, configure credentials or supported authentication, store the connection string securely, and connect using Microsoft.Data.SqlClient or EF Core’s SQL Server provider.

29What is Amazon S3, and what types of data can it store?

S3 is object storage for unstructured data such as documents, images, videos, backups, logs and static website assets. Objects are stored in buckets and addressed by keys. It offers durability, lifecycle policies, versioning and access controls.

30What is the difference between Amazon S3, Amazon EBS and Amazon EFS?

S3 stores objects and is accessed through APIs; EBS provides block storage volumes typically attached to EC2; EFS provides a shared elastic file system that multiple Linux instances can mount. Choose object storage for files, block storage for server disks and shared file storage for POSIX-style access.

31What are the different Amazon S3 storage classes?

S3 classes include Standard, Intelligent-Tiering, Standard-IA, One Zone-IA, Glacier Instant Retrieval, Glacier Flexible Retrieval and Glacier Deep Archive. They trade access latency, availability, storage price and retrieval cost. Select by access frequency and retention requirements; confirm current class names and constraints.

32What is an S3 Bucket, and how is it different from an S3 Object?

A bucket is a top-level S3 container in a Region; an object is an individual stored item consisting of data, key and metadata. A bucket contains many objects, and permissions and lifecycle rules can be applied at bucket or object-related scope.

33What is an S3 pre-signed URL, and why is it used?

A pre-signed URL is a time-limited URL signed by an authorized AWS identity that grants a specific operation on an S3 object. It lets a client upload or download a private object without receiving AWS credentials. Keep expiry short and restrict method, key and content size where possible.

34How can you upload and download files from Amazon S3 using C# and the AWS SDK for .NET?

Use the AWS SDK for .NET, typically AWSSDK.S3. Create an IAmazonS3 client using the default credential chain or workload role, then call PutObjectAsync or TransferUtility for upload and GetObjectAsync/download methods for retrieval. Validate file type/size and grant only required S3 permissions.

35What is Amazon DynamoDB, and how does it differ from Amazon RDS?

DynamoDB is a managed NoSQL key-value/document database designed for low-latency access at scale. RDS is relational and supports SQL, joins and relational constraints. Choose DynamoDB for access patterns built around partition/sort keys and flexible items; choose RDS for relational queries and transactions.

5. AWS Security and Networking

36What is AWS IAM, and what is the difference between an IAM User, Group and Role?

An IAM user represents a long-lived identity, a group organizes IAM users for shared permissions, and a role is an assumable identity that provides temporary credentials. Applications and AWS services should generally use roles rather than permanent user access keys.

37What is an IAM Policy, and how does AWS evaluate permissions?

An IAM policy is a JSON document describing effects, actions, resources and optional conditions. AWS evaluates applicable identity and resource policies, boundaries and organization controls; an explicit Deny overrides an Allow. If no applicable Allow exists, access is denied.

38What is an IAM Role, and why should applications use roles instead of hardcoded AWS access keys?

An IAM role provides temporary credentials through an AWS security token service session. Attach a least-privilege role to EC2, ECS, Lambda or another supported workload so the SDK obtains credentials automatically. This avoids storing long-lived access keys in source code or configuration.

39What is AWS Secrets Manager, and why should .NET developers use it?

Secrets Manager stores and retrieves sensitive values such as database passwords and API credentials, supports encryption and can integrate with rotation workflows. A .NET application should access it through an IAM role and AWS SDK, cache secrets appropriately and avoid logging them.

40What is AWS Key Management Service (KMS)?

KMS creates and manages cryptographic keys used by AWS services and applications. It supports encryption operations, key policies, grants, auditing and integration with services such as S3, RDS and Secrets Manager. Control key access carefully because encryption security depends on permissions.

41What is an Internet Gateway in AWS?

An Internet Gateway attaches to a VPC and enables communication between resources with public addressing and the internet, when route tables and security controls permit it. It is horizontally scaled and highly available; it does not by itself make every subnet or instance public.

42What is a NAT Gateway, and why is it required for private subnets?

A NAT Gateway lets instances in a private subnet initiate outbound IPv4 connections to the internet while preventing unsolicited inbound internet connections. The private subnet routes internet-bound traffic to the NAT Gateway in a public subnet, which routes through an Internet Gateway. Use per-AZ NAT design for resilience.

43What is the difference between a Security Group and a Network ACL?

Security Groups are stateful virtual firewalls attached to network interfaces/resources; return traffic is automatically allowed. Network ACLs are stateless rules applied at subnet level and require explicit inbound and outbound rules. Security Groups are commonly the primary workload control; NACLs provide an additional subnet boundary.

44What is Amazon Cognito, and how can it provide authentication for an Angular application?

Cognito provides user directories and identity federation, including sign-up, sign-in and token issuance. An Angular app can use a Cognito User Pool with an OAuth/OIDC flow such as authorization code with PKCE, then send access tokens to an ASP.NET Core API that validates issuer, audience and signature.

6. Deployment and Monitoring

45What is AWS CodePipeline, and what is its role in CI/CD?

CodePipeline orchestrates CI/CD stages such as source retrieval, build, test and deployment. It connects services such as CodeBuild, CodeDeploy, S3, ECS and external source providers to automate release workflows and approvals.

46What is the difference between AWS CodeBuild and AWS CodeDeploy?

CodeBuild compiles code, runs tests and creates artifacts or container images in a managed build environment. CodeDeploy automates application deployments to supported targets such as EC2, Lambda and ECS. A pipeline often uses CodeBuild to produce an artifact and CodeDeploy to release it.

47What is AWS CodeCommit, and what alternatives can be used for source control in AWS-based projects?

CodeCommit was AWS’s managed Git repository service, but it is no longer available to new customers as of the service’s announced closure to new customers. Existing users should verify current service status and plan source control with GitHub, GitLab, Bitbucket or another supported Git provider integrated into AWS pipelines.

48What is Amazon CloudWatch, and how can it monitor an ASP.NET Core application?

CloudWatch collects AWS service metrics, logs and events and supports dashboards and alarms. For ASP.NET Core, send structured application logs to CloudWatch Logs, publish or collect metrics, create alarms for errors/latency/CPU and use Logs Insights to investigate request failures. Add correlation IDs and avoid logging secrets.

49What is AWS CloudTrail, and how is it different from CloudWatch?

CloudTrail records account activity and AWS API calls for governance, audit and investigation. CloudWatch focuses on operational metrics, logs and alarms. In short, CloudTrail answers who did what to AWS resources; CloudWatch helps determine how systems are operating.

50How do you troubleshoot an ASP.NET Core application hosted on EC2 or AWS App Runner when it stops responding?

Check the endpoint and load balancer health, instance/task status, security groups, routes, DNS and TLS first. Inspect application and platform logs in CloudWatch, CPU/memory and network metrics, deployment/configuration changes and downstream database health. Reproduce with request IDs, verify health endpoints and roll back a bad release if necessary.

How to use this page: Select a difficulty level and expand any question to review its answer. The examples and explanations focus on practical AWS architecture and integration with C#, ASP.NET Core, Angular, SQL Server and .NET application development.