Inspiration
I was recently creating an NFT gallery and chose to load my NFT metadata directly from the collection contract. This left me with a slow ui that wasn't very seamless. This is when I realized that AWS Lambda and DynamoDB could be used to read data from chain and store it in an DynamoDB for a better user experience. Ideally I later update this project to listen for events in contract and update the DB automatically.
What it does
This is a simple demo that uses 3 AWS Lambda functions and a DynamoDB table to illustrate an improved method for loading NFT metadata. The Lambda functions are as follows:
- Grabs NFT metadata from fantom-testnet contract and updates the DynamoDB table with the metadata
- Reads NFT metadata from fantom-testnet contract
- Reads NFT metadata from DynamoDB table
How we built it
I used AWS Lambda, DynamoDB, S3, and API Gateway to create and manage the AWS portion of the codebase. I used thirdwed to create and deploy my fantom-testnet NFT collection as well as using the provider to read the contract and the dashboard to mint the nfts.
What we learned
My goal was to learn more about AWS and web3 development and I believe I did just that. I learned about how the different AWS services interact with eachother on the platform and the different services they all provide. I also learned a great deal about thirdweb's platform and sdk. I will certainly continue to use the platform when building future dapps.
What's next
I will continue to learn about web 3 development and hopefully create more projects in the future.
Built With
- amazon-web-services
- fantom
Log in or sign up for Devpost to join the conversation.