aws_emr_cluster instance_group not recognized

[ghost]

Unable to configure aws_emr_cluster using the new instance_group syntax. Upgraded from 0.9.8 yesterday to have access to the new EMR features, so it could be operator error or local configuration error.

$ terraform -v
Terraform v0.10.6

Affected Resource(s)

• aws_emr_cluster

Terraform Configuration Files

Example gist taken from the docs, including instance_group definition in #1071:
EMR Cluster example with instance_group

Debug Output

$ terraform init

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...
- Downloading plugin for provider "aws" (0.1.4)...

Terraform has been successfully initialized!

$ terraform plan
2 error(s) occurred:

* aws_emr_cluster.emr-test-cluster: "master_instance_type": required field is not set
* aws_emr_cluster.emr-test-cluster: : invalid or unknown key: instance_group

Expected Behavior

Should have provisioned a cluster with multiple MASTER and CORE nodes.

Actual Behavior

Complained about not recognizing the instance_group key, even though that feature should be available in v0.1.4.

Steps to Reproduce

1. Copy example gist to its own directory and configure S3 bucket for one with write access
2. terraform init
3. terraform plan

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

• Enable EMR cluster configuration through the InstanceGroup param #1071

[e-carlin]

+1 I am running into the same issue.

Using the test from https://github.com/apetresc/terraform-provider-aws/blob/500644ae59ff13ee86b6209ef7e163049d417739/aws/resource_aws_emr_cluster_test.go
I also run into the same issue

I came across the test from here #1071

[e-carlin]

I ended up resolving the problem myself. The update to the Terraform AWS Provider was release on 9/27. I hadn't run terraform init since then so I had an outdated version of the provider. Deleting the .terraform directory and running terraform init resolved it.

@kh360 ^

[bflad]

This was previously released in version 1.0.0 of the AWS provider and has been available in all releases since. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.