[Bug]: aws_mq_broker update fails with BadRequestException

[cstclair-tunein]

Terraform Core Version

v1.5.0

AWS Provider Version

5.7.0

Affected Resource(s)

aws_mq_broker

Expected Behavior

When configuring an activeMQ user like so:

resource "aws_mq_broker" "amq" {
  broker_name = "${var.name}_${var.env}"

  configuration {
    id       = aws_mq_configuration.config.id
    revision = aws_mq_configuration.config.latest_revision
  }

  engine_type        = "ActiveMQ"
  engine_version     = "5.15.10"
  host_instance_type = "mq.t2.micro"
  security_groups    = [aws_security_group.allow_internal.id]
  subnet_ids         = [var.subnet_id]

  user {
    username       = var.amq_username
    password       = random_password.amq_password.result
    console_access = true
  }
}

An AMQ user is created that has console access.

Actual Behavior

An error is thrown:

 Error: updating MQ Broker (b-97e317ba-224b-443c-a180-84330470e7b9) users: BadRequestException: Replication user couldn't have console access. [replicationUser] and [consoleAccess] are mutually exclusive parameters.
│ {
│   RespMetadata: {
│     StatusCode: 400,
│     RequestID: "435a3662-40b3-453b-9414-6630542240eb"
│   },
│   Message_: "Replication user couldn't have console access. [replicationUser] and [consoleAccess] are mutually exclusive parameters."
│ }

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

Not relevant.

Steps to Reproduce

• Create a basic AMQ terraform repo
• Attempt to create a user with console access

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[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.

[github-actions]

This functionality has been released in v5.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. Thank you!

[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.