<div dir="ltr"><div>We <a href="https://github.com/mit-probabilistic-computing-project/crosscat/blob/master/crosscat/starcluster_plugin.py" target="_blank">install some system dependencies</a> but don't copy anything sensitive up. Currently, <a href="https://github.com/mit-probabilistic-computing-project/crosscat/blob/master/README_STARCLUSTER.md#creating-an-ami-from-booted-instance">we use ec2cim</a> (ec2-create-image) from ec2-api-tools. Though I just realized that starcluster has its own AMI creation command, <a href="http://star.mit.edu/cluster/docs/latest/manual/create_new_ami.html#creating-an-ebs-backed-ami">ebsimage</a>.<br>
</div><div><br></div><div><div>Is there anything 'special' that should be done before making a customized starcluster AMI pubilc via either of the above methods?</div></div><div><br></div><div>Thanks,</div><div>Dan</div>
<div><br></div><div>PS: my concerns coming from reading <a href="http://alestic.com/2011/06/ec2-ami-security" target="_blank">http://alestic.com/2011/06/ec2-ami-security</a> and not knowing enough about what starcluster does when spinning up an instance to be confident enough to release an AMI.</div>
</div>