This archive was generated by
It really depends on what you're looking to do. Are these PAYING CUSTOMERS who you MUST (contractually) keep apart? Or are they members of a team and you just want them to keep from accidentally hurting each other? You'll have to work throught the ramifications of the answers to these questions yourself, and probably learn about IAM User in the process. I DON'T use IAM User generally, except in a casual "team" world, so can't really answer your question in any detailed way.
From: Ramon Ramirez-Linan [mailto:rlinan_at_navteca.com]
Sent: Thursday, November 13, 2014 10:10 AM
To: MacMullan, Hugh
Subject: Re: [StarCluster] User security
We only have the option of using the separate IAM users.
What is a good way of doing it? Limit access to EC2 based on tags? or what other options ?
On Wed, Nov 12, 2014 at 5:38 PM, MacMullan, Hugh <hughmac_at_wharton.upenn.edu<mailto:hughmac_at_wharton.upenn.edu>> wrote:
Separate IAM User accounts, or separate AWS accounts with Consolidated Billing are good approaches.
> On Nov 12, 2014, at 17:21, "Ramon Ramirez-Linan" <rlinan_at_navteca.com<mailto:rlinan_at_navteca.com>> wrote:
> What is the best way to implement security between the users so they can not stop each others clusters (stop, detroy see, etc)
> I am having the issue that when any user run starcluster listclusters they see all the clusters currently running on the AWS account.
> Also I am curious about how starclusters find the information of current running clusters
> StarCluster mailing list
Received on Thu Nov 13 2014 - 10:18:22 EST