Ability to expose stitch API via our own custom DNS entry
S
Scott Jones
We would like to expose the APIs created in stitch directly to our clients. But we would like them to utilize a domain from our company. At this time we are going to use AWS API Gateway as a reverse proxy.
But all we really would need is the ability for stitch to host our ssl cert that corresponds to our domain
Drew DiPalma
Hi Folks!
As part of our upcoming re-brand of "Stitch" to "Realm" we'll also be migrating our feedback forum and joining the rest of MongoDB at feedback.mongodb.com, as part of that transition, we'll be shutting down this forum. We're still keeping track of this feedback and all of the related comments/discussions, but all future updates will be made here:
https://feedback.mongodb.com/forums/923521-realm/suggestions/40550605-ability-to-expose-api-via-our-own-custom-dns-entry
Drew DiPalma
Drew DiPalma
Merged in a post:
Stitch http Services with custom url
Roberto Dell'Oro
It's possible to change the http service url https://webhooks.mongodb-stitch.com/api/client/v2.0/app/{app-id}/service/{service-name}/incoming_webhook/{webhook-name} , with a custom dns like https:\\{my-project-name}\{service-name}\{webhook-name} in order to make the service available for external calls?
Drew DiPalma
Hi Scott – Thanks for discussing this feedback with us. We have the discussed the ability to expose custom domain and it is on our feature backlog. While we don't have a specific date planned, we are hoping to address later in the year.
S
Scott Jones
Drew DiPalma: great to know
A followup - we will have multiple customers using this. So we will need to direct to a specific stitch endpoint instance. This can be done by the context. Please don't hesitate to contact us when you start reviewing the requirements.