12/3/2023 0 Comments Bitnami mean stack apache tutorialUnder the Load Balancer section in AWS instances select “Target Groups” & create a new targe group. In your domain registrar dns settings point the domain to the Route 53 name servers. For now just create an A record and point it to your elastic IP.In AWS create an elastic IP & associate it to your new Bitnami Parse instance.Ĭreate a new hosted zone in Route 53 for your domain. Create a private key if you don’t already have one, download it and keep track of where you put it.If the Bitnami team is stuck reach out here in the Parse community.Īnyway, with all of that said hopefully this helps some of you… I mention this because if you follow this guide and it breaks somewhere along the way instead of going insane for days or weeks trying to figure it out you should probably reach out to them, run their diagnostic tool, check your Apache log, check your Parse log and send them all of the info you can. If you’re a developer you know full well things happen and you can’t catch everything perfectly every time. This is why the guide is for setting up the LiveQuery server on the same instance and NOT going into separating it or the MongoDB or going into Redis caching at all.īitnami saves us TONS of time with these AMI’s & Parse is one of the few API BaaS platforms you can self-host with websocket/Live Query capability. Separating your LiveQuery server and using an external Redis cache is a must for anything production here but again, this is geared towards those that are new to this stack and maybe even new to AWS and just want to get something up and running quickly to start learning it and see if Parse will work for what you need to build. Nginx may very well be the better solution for running websockets but for someone new to the stack the Bitnami AMI is the easiest way to get something setup to start playing with it and get something built quickly. The other frustrating aspect is the little documentation out there for getting websockets working right under secure wss:// is geared towards Nginx and not Apache which the Bitnami AMI uses. The frustrating thing here can be that the few docs out there are for a basic Parse setup using something like Docker OR they’re for back4app which is it’s own thing. I’ve probably hit every brick wall there is to hit on setting this up twice now in the last 2 years so if you run into issues shoot me a reply here and I’ll try to keep an eye on this thread and help if I can. My hope is that this guide will help more developers coming from something like a LAMP stack or a Wordpress dev background get a basic Parse server and live queries running in AWS so you can spend more time developing and writing code and less time beating your head against the wall trying to figure out server-side Apache stuff and SSL under a bastardized configuration like we have here within AWS load balancing. You will need an SSH client like Putty & I recommend WinSCP or something like it to make editing Apache files and the config files a little easier than doing it through the console if you’re not super familiar with something like nano. If you need a more in-depth guide on how to create/setup elastic IP’s, load balancer, using the AWS SSL certificate manager or Route 53 refer to Amazon’s docs or do a quick Google search for this. I’m just giving a quick highlight on setting up the Amazon AWS side and focusing more on the actual Apache and Parse configuration. If you got far enough to find this guide I’m assuming you’re at least a little familiar with the AWS side and at least a little familiar with Node.js. Here’s a quick and dirty “how to” on setting up the Bitnami Parse AMI for SSL HTTPS & websockets WSS using Route 53, with elastic IP and load balancing. BITNAMI PARSE AMI SSL HTTPS & WSS SETUP WITH ROUTE 53 & LOAD BALANCER
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |