#Port mapping with MAU?!

2 messages · Page 1 of 1 (latest)

small nymph
#

I've spent easily the better half of the week trying to deploy my Nest backend to AWS. Fargate or EC2 - I'm not to worried at the point. I just want it to work.

Using the default port 3000 in my nest application and when setting up a new application in the MAU portal works fine. Everything gets deployed. However - the port mapping in AWS is still 3000:3000. Am I being a complete idiot?

Going to the URL provided by the portal gives me the "Mau placeholder | NestJS - A progressive Node.js framework" after I've deployed my nest application.

Am I missing something? The documentation isn't that great. 😕

dawn lichen
#

We don't provide MAU support on the discod channel. We as volunteers don't have access to it, as it is a commercial product developed exclusively by Trilon. If you need support, please use the contact mail on their website: https://www.mau.nestjs.com/

Someone from the community, who used it might still give you some insights though.

Deploy with Mau | NestJS - A progressive Node.js framework

Provision and manage your infrastructure on AWS without the hassle and extra DevOps work. Deploy your NestJS application with Mau in minutes and focus on what matters most..