: DNS/Routing Issue - How to Provide Immediate Access to a Newly Created Instance Background: SaaS company here. Each of our customers is going to receive their own private ec2 instance containing
Background: SaaS company here. Each of our customers is going to receive their own private ec2 instance containing their own copy of one or more of our apps. The plan is for customers to be able to sign up on our site and automatically launch the ec2 instance via the AWS ec2 api.
My question is: How can we begin routing them to their instance as soon as it's been set up? (I don't want to give non-tech people an IP address and have to explain to them that they need to use it until their custom subdomain propagates.)
As far as urls go, either of these two methods would be acceptable (but I'd prefer the first):
ourcompany.com/{appName}/{customerName} {app}-{customerName}.ourcompany.com
How would I go about routing traffic via one of these two URL set-ups to the customer's newly launched ec2 instance?
More posts by @Smith883
1 Comments
Sorted by latest first Latest Oldest Best
For the first alternative, use Alt-SVC headers and prepare your SaaS customer instances to accept requests under the domain names and urls that you proposed. Tell your customer to try the new instance using a reasonably modern browser.
(At the time of this writing,j only Firefox has reasonably complete Alt-SVC support. Chrome has filled bug: bugs.chromium.org/p/chromium/issues/detail?id=615413 and they seem to be working on it).
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.