<div dir="ltr">We only have the option of using the separate IAM users.<div>What is a good way of doing it? Limit access to EC2 based on tags? or what other options ?</div><div><br></div><div>Ramon</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 12, 2014 at 5:38 PM, MacMullan, Hugh <span dir="ltr"><<a href="mailto:hughmac@wharton.upenn.edu" target="_blank">hughmac@wharton.upenn.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Separate IAM User accounts, or separate AWS accounts with Consolidated Billing are good approaches.<br>
<br>
-Hugh<br>
<br>
> On Nov 12, 2014, at 17:21, "Ramon Ramirez-Linan" <<a href="mailto:rlinan@navteca.com">rlinan@navteca.com</a>> wrote:<br>
><br>
> Hello,<br>
><br>
> What is the best way to implement security between the users so they can not stop each others clusters (stop, detroy see, etc)<br>
><br>
> I am having the issue that when any user run starcluster listclusters they see all the clusters currently running on the AWS account.<br>
><br>
> Also I am curious about how starclusters find the information of current running clusters<br>
><br>
> Thanks<br>
><br>
> Ramon<br>
> _______________________________________________<br>
> StarCluster mailing list<br>
> <a href="mailto:StarCluster@mit.edu">StarCluster@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/starcluster" target="_blank">http://mailman.mit.edu/mailman/listinfo/starcluster</a><br>
</blockquote></div><br></div>