Deployment guide: AWS #1534
Replies: 4 comments 4 replies
-
I'll write more later on but with my use case I utilize the following:
I have gone down the route of manually pushing with docker ecs-integration but may reconsider later down the line. I'm also interested in using serverless architecture (lambdas for frontend, and possibly backend?) but want to know the performance implications. Cheers |
Beta Was this translation helpful? Give feedback.
-
I have not deployed Vuendure to AWS but a cool thing to have for AWS is a terraform project template with all the needed components that @cribmove mentioned and plugin infracost to give a cost estimate with a cost policy that is set to fail. that way anyone start a project from that template and just inject their AWs credentials to deploy their Vendure instance and it would give them a cost estimate before deployment. |
Beta Was this translation helpful? Give feedback.
-
My two cents on AWS deployment:
I think running all parts of Vendure in a serverless manner could greatly reduce infrastructure cost Btw I'm working on a Vendure plugin that implements JobQueueStrategy for SQS similar to https://github.com/Pinelab-studio/pinelab-vendure-plugins/tree/master/packages/vendure-plugin-google-cloud-tasks) |
Beta Was this translation helpful? Give feedback.
-
Has anyone managed to actually deploy the whole stack (Database, Server, Worker, AdminUI, Storefront) to AWS? My goal was to use NX monorepo with angular universal and vendure, running everything on AWS Lambda to minimize cost and use SQS for worker to minimize costs, however it seems that its quite tricky to setup. I've seen article for setup for Google cloud, however Google cloud doesn't offer any SQL in free tier which means quite big cost jump from the start (min 40$/month) |
Beta Was this translation helpful? Give feedback.
-
Collecting information / tips / gotchas about deploying Vendure to AWS. The idea is to consolidate into an official guide.
Beta Was this translation helpful? Give feedback.
All reactions