I have the following situation:
There is a docker container I use to authenticate myself to a Web API Gateway (ibeam, see here). The authentication is done through https://localhost:5000 (but can be changed). It is kind of a server.
I have a bunch of scripts which uses the web api through https://localhost:5000/v1/api endpoint to receive data after authentication and analyse it.
What would be the most cost efficient way to host this setup in Azure in a way that it can be scheduled (authentication through the “server” and then data retriever + analysis)?
What I have already tried:
-
Hosting the authentication container in an Azure Container Instance (ACI), forwarding port 5000 out and use the API endpoints through the https://public.ip.of.ACI:5000/v1/api endpoint from a VM/Web App/Azure Function. Problem: even though I make the authentication, it is not “forwarded” through the open port (do not understand why) and cannot use the endpoint in the VM/Web App/Azure Function (which one should I use btw.?)
-
Hosting everything on a VM, which is turned on by a scheduled Azure function (should be doable, see here) and trigger the authentication + data retriever + analysis by a service or like that. <- doable, but I guess there is a more elegant, more “azuric” way to reach my goal.
Is it possible to host a web app which runs two docker containers depending from each other (e.g. second docker container does it’s job after the authenticator container is done) controlled by a docker-compose or so (see here)?
Should I put the authenticator server container to ACI and schedule a Web App/Function App using this container? How could I do that?
Or is there anything else in your mind?
I am kind of lost between the possibilities in Azure and don’t know what would be the best as I don’t have much experience with servers and so. Any advice is appreciated!
Thanks a lot!