Fine-grained access control in DynamoDB - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is fine-grained access control in DynamoDB?

Fine-grained access control lets you set detailed permissions on who can access specific items or attributes in a DynamoDB table, not just the whole table.

intermediate

How does DynamoDB implement fine-grained access control?

It uses IAM policies with condition keys that check item attributes, so you can allow or deny access based on data values in the table.

intermediate

Which IAM condition key is commonly used for fine-grained access control in DynamoDB?

The condition key 'dynamodb:LeadingKeys' is used to restrict access to items with specific partition key values.

beginner

Why is fine-grained access control useful in real life?

It helps protect sensitive data by letting users see or change only the data they are allowed to, like employees accessing only their own records.

advanced

Can fine-grained access control restrict access to specific attributes in DynamoDB items?

Yes, you can use IAM policies with the 'dynamodb:Attributes' condition to allow or deny access to certain attributes within items.

What does fine-grained access control in DynamoDB allow you to do?

A Control access only to the entire table

B Control access to specific items or attributes

C Control access to AWS services outside DynamoDB

D Control network traffic to DynamoDB

Fine-grained access control lets you set permissions on specific items or attributes, not just the whole table.

Which IAM condition key restricts access based on partition key values?

A dynamodb:Select

B dynamodb:Attributes

C dynamodb:LeadingKeys

D dynamodb:ReturnConsumedCapacity

The 'dynamodb:LeadingKeys' condition key is used to restrict access to items with specific partition key values.

What is a common use case for fine-grained access control?

A Allowing users to access only their own data

B Backing up the entire database

C Increasing read capacity units

D Encrypting data at rest

Fine-grained access control is often used to let users access only their own records or data.

Can fine-grained access control be used to restrict access to specific attributes in an item?

A No, it only works at the item level

B No, it only controls table-level access

C Yes, but only for indexes

D Yes, using 'dynamodb:Attributes' condition key

You can restrict access to specific attributes using the 'dynamodb:Attributes' condition key in IAM policies.

Which AWS service is used to define fine-grained access control policies for DynamoDB?

A AWS IAM

B AWS Lambda

C Amazon S3

D Amazon EC2

AWS IAM is used to create policies that define fine-grained access control for DynamoDB.

Explain how fine-grained access control works in DynamoDB and why it is important.

Think about how you can let users see only their own data.

Describe a real-life scenario where fine-grained access control in DynamoDB would be useful.

Imagine a company where employees should only see their personal information.

Practice

1. What is the main purpose of fine-grained access control in DynamoDB?

easy

A. To automatically backup data

B. To speed up query performance

C. To restrict access to specific items based on keys

D. To encrypt data at rest

Solution

1. Step 1: Understand fine-grained access control concept

   Fine-grained access control limits access to individual items or attributes in a DynamoDB table.

2. Step 2: Identify the main purpose

   This control is used to restrict access based on keys, ensuring users see only their data.

3. Final Answer:

   To restrict access to specific items based on keys -> Option C

4. Quick Check:

   Fine-grained access control = restrict by keys [OK]

Hint: Focus on access control by keys, not performance or encryption [OK]

Common Mistakes:

• Confusing access control with encryption
• Thinking it improves query speed
• Assuming it manages backups

2. Which IAM policy condition key is used to enforce fine-grained access control in DynamoDB?

easy

A. dynamodb:LeadingKeys

B. dynamodb:TableName

C. dynamodb:Attributes

D. dynamodb:EncryptionEnabled

Solution

1. Step 1: Identify IAM condition keys for DynamoDB

   DynamoDB uses specific condition keys in IAM policies to control access.

2. Step 2: Match condition key for fine-grained access

   The key dynamodb:LeadingKeys restricts access based on partition key values.

3. Final Answer:

   dynamodb:LeadingKeys -> Option A

4. Quick Check:

   Fine-grained access uses dynamodb:LeadingKeys [OK]

Hint: Remember 'LeadingKeys' controls item-level access [OK]

Common Mistakes:

• Choosing TableName which controls table-level access
• Confusing Attributes with keys
• Selecting unrelated encryption keys

3. Given this IAM policy snippet, which items can the user access?

{
  "Effect": "Allow",
  "Action": "dynamodb:GetItem",
  "Resource": "arn:aws:dynamodb:us-east-1:123456789012:table/Orders",
  "Condition": {
    "ForAllValues:StringEquals": {
      "dynamodb:LeadingKeys": ["user123"]
    }
  }
}

medium

A. All items in the Orders table

B. Only items with partition key 'user123'

C. Items with any partition key except 'user123'

D. No items, because the policy is invalid

Solution

1. Step 1: Analyze the IAM policy condition

   The condition restricts access to items where the partition key matches 'user123'.

2. Step 2: Determine accessible items

   Only items with partition key 'user123' are accessible; others are denied.

3. Final Answer:

   Only items with partition key 'user123' -> Option B

4. Quick Check:

   Condition limits to 'user123' keys [OK]

Hint: Check the LeadingKeys value to find accessible items [OK]

Common Mistakes:

• Assuming access to all items
• Thinking policy denies all access
• Ignoring the condition block

4. You wrote this IAM policy to restrict access to items with partition key 'user456', but users still access other items:

{
  "Effect": "Allow",
  "Action": "dynamodb:GetItem",
  "Resource": "arn:aws:dynamodb:us-east-1:123456789012:table/Orders",
  "Condition": {
    "StringEquals": {
      "dynamodb:LeadingKeys": "user456"
    }
  }
}

What is the likely error?

medium

A. Action should be dynamodb:Query instead of GetItem

B. Resource ARN is incorrect

C. Effect should be Deny instead of Allow

D. Condition should use ForAllValues:StringEquals with an array

Solution

1. Step 1: Check condition syntax for dynamodb:LeadingKeys

   The condition expects an array with ForAllValues:StringEquals, not a single string with StringEquals.

2. Step 2: Understand impact of incorrect condition

   Using StringEquals with a string causes the condition to be ignored, allowing broader access.

3. Final Answer:

   Condition should use ForAllValues:StringEquals with an array -> Option D

4. Quick Check:

   Use ForAllValues:StringEquals and array for LeadingKeys [OK]

Hint: Use ForAllValues:StringEquals with array for LeadingKeys [OK]

Common Mistakes:

• Using StringEquals with a string instead of array
• Incorrect ARN format
• Confusing action types
• Changing Effect to Deny unnecessarily

5. You want to allow users to read only their own orders in a DynamoDB table where the partition key is 'UserId'. Which IAM policy condition correctly enforces this fine-grained access control for user 'alice'?

hard

A. { "ForAllValues:StringEquals": { "dynamodb:LeadingKeys": ["alice"] } }

B. { "StringEquals": { "dynamodb:Attributes": ["alice"] } }

C. { "ForAnyValue:StringEquals": { "dynamodb:LeadingKeys": ["alice"] } }

D. { "StringLike": { "dynamodb:LeadingKeys": "alice*" } }

Solution

1. Step 1: Identify correct condition operator for exact key match

   For fine-grained access, ForAllValues:StringEquals with an array ensures all keys match exactly.

2. Step 2: Evaluate options for correct syntax and semantics

   { "ForAllValues:StringEquals": { "dynamodb:LeadingKeys": ["alice"] } } uses correct operator and array format; others use wrong keys or operators.

3. Final Answer:

   { "ForAllValues:StringEquals": { "dynamodb:LeadingKeys": ["alice"] } } -> Option A

4. Quick Check:

   Exact key match needs ForAllValues:StringEquals with array [OK]

Hint: Use ForAllValues:StringEquals with array for exact user keys [OK]

Common Mistakes:

• Using dynamodb:Attributes instead of LeadingKeys
• Using StringEquals without array
• Using StringLike which allows wildcards