Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
AlmondSauce841870dSo many ways to do one thing in AWS these days.
The "classic" approach is to grab an EC2 instance to run your app (frontend & backend), load everything you need on that, use S3 for file storage, and away you go (maybe with some cloudfront / route53 config facing it, but that's just decoration per-se.) Don't forget you'll need to maintain that EC2 instance yourself, but this is likely the easiest if you're getting started.
The "modern" approach is generally to spec out an EKS instance and use K8s with their ECS / Fargate service, using one of their storage services (RDS, Dynamo, etc.) for persistence. But that's almost certainly going to work out more expensive and complicated. Advantages are no need to maintain EC2 instances, and K8s brings easy redundancy, auto-scaling, update management and trivial horizontal scaling. That's the "gold standard" I generally look to for spinning up something in AWS these days.
AlmondSauce841870dThere's many other options of course - you could go elastic beanstalk, you could go lambda (aka "serverless"), you could probably go with a hundred other more esoteric services that I know nothing about. But the above two are the main ones I generally recommend.
Pricing is pretty transparent for all services, but how much it costs can vary from "almost nothing" to "thousands a month" depending on how big an instance you choose, how many instances you choose, how much traffic you have, etc. Best thing is to put some numbers together on the above for different scenarios (peak traffic, low traffic, normal traffic etc.), look up the prices and then work out costs from that.
cervantes0169870dThanks everyone for all of the help, it's much appreciated I'm studying their plans now lol.
Once again thanks to all for helping out.