การผสานรวม Lambda และ DynamoDB

Welcome to integrating AWS Lambda with DynamoDB! This combination is a cornerstone for building powerful, serverless backends.

AWS Lambda provides the compute power to run your code without managing servers, while DynamoDB offers a fast, flexible NoSQL database that scales automatically.

Together, they allow you to create data-driven applications that handle create, read, update, and delete (CRUD) operations efficiently.

Before your Lambda function can interact with DynamoDB, it needs permission. This is managed through an IAM Role attached to your Lambda function.

The IAM role must have a policy that grants specific DynamoDB actions, such as:

• dynamodb:PutItem (for creating/updating)
• dynamodb:GetItem (for reading)
• dynamodb:UpdateItem (for modifying parts of an item)
• dynamodb:DeleteItem (for removing items)

Always follow the principle of least privilege: grant only the permissions necessary.

In a Python Lambda function, you'll use the AWS SDK for Python, Boto3, to interact with DynamoDB. First, you need to initialize a DynamoDB client or resource.

The boto3.resource('dynamodb') approach is often preferred as it provides a higher-level, object-oriented interface.

Try running this example to see how to initialize the client:

The put_item() method is used to create a new item or completely replace an existing item in a DynamoDB table.

• If an item with the same primary key already exists, put_item() will overwrite it entirely.
• If no item with that primary key exists, it will create a new one.

This operation is useful when you want to ensure an item exists with specific attributes, or you need to replace all its attributes.

Here's a Lambda function demonstrating how to use put_item() to add or update an item. We'll use a placeholder table name and item details from the event.

Run the code to see the simulated item creation!

To retrieve a single item from a DynamoDB table, you use the get_item() method. This operation requires you to provide the full primary key of the item.

If your table has a simple primary key (only a Partition Key), you'll provide just that value. If it has a composite primary key (Partition Key and Sort Key), you must provide both.

get_item() is highly efficient for direct lookups.

This Lambda function shows how to retrieve an item using its itemId (assuming it's our primary key). The response will contain the item's attributes if found.

Run this example to see how get_item() works.

The update_item() method allows you to modify specific attributes of an existing item without replacing the entire item.

This is more efficient than put_item() if you only need to change a few attributes. It requires an UpdateExpression to specify which attributes to modify and how.

Update expressions can add, set, remove, or delete attributes.

To delete an item from a DynamoDB table, you use the delete_item() method. Similar to get_item(), you must provide the full primary key of the item you wish to remove.

Once an item is deleted, it cannot be recovered through this operation. Be cautious when using delete_item(), especially in production environments.

You need to create a new user profile in your DynamoDB Users table. If a user with the same ID already exists, you want to completely overwrite their old profile with the new data. Which Boto3 method should your Lambda function use?

Great job! You've learned how to integrate AWS Lambda with DynamoDB to build data-driven serverless applications.

• We covered the importance of IAM permissions for secure access.
• You saw how to use the Boto3 SDK to connect from Python Lambda.
• We explored the core CRUD operations: put_item() (create/replace), get_item() (read), update_item() (modify), and delete_item() (remove).

This knowledge is crucial for developing robust serverless backends!