6. Go Live
Your Event Manager app is complete and working locally. Buildpad has already set everything up: your git repository, AWS Amplify CI/CD, and all production credentials. Going live means telling your AI to push your code — Amplify does the rest.
By the end you’ll have:
- Your app deployed and accessible at a public URL
- All connections to your backend and database live
- A link you can share with anyone
Time: About 10 minutes.
Prerequisites
- Completed 5. Add a Dashboard
- Your app is working fully at
http://localhost:3000
How deployment works in Buildpad — When you downloaded the starter, Buildpad pre-configured everything: the git repository, the AWS Amplify CI/CD pipeline, and all your production credentials. Your .env.local already contains the live Amplify URL. You don’t need an AWS account, GitHub account, or access to any console — it’s all managed for you.
Check Your Production URL
Your Amplify URL is already in your .env.local as NEXT_PUBLIC_MICROSERVICE_URL_MAIN. Ask your AI to confirm it:
Say this to your AI:
What is my production URL? Check my .env.local for NEXT_PUBLIC_MICROSERVICE_URL_MAIN.
It looks like: https://main.d1234abcde.amplifyapp.com. Keep this handy — you’ll use it in the next step.
Update Your App’s URL Config
Your project has a file called config/app-urls.ts that needs your production URL. Your AI will update it and push the change.
Say this to your AI:
Update config/app-urls.ts with my Amplify URL from .env.local, then commit and push.
Your AI reads the URL from .env.local, updates config/app-urls.ts, commits, and pushes.
Allow Your URL in the DaaS Backend
Your DaaS backend must explicitly allow your production URL before it will respond to requests from it.
Say this to your AI:
My production URL is [your Amplify URL from Step 1]. Please update the DaaS CORS settings to allow it.
Your AI updates the DaaS CORS configuration to include your production URL using its built-in platform tools.
If you skip this step, the app loads but all data fails silently — lists show empty, forms don’t save. This is the most common deployment issue.
Push Your Code and Deploy
Your starter is on a branch called temporary-local. Tell your AI you’re ready to go live:
Say this to your AI:
I’m ready to go live. Please commit all my changes, push them, and merge to main so Amplify deploys.
Your AI will:
- Create a feature branch from
temporary-local - Commit all your files (credentials are excluded automatically)
- Push the feature branch
- Merge it to
main
The moment main is updated, Amplify starts building automatically. The first build takes 2–3 minutes.
Test Your Live App
Open your Amplify URL and run through the full flow:
- Sign in as Organizer — the dashboard loads with your stats
- Go to the events page — see your published event
- Sign out and visit the events page — events still show (no sign-in required)
- Submit a test RSVP as a new attendee
- Sign back in as Organizer — RSVP count updated
If data doesn’t load → the DaaS CORS wasn’t updated (Step 3). Ask your AI:
The data isn’t loading on my live app. Please check and fix the DaaS CORS settings.
If sign-in fails → something unexpected. Ask your AI:
Sign-in isn’t working on my live app at [URL]. Please help me debug it.
Share Your App
You’re done! Share your Amplify URL. Every time you update your app, just describe the change to your AI — when you’re happy with it locally, your AI commits, pushes to main, and Amplify redeploys automatically.
What Just Happened?
You deployed a full-stack web application to production. AWS Amplify runs your app on a global CDN — it loads fast from anywhere in the world, scales automatically, and redeploys every time main is updated.
Congratulations 🎉
You built and shipped a real web app — from idea to live URL — without writing code. Here’s everything you created:
| Tutorial | What you built |
|---|---|
| 1 | Connected AI IDE to a live backend |
| 2 | Designed a database with events and RSVPs |
| 3 | Built an events page, RSVP form, and admin area |
| 4 | Set up organizer and attendee roles with permissions |
| 5 | Added a live stats dashboard |
| 6 | Deployed to production (this tutorial) |
Keep Going
Want to add more features? Just keep talking to your AI:
- “Add a waitlist feature when max capacity is reached”
- “Send a confirmation email when someone RSVPs”
- “Let organizers export RSVPs to CSV”
- “Add a map showing the event location”
Every feature you can describe, your AI can build.
Explore the Advanced Tutorials
- Dashboard & Analytics — richer stats with charts and date filtering
- Deploying to Production — custom domains, monitoring, and the full git-based deployment workflow