AWS hosting of SPA Web App
The AWS answer would be to use appropriate services for each component.
E.g. Put the database on an RDS - they have multiple choices. Deploy the front-end using Fargate and Lambda.
There are 2 issues to consider:
1. The learning curve.
Getting up to speed on AWS technology - and keeping up with them as they make minor tweaks that break lagacy deployments - can get very expensive, time-wise.
OTOH, once you're an expert at these technologies, you can leverage them with amazing results.
2. The costs:
While you develop you will be using the free-tier mostly, and the costs will be minimal.
Once you move into production, you have have to start using &quot;real&quot; machinery, and even if you don't, most services have an expiration for their free tier: 12 months and/or a certain amount of usage.
At that point the costs start ballooning. from small-change to 3 or even 4-figure numbers for a small installation.

The other approach is to do it the way you'd do it without AWS.
You didn't give me much details, but if you're deploying something simple, you may want to spin up an EC2 instance, install a LAMP server and use it for both front &amp; back end.
You can then use the Lifecycle Manager to back up the entire machine daily.
However, if you have to scale this up in a big way, you'll have to start from scratch.

So, what do you choose?
The answer depends on your resources: time, money and manpower, as well as how you see this growing from a one-off project to a long term heavily used installation that needs redundancy, load balancing and the ability to scale dynamically.
You could also look at something like AWS Beanstalk, which is easier to implement and redeploy, but not as dynamic, as their serverless approach.