Security concerns with making a customized starcluster AMI public

From: Dan Lovell <no email>
Date: Tue, 4 Feb 2014 14:45:03 -0500

We install some system
dependencies<https://github.com/mit-probabilistic-computing-project/crosscat/blob/master/crosscat/starcluster_plugin.py>but
don't copy anything sensitive up. Currently, we
use ec2cim<https://github.com/mit-probabilistic-computing-project/crosscat/blob/master/README_STARCLUSTER.md#creating-an-ami-from-booted-instance>(ec2-create-image)
from ec2-api-tools. Though I just realized that
starcluster has its own AMI creation command,
ebsimage<http://star.mit.edu/cluster/docs/latest/manual/create_new_ami.html#creating-an-ebs-backed-ami>
.

Is there anything 'special' that should be done before making a customized
starcluster AMI pubilc via either of the above methods?

Thanks,
Dan

PS: my concerns coming from reading
http://alestic.com/2011/06/ec2-ami-security and not knowing enough about
what starcluster does when spinning up an instance to be confident enough
to release an AMI.
Received on Tue Feb 04 2014 - 14:45:29 EST