Personally I'd build a single AMI with a startup script that extracts any configuration for things like which partition group the instance is in from user data (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-insta...)
Thank you. It seems to me like you'd need variation in your Terraform file to specify that. How do you do that? The DSL doesn't have control structures.
Do people usually just build k AMIs if they have k partition groups that they want to serve?
For a sort of simplistic version of the problem, imagine the data was splittable into 6 partitions and you hashmod the partitions across 3 groups. So instances in group 1 will serve partitions 0,4; instances in group 2 will server partitions 1,5; and so on. Does one build an AMI for group 1, one for group 2, and one for group 3? Does one provide configuration informing which group a specific node should serve through other means? Or does one stick that in a Terraform definition?
0: https://www.project-voldemort.com/voldemort/design.html