Keith, Great news you got platform set for everyone on cloud and future deployments.
My vote goes to Nginx or nginx plus - it never fails. I have been using it for 6-7 years and it is the most reliable and flexible and beautiful piece of software I have ever used. I can offer some help - to start with you probably want to think about a test driven installation, configuration and the setup of each instance for each client on EC2 with AWS cloud formation automation for continuous delivery. I found NGINX more robust and flexible model than AWS ELBs and we do not lock into AWS ecosystem - because nginx is so light weight and powerful. What you want to do is setup a domain with wildcard ssl and each client get unique sub domain - say UUIDofclient.synergistcloud.com Then automate everything then onwards!!! Ideal Linux is Redhat/Centos with reboot less servers with auto patches. Ubuntu is also very ideal platform but I know Redhat/Centos reasonably well. Also with Ansible being part of Redhat now you pretty much can automate the entire server setup, testing, compliance, deployment etc. I am going to release new version of Deploy4D competent soon with DevOps tools which has auto update client for keeping all installations up to date - which should also help in this project. Let me know if you wish to discuss about it more with me. Cheers / Balinder On Wednesday, 14 September 2016, Keith White <kwh...@synergist.co.uk> wrote: > Hi all > > We've now got most of Synergist into a web user interface, after a > considerable effort and a couple of false starts. > > We decided to use an AWS EC2 instance for each customer, some time ago. > The integration with S3 has been done (thanks to Bruno Legay for his help!). > > Each customer will be given a subdomain name from "synergist.cloud". The > primary domain is being transferred to AWS Route 53 for convenience. > > As much of the setup for each customer instance & routing needs to be > automated to keep consistency and avoid configuration errors. > > Most customers will be UK based, but if we start to sign up customers in > other regions, we'll want their instance and route to be local to them. > > So now I'm looking at the configuration of the domain and reverse proxies > to front the instances and to handle the SSL piece. The fronting/SSL needs > to have reasonable resilience to avoid a single point of failure. > > So far I've looked at:- > > NGINX Plus. For production environments this needs Linux/Unix. We know > NGINX reasonably well but we have almost zero experience of Linux, so this > would be be a challenge. > > HAProxy. Again Linux, but they offer config & training services. > > Microsoft IIS. I've got a working configuration using URL Rewrite which > seems to work. I've yet to look at automating the configuration. > > I wondered if anyone has any advice, experience or opinion as to possible > approach? > > Many thanks > > Best regards > > Keith White > Synergist Express Ltd, UK. > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com <javascript:;> > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
