[Bug]: Unable to successfully create MSK cluster with explicit default values for vpc connectivity

[eloveeri]

Terraform Core Version

1.4.6

AWS Provider Version

5.14.0

Affected Resource(s)

• aws_msk_cluster

Expected Behavior

When applying, cluster should be created without error

Actual Behavior

Apply fails and subsequent applies report tainted cluster resource

Relevant Error/Panic Output Snippet

│ Error: updating MSK Cluster (Arn:omitted) broker connectivity: BadRequestException: The specified parameter value is identical to the current value for the cluster. Specify a different value, then try again.
│ {
│   RespMetadata: {
│     StatusCode: 400,
│     RequestID: "omitted"
│   },
│   InvalidParameter: "connectivityInfo",
│   Message_: "The specified parameter value is identical to the current value for the cluster. Specify a different value, then try again."
│ }

Terraform Configuration Files

resource "aws_msk_cluster" "cluster" {
  ...
  broker_node_group_info {
    ...
    connectivity_info {
      public_access {
        type = "DISABLED"
      }
      vpc_connectivity {
        client_authentication {
          sasl {
            scram = false
            iam   = false
          }
          tls = false
        }
     }
  }
  ...
}

Steps to Reproduce

When creating an MSK cluster, the aws provider intentionally creates the vpc connectivity info with default values:
https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/kafka/cluster.go#L545

But if the explicitly given values in your terraform resource are actually equal to the default values, the provider will try to update them anyway without checking here:
https://github.com/hashicorp/terraform-provider-aws/blob/main/internal/service/kafka/cluster.go#L593

This is not allowed and results in a 400 (https://docs.aws.amazon.com/msk/1.0/apireference/clusters-clusterarn-connectivity.html).

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[Jonathan-Emmanuel-deel]

Hi, i am also getting this error now, was yours ever resolved?

[magiusdarrigo]

I removed the below block from my MSK tf resource and now it works. Thanks @eloveeri

    connectivity_info {
      public_access {
        type = "DISABLED"
      }

      vpc_connectivity {
        client_authentication {
          sasl {
            iam   = "false"
            scram = "false"
          }
          tls = "false"
        }
      }
    }