Added security configuration resource to EMR containers #41716
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a new resource
aws_emrcontainers_security_configuration
is similar in its purpose to existingaws_emr_security_configuration
, but for EMR containers. The reference can be added toaws_emrcontainers_virtual_cluster
- it allows to enable recently added fine-grained access control powered by AWS Lake Formation, as well as encryption in transit, for EMR on EKS.Additionally, failing acceptance tests for
aws_emrcontainers_virtual_cluster
are now fixed and skipped in short-run (until now the provider tried to create virtual cluster before EKS cluster was provisioned or when its network configuration was being updated).Relations
Closes #41712
References
https://docs.aws.amazon.com/emr-on-eks/latest/APIReference/API_CreateSecurityConfiguration.html
https://docs.aws.amazon.com/emr-on-eks/latest/APIReference/API_DescribeSecurityConfiguration.html
https://aws.amazon.com/about-aws/whats-new/2025/02/fine-grained-control-aws-lake-formation-emr-eks/
Output from Acceptance Testing