AWS Testing Interview Questions: 25 Most Asked (1970)

Common AWS services tested in 2026 include Lambda (serverless functions), S3 (object storage), RDS / DynamoDB (databases), API Gateway (REST APIs), SQS / SNS (queues and topics), ECS / EKS / Lambda (compute), and CloudFront + S3 (CDN and static hosting). Pair this with our API Testing Tutorial for end-to-end coverage.

Invoke the function directly with boto3 and assert the response payload and status code.

import boto3, json

def test_lambda_invoke():
    client = boto3.client('lambda', region_name='us-east-1')
    response = client.invoke(
        FunctionName='my-function',
        Payload=json.dumps({'key': 'value'})
    )
    payload = json.loads(response['Payload'].read())
    assert payload['statusCode'] == 200

Use moto to mock AWS services in-process — no real cloud calls, no credentials.

from moto import mock_aws
import boto3

@mock_aws
def test_s3_upload():
    s3 = boto3.client('s3')
    s3.create_bucket(Bucket='test-bucket')
    s3.put_object(Bucket='test-bucket', Key='file.txt', Body=b'hello')
    response = s3.get_object(Bucket='test-bucket', Key='file.txt')
    assert response['Body'].read() == b'hello'

List or fetch objects with boto3 and assert the expected keys/contents exist.

import boto3

def test_s3_list_objects():
    s3 = boto3.client('s3')
    response = s3.list_objects_v2(Bucket='my-bucket')
    keys = [obj['Key'] for obj in response.get('Contents', [])]
    assert 'expected-file.txt' in keys

import boto3

def test_dynamodb_query():
    dynamodb = boto3.resource('dynamodb')
    table = dynamodb.Table('Users')
    response = table.get_item(Key={'UserId': '123'})
    item = response.get('Item')
    assert item is not None
    assert item['Email'] == 'admin@example.com'

For broader API/data testing context, see our API Testing Tutorial.

Test the integration in layers: (1) direct Lambda invocation for unit tests, (2) API Gateway test events for integration, (3) end-to-end via curl/Postman for system tests. See our Postman API Testing Tutorial for the E2E layer.

Use dummy credentials for local dev with moto, and IAM roles for CI/CD.

import os
os.environ['AWS_ACCESS_KEY_ID'] = 'test'
os.environ['AWS_SECRET_ACCESS_KEY'] = 'test'
os.environ['AWS_DEFAULT_REGION'] = 'us-east-1'

AWS CodeBuild is a managed CI/CD service that runs your test suites on every commit.

# buildspec.yml
version: 0.2
phases:
  install:
    runtime-versions:
      nodejs: 20
  pre_build:
    commands:
      - npm ci
  build:
    commands:
      - npm run test

A managed service for testing mobile apps on real devices in the cloud. See our Appium Mobile Testing Tutorial for the test-side setup.

• Unit-test Lambda functions (mock with moto)
• Integration test via SAM Local or LocalStack
• End-to-end test against the deployed API
• Performance test with concurrent invocations

A distributed tracing service. Useful for debugging latency and request flow issues across microservices.

• Separate AWS accounts for dev/staging/prod
• IAM roles for least-privilege access
• Reset databases between test runs
• S3 versioning for test data files

import boto3

def test_sqs_receive_message():
    sqs = boto3.client('sqs')
    response = sqs.receive_message(
        QueueUrl='https://sqs.us-east-1.amazonaws.com/123/my-queue',
        MaxNumberOfMessages=1,
        WaitTimeSeconds=10
    )
    messages = response.get('Messages', [])
    assert len(messages) > 0
    assert 'expected payload' in messages[0]['Body']

Same as any other web app — point your tests at the deployed URL. For staging, use the staging API Gateway endpoint. See our Selenium WebDriver Guide.

• Use AWS Secrets Manager for test secrets
• Use IAM roles for service access
• Never commit secrets to git
• Rotate secrets regularly

import boto3

def test_cognito_login():
    client = boto3.client('cognito-idp', region_name='us-east-1')
    response = client.initiate_auth(
        AuthFlow='USER_PASSWORD_AUTH',
        ClientId='your-client-id',
        AuthParameters={
            'USERNAME': 'admin@example.com',
            'PASSWORD': 'Sup3rSecret!'
        }
    )
    assert 'IdToken' in response['AuthenticationResult']

A CI/CD orchestration service that integrates CodeBuild, CodeDeploy, and third-party tools into a release pipeline.

Use k6 or JMeter pointed at the API Gateway endpoint. Use AWS CloudWatch metrics for the server-side view. See our JMeter Tutorial for setup.

• Use cfn-lint for syntax validation
• Use cfn-nag for security best practices
• Deploy to a test stack before prod
• Use Change Sets for safe updates

A monitoring and logging service. Use it to watch Lambda invocations during tests, monitor RDS query performance, set alarms for test failures, and aggregate test metrics.

• Deploy via CI/CD to a test environment
• Run smoke tests against the deployed service
• Monitor via CloudWatch
• Tear down after tests to save costs

See our CI/CD Pipeline Testing Tutorial.

AWS: faster infrastructure provisioning, pay-per-use (can be expensive), more services to test, IAM and security complexity.

On-prem: slower provisioning, fixed costs, fewer services, more direct access control.

• Use t3.micro / t3.small for test instances
• Use LocalStack / moto for local testing
• Tear down test resources after runs
• Use AWS Cost Explorer to monitor

# GitHub Actions
- name: Configure AWS credentials
  uses: aws-actions/configure-aws-credentials@v4
  with:
    role-to-assume: arn:aws:iam::123456789:role/GitHubActionsRole
    aws-region: us-east-1

For broader patterns, see our GitHub Actions for Automation Testing guide.