provider/aws: aws_neptune_cluster_instance unexpected state when configuring enhanced monitoring

[mvanzoest-rcd]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.12.28

provider "aws" (hashicorp/aws) 2.70.0

Affected Resource(s)

• aws_neptune_cluster_instance

Terraform Configuration Files

Resource configuration:

# ...

resource "aws_neptune_cluster_instance" "cluster_instances" {
    count = var.instance_count
    identifier = "${local.prefix_instance_name}-${count.index}"
    cluster_identifier = "${aws_neptune_cluster.provisioned_cluster.id}"
    engine = "neptune"
    engine_version = var.engine_version
    instance_class = var.instance_class
    apply_immediately = var.apply_immediately
    auto_minor_version_upgrade = true
    neptune_subnet_group_name = aws_neptune_subnet_group.subnet_group.name
    neptune_parameter_group_name = aws_neptune_parameter_group.instance_parameter_group.name
    port = var.port

    tags = local.tags
    lifecycle {
        # Ensure if recreating instances that new ones are added first
        create_before_destroy = true
    }
    depends_on = [
        aws_neptune_cluster.provisioned_cluster,
        aws_neptune_subnet_group.subnet_group,
        aws_neptune_parameter_group.instance_parameter_group
    ]
}

# ...

Build (only displaying changes):

# aws_neptune_cluster_instance.cluster_instances[0] will be updated in-place
  ~ resource "aws_neptune_cluster_instance" "cluster_instances" {
        # ...
      ~ instance_class = "db.r5.large" -> "db.r5.xlarge"
        # ...
    }

Debug Output

Error: unexpected state 'configuring-enhanced-monitoring', wanted target 'available'. last error: %!s(<nil>)

  on main.tf line 106, in resource "aws_neptune_cluster_instance" "cluster_instances":
 106: resource "aws_neptune_cluster_instance" "cluster_instances" {

Panic Output

N/A

Expected Behavior

Apply should have succeeded.

Actual Behavior

Apply failed.

Steps to Reproduce

1. Create a neptune cluster instance with instance type db.r5.large.

2. Update the instance type to db.r5.xlarge, plan and try to apply.

3. terraform apply

Important Factoids

References

• Similar to provider/aws: aws_rds_cluster_instance unexpected state when configuring enhanced monitoring  #1743

[ghost]

This has been released in version 3.8.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!