Join our community of over 8,800 readers delving into AWS. We highlight real-world best practices through easy-to-understand visualizations and one-pagers. Expect a fresh newsletter edition every two weeks.
Share
How We've Built Our CloudWatch Book Video Platform 🎥
Published 5 months ago • 3 min read
⌛ Reading time: 10 minutes
🎓 Main Learning: Building a Serverless Platform With SST, Lambda & Next.js
In this post, we want to guide you through our complete setup for our custom video platform.
Our CloudWatch Book's Video Section
This starts from the purchase to actually accessing our custom build video-access platform.
Overview about our CloudWatch Book Landing Page & Video Platform Architecture
We'll explain why we decided against a third-party solution for our video section and built something on our own with SST, Next.js, Lambda, and Vimeo.
Preface
We launched our first educational book about AWS, AWS Fundamentals 📙, at the start of 2023. While it includes many visuals, it neither comes with deployable code nor hands-on video tutorials.
For our second book, The CloudWatch Book 📕, we aimed higher. The book comes with hands-on application that can be deployed on AWS. Along this, there are videos where we explore CloudWatch features 🎥.
For delivering videos, we looked for the most convenient way for us and the users.
Why Custom & Serverless?
We opted for a custom solution to avoid restrictions and maintain full control, integrating seamlessly with 📨 ConvertKit and LemonSqueezy. A Serverless approach was ideal for us - we know the services very well and Lambda comes with basically zero operations and low-to-zero costs (in our case).
Overview of Technologies
We utilized a modern tech stack:
SST: A framework for building serverless applications on AWS, simplifying deployments and management immensely. Deploying a Lambda function with an API Gateway? Not more than a few lines of code. SST will take care of the heavy lifting.
Next.js: A React framework for fast, user-friendly web applications, natively supported by SST. Also enables you to run code on the server side. This means you can access AWS resources without creating APIs. Next.js will take care of this and SST will deploy the server-side code to Lambda@Edge functions.
Architecture Overview
Our architecture includes:
Customer Purchase Flow: Users buy the package on cloudwatchbook.com. A successful payment triggers a webhook-based Lambda function to generate a personalized access token stored in DynamoDB and ConvertKit.
Personalized Video Access Link Notification: The token links to the user’s purchase, allowing unique access to video content. An automated email is sent with the access link.
Video Platform Access and Content Delivery: Users access the platform with a validated token, loading embedded Vimeo links.
We’ve managed to keep AWS costs close to zero, only paying for Vimeo. 🙃
Building the Platform
Let's dive into these three main components that made up everything from purchasing the book to accessing our videos.
Customer Purchase Flow
After the payment completes in LemonSqueezy, we'll receive an order_created webhook to our Lambda function.
Purchase Flow
This function will take care of storing the necessary information both on ConvertKit side, as well as in our own DynamoDB table.
Storing Customer Data received from LemonSqueezy
We'll generate an access token which can be later used to access the video section.
Personalized Video Access Link Notification
We send an email with the personalized link using ConvertKit’s Visual Automation based on custom fields and a uniquely assigned tag in the previous step.
Sending out the Links to access our Platform
The subscriber will automatically join the flow and receive the email with the link that contains the personalized access token.
Video Platform Access and Content Delivery
Users access the platform with their link and we'll validate their token via a Lambda function and the data in our DynamoDB table, which will finally retrieve the video links from Vimeo.
Actually accessing our Platform
What we'll also do: we track views and follow up with users who haven’t accessed content within 30 days. This way, we can get feedback if there's an issue with the platform or if the content is not as expected.
Where to Go from Here
We’re thrilled with our custom platform, which allows for future enhancements like:
Motivational animations for video completions.
Custom “completion badges” for users.
Feedback forms for user issues.
... and much more.
Conclusion
That's already it! 🎉
We shared how we built a serverless video platform for our CloudWatch Book using SST, Next.js, ConvertKit, LemonSqueezy, and Vimeo. This custom solution provides control, flexibility, and cost-effectiveness.
We encourage you to explore building your own serverless platform.
Even though we still reside in a "buy before build" mindset, many custom setups do make sense to connect the dots between multiple platforms!
P.S.: We're on the AWS Community Days in Romania! 🇷🇴 Sandro will be on stage to give a talk about Hashnode's journey with GraphQL 🗣️ If you're also there in person, please come and talk to us! 💛
Join our community of over 8,800 readers delving into AWS. We highlight real-world best practices through easy-to-understand visualizations and one-pagers. Expect a fresh newsletter edition every two weeks.
Hey Reader 👋🏽 This issue will be about a recent real-world experience that just went off right with the new year! 🎉 Once upon a time... 🦄 It all started in September 2024 where Edgio, the main CDN provider we used for one of my large enterprise projects, filed for bankruptcy. Edgio was natively integrated into Azure, allowing you to use it without leaving the Azure ecosystem. It also featured a powerful rules engine (allowing for all kinds of conditions, redirects and rewrites) and didn’t...
⌛ Reading time: 13 minutes 🎓 Main Learning: How to Run Apps on Fargate via ECS 👾 GitHub Repository ✍️ Read the Full Post Online 🔗 Hey Reader 👋🏽 When building applications on AWS, we need to run our code somewhere: a computation service. There are a lot of well-known and mature computation services on AWS. You’ll often find Lambda as the primary choice, as it’s where you don’t need to manage any infrastructure. You only need to bring your code - it’s Serverless ⚡️. However, more options can be...
⌛ Reading time: 10 minutes 🎓 Main Learning: Running Postgres on Aurora DSQL with Drizzle 👾 GitHub Repository ✍️ Read the Full Post Online 🔗 Hey Reader 👋🏽 With re:Invent 2024, AWS finally came up with an answer to what many people (including us) asked for years: "What if there were something like DynamoDB but for SQL?" With Amazon Aurora DSQL, this is finally possible. It’s not just a “scales-to-zero” solution like Aurora Serverless V2. It is a true distributed, serverless, pay-per-use...