Allow flexibility for users to provide their own IAM roles created outside this module.
why
For my use case, enabling encryption on EMR ( see security_configuration variable ) using KMS CMK needs KMS permissions attached to the policies of the service role. This needs to happen before the cluster creation so that cluster can read the certs from s3 & enable at rest encryption using customer specified KMS key.
By allowing this flexibility users can provide their own IAM roles before the cluster is created and enable encryption.
what
why
security_configuration
variable ) using KMS CMK needs KMS permissions attached to the policies of the service role. This needs to happen before the cluster creation so that cluster can read the certs from s3 & enable at rest encryption using customer specified KMS key.references