Thanks sander, would you have an example of how to do this? I'm not sure how I could get my config inside angular to use AWS DNS. The API endpoint is on the same host and the host name is dynamic and they are pretty much a standalone microapp/service so they only talk to themselves, people test on them they get disposed. I don't need to save or get state from a third party service. So I don't think AWS DNS would be suitable here. Maybe I'm wrong?
I realise I can have a multi container service in place as another option but I still would need to configure the Angular service to use the endpoint URL somehow from the containers starting up. Plus thats overkill and costs more money on AWS. 8-) Thanks MB On Wednesday, 26 April 2017 16:43:23 UTC+10, Sander Elias wrote: > > Hi Michael, > > Usually, this is something you arrange inside your webserver, in this > case, it's Nginx I believe. And you use the AWS DNS to hook it up to a > domain name. Then in your app, you can simply inspect the headers if you > need it for some reason in your app itself. > > Regards > Sander > -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
