AWS Shield for DDoS protection - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable AWS Shield Advanced protection on a resource.

AWS

aws shield create-protection --name MyProtection --resource-arn [1]

Drag options to blanks, or click blank then click option'

Aarn:aws:lambda:region:account-id:function:function-name

Barn:aws:elasticloadbalancing:region:account-id:loadbalancer/app/my-load-balancer/50dc6c495c0c9188

Carn:aws:s3:::my-bucket

Darn:aws:ec2:region:account-id:instance/instance-id

Attempts:

3 left

💡 Hint

Common Mistakes

Using an ARN for unsupported resources like EC2 instances or S3 buckets.

Not providing the full ARN format.

The resource ARN must be for a supported resource like an Application Load Balancer to enable AWS Shield Advanced protection.

2fill in blank

medium

Complete the code to list all protections enabled in AWS Shield.

AWS

aws shield list-[1]

Drag options to blanks, or click blank then click option'

Aresources

Battacks

Cprotections

Dalerts

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'list-resources' which is not a valid AWS Shield command.

Confusing 'attacks' with protections.

The command 'list-protections' lists all the protections enabled in AWS Shield.

3fill in blank

hard

Fix the error in the command to describe a DDoS attack by its ID.

AWS

aws shield describe-attack --[1]

Drag options to blanks, or click blank then click option'

Aattack-id

Battack_id

CattackID

DattackId

Attempts:

3 left

💡 Hint

Common Mistakes

Using camelCase or underscores in parameter names.

Misspelling the parameter name.

The correct parameter name is '--attack-id' with hyphens, matching AWS CLI syntax.

4fill in blank

hard

Fill both blanks to create a Shield protection and specify the resource ARN.

AWS

aws shield create-protection --name [1] --resource-arn [2]

Drag options to blanks, or click blank then click option'

AMyWebAppProtection

BMyBucketProtection

Carn:aws:elasticloadbalancing:region:account-id:loadbalancer/app/my-load-balancer/50dc6c495c0c9188

Darn:aws:s3:::my-bucket

Attempts:

3 left

💡 Hint

Common Mistakes

Using an S3 bucket ARN which is not supported for Shield Advanced protection.

Using generic or unclear protection names.

The protection name should be descriptive like 'MyWebAppProtection' and the resource ARN must be a supported resource like a load balancer ARN.

5fill in blank

hard

Fill all three blanks to create a Shield protection, enable automatic response, and specify the resource ARN.

AWS

aws shield create-protection --name [1] --resource-arn [2] --[3]

Drag options to blanks, or click blank then click option'

AAutoMitigationProtection

Barn:aws:elasticloadbalancing:region:account-id:loadbalancer/app/my-load-balancer/50dc6c495c0c9188

Cenable-automatic-response

Ddisable-automatic-response

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disable-automatic-response' when the goal is to enable it.

Using unsupported resource ARNs.

Using unclear protection names.

Use a descriptive protection name, specify the load balancer ARN, and enable automatic response to mitigate attacks automatically.

Practice

1. What is the main purpose of AWS Shield?

easy

A. To protect AWS resources from DDoS attacks

B. To store data securely in the cloud

C. To monitor user activity on AWS

D. To manage AWS billing and costs

Solution

1. Step 1: Understand AWS Shield's function

   AWS Shield is designed to protect AWS resources from Distributed Denial of Service (DDoS) attacks that try to overwhelm services.

2. Step 2: Compare options with AWS Shield's purpose

   Only To protect AWS resources from DDoS attacks correctly describes AWS Shield's main role as protection against DDoS attacks.

3. Final Answer:

   To protect AWS resources from DDoS attacks -> Option A

4. Quick Check:

   AWS Shield = DDoS protection [OK]

Hint: AWS Shield = DDoS defense for AWS resources [OK]

Common Mistakes:

• Confusing AWS Shield with storage services
• Thinking AWS Shield manages billing
• Assuming AWS Shield monitors user activity

2. Which AWS Shield tier provides additional support and advanced protections?

easy

A. AWS Shield Standard

B. AWS Shield Basic

C. AWS Shield Advanced

D. AWS Shield Premium

Solution

1. Step 1: Identify AWS Shield tiers

   AWS Shield has two main tiers: Basic and Advanced. Basic offers automatic protection, Advanced adds extra features and support.

2. Step 2: Match tier with advanced features

   Only AWS Shield Advanced provides additional protections and 24/7 support.

3. Final Answer:

   AWS Shield Advanced -> Option C

4. Quick Check:

   Advanced tier = extra protection and support [OK]

Hint: Advanced = extra protection and support [OK]

Common Mistakes:

• Confusing Basic with Advanced tier
• Assuming Standard or Premium tiers exist
• Mixing up tier names

3. Given this AWS Shield setup code snippet, what resource is being protected?

aws_shield_protection = {
  "Name": "MyCloudFrontDistribution",
  "ResourceArn": "arn:aws:cloudfront::123456789012:distribution/EDFDVBD632BHDS5"
}

medium

A. An EC2 instance

B. An RDS database

C. An S3 bucket

D. A CloudFront distribution

Solution

1. Step 1: Analyze the ResourceArn

   The ARN contains "cloudfront" and "distribution", indicating the resource is a CloudFront distribution.

2. Step 2: Match resource type to options

   Only A CloudFront distribution matches a CloudFront distribution; others are different AWS services.

3. Final Answer:

   A CloudFront distribution -> Option D

4. Quick Check:

   ResourceArn with cloudfront = CloudFront distribution [OK]

Hint: Look for 'cloudfront' in ARN to identify resource type [OK]

Common Mistakes:

• Assuming EC2 or S3 from ARN without checking
• Ignoring ARN format details
• Confusing resource types

4. You configured AWS Shield Advanced but your Elastic Load Balancer (ELB) is still not protected. What is the likely issue?

medium

A. AWS Shield does not support ELB protection

B. You forgot to associate the ELB with AWS Shield protection

C. You need to enable AWS Shield Basic first

D. AWS Shield only protects EC2 instances

Solution

1. Step 1: Understand AWS Shield Advanced usage

   AWS Shield Advanced requires you to explicitly associate resources like ELB to enable protection.

2. Step 2: Evaluate options for ELB protection

   You forgot to associate the ELB with AWS Shield protection correctly identifies the missing association step. Options B, C, and D are incorrect because ELB is supported, Basic is automatic, and Shield protects multiple resource types.

3. Final Answer:

   You forgot to associate the ELB with AWS Shield protection -> Option B

4. Quick Check:

   Associate resources to Shield Advanced for protection [OK]

Hint: Associate ELB explicitly with Shield Advanced [OK]

Common Mistakes:

• Assuming ELB is auto-protected
• Thinking Shield only protects EC2
• Believing Shield Basic must be enabled first

5. Your company wants to protect a global web application using AWS Shield Advanced. Which combination of AWS services should you protect to ensure best DDoS defense?

hard

A. Protect CloudFront distributions and Elastic Load Balancers

B. Protect only EC2 instances running the web servers

C. Protect S3 buckets storing static content

D. Protect RDS databases and DynamoDB tables

Solution

1. Step 1: Identify key services for global web app delivery

   CloudFront distributes content globally and ELB balances traffic to servers, both critical for DDoS protection.

2. Step 2: Evaluate protection targets

   Protecting CloudFront and ELB covers edge and traffic distribution points. Protecting only EC2 misses edge protection. S3 and databases are less exposed to DDoS.

3. Final Answer:

   Protect CloudFront distributions and Elastic Load Balancers -> Option A

4. Quick Check:

   Shield Advanced protects CloudFront + ELB for best defense [OK]

Hint: Protect edge (CloudFront) and traffic points (ELB) [OK]

Common Mistakes:

• Protecting only backend servers
• Ignoring CloudFront's role
• Trying to protect databases for DDoS