[Bug]: modifying the configuration of an ActiveMQ broker running 5.18 fails with BadRequestException: Broker engine version [5.18.4] is invalid for broker engine type [ACTIVEMQ]

[paulswartz]

Terraform Core Version

1.4.2, OpenTofu 1.6.2

AWS Provider Version

5.61.0

Affected Resource(s)

• aws_mq_broker
• aws_mq_configuration

Expected Behavior

The plan from Terraform does not modify the engine_version, only the configuration.

Actual Behavior

The engine version is configured in Terraform as "5.18", but reported by AWS as "5.18.4". My assumption is that the provider tries to re-send the reported version back to AWS, which then fails.

Relevant Error/Panic Output Snippet

Error: updating MQ Broker (XXX) configuration: BadRequestException: Broker engine version [5.18.4] is invalid for broker engine type [ACTIVEMQ]. Valid values: [5.18, 5.17.6, 5.16.7, 5.15.16].│ {│   RespMetadata: {│     StatusCode: 400,│     RequestID: "cffc2472-2dcf-4062-a2e9-2ded71335611"│   },│   ErrorAttribute: "engineVersion",│   Message_: "Broker engine version [5.18.4] is invalid for broker engine type [ACTIVEMQ]. Valid values: [5.18, 5.17.6, 5.16.7, 5.15.16]."│ }│ │   with module.mq_broker.aws_mq_broker.default,│   on ../modules/ctd-activemq/mq.tf line 11, in resource "aws_mq_broker" "default":│   11: resource "aws_mq_broker" "default" {│ ╵

Terraform Configuration Files

resource "aws_security_group" "example" {
  name = "example"

  ingress {
    description      = "MQTT over TLS"
    from_port        = 8883
    to_port          = 8883
    protocol         = "tcp"
    cidr_blocks      = ["0.0.0.0/0"]
    ipv6_cidr_blocks = ["::/0"]
  }

  egress {
    from_port        = 0
    to_port          = 0
    protocol         = "-1"
    cidr_blocks      = ["0.0.0.0/0"]
    ipv6_cidr_blocks = ["::/0"]
  }
}

# resource "aws_mq_configuration" "example" {
#   description    = "Example Configuration"
#   name           = "example"
#   engine_type    = "ActiveMQ"
#   engine_version = "5.18"

#   data = <<DATA
# <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
# <broker xmlns="http://activemq.apache.org/schema/core">
# </broker>
# DATA
# }

resource "aws_mq_broker" "example" {
  broker_name = "example"

  engine_type                = "ActiveMQ"
  engine_version             = "5.18"
  host_instance_type         = "mq.t3.micro"
  apply_immediately          = true
  auto_minor_version_upgrade = true
  security_groups            = [aws_security_group.example.id]

  # configuration {
  #   id       = aws_mq_configuration.example.id
  #   revision = aws_mq_configuration.example.latest_revision
  # }

  lifecycle {
    ignore_changes = [engine_version]
  }

  user {
    username = "ExampleUser"
    password = "LongPasswordString"
  }
}

Steps to Reproduce

1. Run an initial apply
2. Un-comment the aws_mq_configuration block and the configuration in aws_mq_broker
3. Run another apply

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.

[el-chazmo]

This issue is present with aws v5.63 | checked today.
EDIT: This issue wasn't present when previously running with aws v5.59 | but when testing today, the issue is there.
I assume this is actually an AWS API issue, rather than a provider issue. I have opened a case with AWS and will report back

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

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