Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate Custom Configurations for Core and Master Instance Groups #91

Open
GAUTAM-CB opened this issue Dec 19, 2024 · 0 comments
Open

Comments

@GAUTAM-CB
Copy link

Describe the Feature

I am reaching out to request a feature enhancement for the AWS EMR module. Currently, when managing EMR clusters via Terraform, both the master and core instance groups are provisioned through the aws_emr_cluster resource. However, it is not possible to apply custom configurations(configurations_json) to these instance groups separately, as configurations are applied at the cluster level, impacting both instance groups.

This limitation reduces flexibility for managing distinct configurations for core and master groups in the same EMR cluster. It would be greatly beneficial if Terraform could allow specifying custom configurations for both core and master instance groups independently, similar to the ability to create separate task instance groups with distinct configurations.

Expected Behavior

Separate configuration Json for core and master instance group

Use Case

Yes, the feature request is directly related to a challenge we are facing. Currently, there is a limitation within the Terraform AWS EMR module that prevents us from specifying separate custom configurations for the core and master instance groups within an EMR cluster.

Describe Ideal Solution

I would like the Terraform AWS EMR module to support the ability to specify custom configurations for the core and master instance groups separately within the aws_emr_cluster resource. This would allow us to apply different configurations for each instance group independently, providing greater flexibility in managing EMR clusters.

Alternatives Considered

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant