AWS Builder Center
Building a Personal Bookmark Manager with AWS Building Blocks

Building a Personal Bookmark Manager with AWS Building Blocks

Learn how to build a simple full-stack bookmark manager using AWS Building Blocks, from backend APIs and persistent storage to frontend integration and end-to-end testing. This hands-on walkthrough focuses on the developer workflow and lessons learned while building with AWS Blocks.

AI | Cloud | Devops
# Building a Personal Bookmark Manager with AWS Building Blocks

## Introduction

AWS Building Blocks provide reusable abstractions that make it easier to build cloud-enabled applications.

In this project, I built a simple **Personal Bookmark Manager** to understand how AWS Building Blocks can be used for backend APIs, persistence, frontend integration, testing, and deployment.

The application supports:

- Create bookmarks
- View bookmarks
- Update bookmarks
- Delete bookmarks
- Persistent data storage

---

## Architecture

```text
User
↓
Frontend (src/)
↓
Typed API
↓
Backend (aws-blocks/index.ts)
↓
AWS Building Blocks
↓
Persistent Storage

The frontend is responsible for the user interface, while the backend handles APIs, authentication, data models, and persistence.



Project Structure

project/
├── aws-blocks/
│ └── index.ts
├── src/
├── test/
│ └── e2e.test.ts
└── package.json

The backend is implemented in  aws-blocks/index.ts , while the frontend lives inside  src/ .



Using Typed APIs

The frontend communicates with the backend using the provided API:
import { api } from 'aws-blocks';

The JSON-RPC transport is handled by AWS Blocks, so there is no need to manually construct RPC requests.



Persistence

The application uses AWS Building Blocks for persistence instead of:
  • Local files
  • In-memory arrays
  • Local databases
This ensures bookmark data can persist beyond a single application process.



Testing

End-to-end tests are located in:
test/e2e.test.ts

Run the tests with:
npm run test:e2e

The main workflows to test are:
Create → Read → Update → Delete

Testing the complete flow helps verify that the frontend, backend, and persistence layers work together correctly.



Development Workflow

The recommended workflow is:
Make changes
↓
Run E2E tests
↓
Fix issues
↓
Test again
↓
Deploy

For faster iteration:
npm run dev

Then:
npm run test:e2e




Deployment

For a sandbox deployment:
npm run sandbox

For a production deployment:
npm run deploy

To remove sandbox resources:
npm run sandbox:destroy

AWS credentials are required for deployment.



Key Lessons

Building this project helped me understand:
  1. How AWS Building Blocks simplify cloud application development.
  1. Why persistent storage is important.
  1. How typed APIs simplify frontend-backend communication.
  1. Why documentation should be read before using a Building Block.
  1. How E2E testing validates the complete application workflow.
  1. How a small project can provide a practical introduction to cloud development.



Conclusion

The Personal Bookmark Manager is a simple project, but it demonstrates the complete application lifecycle:
Design
↓
Build
↓
Persist
↓
Test
↓
Deploy

AWS Building Blocks allow developers to focus on application functionality while using reusable cloud capabilities.
Starting with a small application like this provides a practical foundation for building more advanced cloud-native and AI-powered applications.
Build small, learn the abstractions, test continuously, and improve step by step.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article