I’m a Computer Science student in Algeria, currently working on Alimni Aya, a platform for Quran schools.
The project uses a familiar web stack:
• React for the frontend
• Node.js and Express for the backend
• Prisma as the ORM
• PostgreSQL for the database
Until now, my focus has mainly been application development. Joining AWS Student Rewards gave me a good reason to look at the infrastructure side of the project more seriously.
Instead of learning AWS only through theory, I want to use my existing project as a practical learning environment.
What I’m looking at first
The first question I’m exploring is simple:
What should a student project actually move to AWS, and what should stay on a simpler platform?
My current deployment uses Vercel, Neon, and Render. This setup is convenient for development and small projects.
AWS introduces a much larger set of options.
For example:
• EC2 gives me control over the server environment.
• RDS provides managed relational databases.
• S3 can handle object storage.
• CloudFront can distribute static and cached content.
• IAM provides more granular access control.
• CloudWatch can provide monitoring and observability.
The challenge is not learning what each service does.
The challenge is learning when to use each service.
A simple example: PostgreSQL
Alimni Aya uses PostgreSQL with Prisma.
That makes RDS particularly interesting to me because it keeps the relational database model I already understand while adding AWS-managed infrastructure.
But moving from a hosted PostgreSQL provider to RDS is not simply changing a connection string.
I need to think about:
• Database networking
• Connection management
• Backups
• Security groups
• Credentials and secrets
• Monitoring
• Costs
• Prisma connection behavior
This is the type of AWS knowledge I want to develop.
Architecture before migration
I’m deliberately not migrating the project just because AWS has a service for everything.
My current goal is to understand the architecture first.
If a free or low-cost managed service already solves a problem well, replacing it may add complexity without providing meaningful value.
On the other hand, learning how the AWS equivalent works gives me useful knowledge for larger projects later.
My AWS learning path
I recently started the AWS AI Practitioner learning path.
I’m particularly interested in the intersection between:
• Web development
• Cloud infrastructure
• AI services
• PostgreSQL
• Practical software architecture
I plan to document what I learn by applying it to real problems instead of writing purely theoretical summaries.
What would you choose?
If you were building a student application with React, Node.js, Prisma, and PostgreSQL, which AWS service would you learn first?
Would you start with EC2, RDS, S3, Lambda, or something else?
I’m interested in hearing how other builders approached their first AWS project.
Loading article