Azure Container Instance multi-client capable

%3CLINGO-SUB%20id%3D%22lingo-sub-1635426%22%20slang%3D%22en-US%22%3EAzure%20Container%20Instance%20multi-client%20capable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1635426%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20want%20to%20develop%20the%20service%20Azure%20Container%20Instance.%3CBR%20%2F%3EThe%20question%3A%20Do%20we%20need%20an%20Azure%20Container%20instance%20for%20each%20individual%20customer%2C%20where%20a%20container%20runs%20in%20it%20or%20can%3CBR%20%2F%3Eto%20implement%20several%20container%20clients%20in%20one%20ACI.%3CBR%20%2F%3EMeaning%3A%20Is%20it%20possible%20to%20limit%20permissions%20in%20such%20a%20way%20that%20permissions%20can%20be%20assigned%20in%20the%20ACI%3F%3CBR%20%2F%3EThat%20kind%20of%20multi-client%20ACI.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1635426%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Containers%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ECompute%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1643275%22%20slang%3D%22en-US%22%3ERe%3A%20Azure%20Container%20Instance%20multi-client%20capable%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1643275%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F782166%22%20target%3D%22_blank%22%3E%40Horst_Wutscher_Blogg%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20would%20be%20the%20Workload%3F%3C%2FP%3E%3CP%3EShould%20these%20Containers%20be%20Internet%20Facing%20or%20for%20internal%20Network%20Usage%3F%3C%2FP%3E%3CP%3ESo%20are%20they%20attached%20with%20a%20Public%20IP%20or%20with%20a%20internal%20Network%20IP%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20the%20Customers%20also%20need%20Access%20to%20those%20Resources%20in%20Azure%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20from%20a%20cost%20view%2C%20having%20more%20then%20one%20ACI%20would%20not%20be%20a%20Problem%2C%20as%20you%20pay%20for%20what%20you%20use%2C%20so%20have%20a%20ACI%20with%202%20Container%20or%202%20with%20one%20Container%20should%20cost%20nearly%20the%20same.%20I%20would%20recommend%20the%20use%20of%20two%20instances%2C%20one%20for%20each%20customer%20instead%20of%20crossusage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20Regards%2C%20Peter%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We want to develop the service Azure Container Instance.
The question: Do we need an Azure Container instance for each individual customer, where a container runs in it or can
to implement several container clients in one ACI.
Meaning: Is it possible to limit permissions in such a way that permissions can be assigned in the ACI?
That kind of multi-client ACI.

2 Replies

Hi @Horst_Wutscher_Blogg,

 

What would be the Workload?

Should these Containers be Internet Facing or for internal Network Usage?

So are they attached with a Public IP or with a internal Network IP?

 

Will the Customers also need Access to those Resources in Azure?

 

I think from a cost view, having more then one ACI would not be a Problem, as you pay for what you use, so have a ACI with 2 Container or 2 with one Container should cost nearly the same. I would recommend the use of two instances, one for each customer instead of crossusage.

 

Kind Regards, Peter

Hello @Peter_Beckendorf ,

 

we would like to implement our ACIs with private / internal IPs.

 

Yes, the internal company customers should get access to Azure Portal.

 

Yes, one reason is costs. We think, if we deploy one ACi for more internal customers, its is cheaper and also not so much governance and work to do.

 

Horst