Only recommend amplify for frontend, not backend (#71)

Author: josephine-njooi

src/content/docs/tech-recommendations/infrastructure.md

@@ -7,13 +7,11 @@ wip: true
 
 ### Amplify
 
-**Your go-to option for most projects**
+**Your go-to option for most frontends**
 
-Think of Amplify as the "easy button" for hosting full-stack apps. You've got a React frontend and Node.js backend? Amplify handles it all. Just connect your GitHub repo and it automatically deploys your app, sets up SSL, distributes it via CDN, and even creates preview environments for your pull requests. It's very little DevOps work, it just needs to be configured behind the right firewalls. Submit an [Operations Request Ticket](https://github.com/newjersey/internal-ops/issues/new?template=request_new_website_webapp.yaml) to get started.
+Think of Amplify as the "easy button" for hosting frontend apps. Whether your frontend is static Vite or full stack NextJS, Amplify handles it all. Just connect your GitHub repo and it automatically deploys your app, distributes it via CDN, and even creates preview environments for your pull requests. It's very little DevOps work, and just needs to be configured behind the right firewalls. Submit an [Operations Request Ticket](https://github.com/newjersey/internal-ops/issues/new?template=request_new_website_webapp.yaml) to get started.
 
-**Use Amplify when**: You're building a normal web app and don't have weird requirements. Start here unless you have a specific reason not to.
-
-**Skip Amplify when**: You need to tinker with server configurations, have complex networking stuff like VPCs, or you're not actually building a web app (like if you're doing batch processing or background jobs).
+**Use Amplify when**: You're building a normal frontend app and don't have weird requirements. Start here unless you have a specific reason not to.
 
 ### Lambda