Deploying Serverless Embedding App with AWS CDK, Lambda and Amazon Aurora PostgreSQL

Deploying Serverless Embedding App with AWS CDK, Lambda and Amazon Aurora PostgreSQL

Build a serverless multimodal search engine understanding text and images. Develop AWS Lambda functions, deploy with CDK, and integrate S3 and Aurora Serveless PostgreSQL. Enhance your app's search capabilities and unlock new RAG possibilities.

Elizabeth Fuentes
Amazon Employee
Published Sep 14, 2024
Welcome to Part 2 of our two-part blog series!
In this post, I'll elevate the concepts explored in Part 1 to create a scalable, production-ready solution. Using AWS Lambda functions and AWS CDK, you'll transform our notebook-based prototype into a robust, serverless architecture.
Together, we'll develop AWS Lambda functions for embedding generation and retrieval, leverage AWS CDK for infrastructure-as-code deployment, and integrate with Amazon S3 and Amazon Aurora PostgreSQL for efficient data storage and retrieval. By the end of this tutorial, you'll have a fully functional, serverless multimodal search engine capable of understanding and retrieving both textual and visual content.

โœ… AWS Level: Advanced - 300

Prerequisites:

๐Ÿ’ฐ Cost to complete:

In the second part, you'll construct a Serverless Embedding App utilizing the AWS Cloud Development Kit (CDK) to create four Lambda Functions.

AWS Lambda Functions for Generating Embeddings for Text and Image Files:

To handle the embedding process, there is a dedicated Lambda Function for each file type:

Event to trigger:

Event to trigger:

๐Ÿ’ก Before testing this Lambda Function keep in mind that it must be in the same VPC and be able to access the Amazon Aurora PostreSQL DB, for that check Automatically connecting a Lambda function and an Aurora DB cluster, Using Amazon RDS Proxy for Aurora and Use interface VPC endpoints (AWS PrivateLink) for Amazon Bedrock VPC endpoint.
Event to trigger:

AWS Lambda Funtions to Query for Text and Image Files in a Vector DB:

To handle the embedding process, there is a dedicated Lambda Function for each file type:

Event to trigger:

You can search by text or by image
  • Text event to trigger
Image event to trigger
๐Ÿ’ก The next step is to take the image_path value and download the file from Amazon S3 bucket with a download_file boto3 method.

๐Ÿ’ก Use location and bucketNameto deliver image location to make a query.

๐Ÿš€ Let's build!

The Amazon Lambdas that you build in this deployment are created with a container images, you must have Docker Desktop installed and active in your computer.
Step 1: APP Set Up
โœ… Clone the repo
โœ… Go to:
Step 2: Deploy architecture with CDK.
โœ… Create The Virtual Environment: by following the steps in the README
for windows:
โœ… Install The Requirements:
โœ… Synthesize The Cloudformation Template With The Following Command:
โœ…๐Ÿš€ The Deployment:

๐Ÿงน Clean the house!:

If you finish testing and want to clean the application, you just have to follow these two steps:
  1. Delete the files from the Amazon S3 bucket created in the deployment.
  2. Run this command in your terminal:

Conclusion

In this post, you've demonstrated how to transform a notebook-based multimodal search solution into a scalable, serverless architecture using AWS services. You've walked through the process of developing Lambda functions for embedding tasks, utilizing AWS CDK for infrastructure deployment, and integrating with S3 and Aurora PostgreSQL for efficient data management.
By leveraging these serverless technologies, you can now deploy a robust, production-ready multimodal search engine capable of handling both textual and visual content. This approach not only enhances scalability but also reduces operational overhead, allowing you to focus on improving your search capabilities and user experience.
I encourage you to build upon this foundation, experiment with different embedding models, and explore additional AWS services to further enhance your multimodal search engine. Don't hesitate to share your experiences or ask questions in the comments below. Happy building!
ย 

Any opinions in this post are those of the individual author and may not reflect the opinions of AWS.

Comments