Figure out Wasp's deployment story on AWS

[Martinsos]

Right now we have instructions for deploying Wasp to Fly, Railway, Heroku.

Of course, Wasp can right now be deployed to AWS already, since we give you Docker for server and static files for frontend, but we don't have nice instructions and recommendations on how to best go about it.

Advice we got from AWS pplz:

• Given the containers part, I suggest to look into AppRunner for compute. AppRunner which is an AWS service that provides a fast, simple, and cost-effective way to turn an existing container image or source code directly into a running web service in the AWS Cloud: https://docs.aws.amazon.com/apprunner/latest/dg/architecture.html
• For Database, I suggest to go with RDS as it will allow to have instances as small as db.t4g.micro: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.html
• These 2 could be then put together as a CloudFormation Template which can be shared with the customers. There is sample template which can be used and modified based on your complete infra: https://github.com/aws-containers/hello-app-runner-nodejs
• There is another cost effective option by using Amazon Lightsail which is easy-to-use VPS instances: https://aws.amazon.com/lightsail/. This can be used to deploy managed mySQL instances and containers https://docs.aws.amazon.com/AmazonECS/latest/userguide/create-container-image.html.
• Amazon Lightsail would be the easier and cheaper solution for users that are not experienced with AWS. This would also limit the ‘blast-radius’ in terms of what they are able to provision as it is on a different console than the full AWS Console.
• You could have Amazon Lightsail for ‘non-experienced users’ and AWS App Runner for users with experience in a cloud environment.

[Martinsos]

@infomiho also mentioned sst.dev and Pulumi as interesting options.

[rugs07]

Did you have instructions to deploy it on AWS?

[Martinsos]

Nope, this is waht this issue is about! Would be great to have some.