Ability to expose API via our own custom DNS entry
We would like to expose the APIs created 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 to host our ssl cert that corresponds to our domain
14
votes
Scott
shared this idea
-
Andy O' Connor
commented
The extra effort of implementing a reverse proxy seems like it is against the principles of utilising managed app services. This would be useful.
-
Rishi
commented
Having a custom domain for realm http triggers is important for maintaining a good branded experience. users see the task bar when calls are made to third party services, best to be on a sub domain i.e. api.xxxx.com. Lambda and all other serverless function services allow for this.