[Bug]: Modifying the configuration of a RabbitMQ broker running 3.13.7 fails with BadRequestException: Broker engine version [3.13.7] is invalid for broker engine type [RABBITMQ]

[michaelbauerinc]

Terraform and AWS Provider Version

Terraform Core Version

Terraform v1.7.5

AWS Provider Version

v5.97.0

Affected Resource(s) or Data Source(s)

aws_mq_broker

Expected Behavior

Terraform should allow us to configure a broker currently running RabbitMQ version 3.13.7 without error, especially given that the engine is already on that version. Per #38708, a similar issue for ActiveMQ was reportedly fixed in AWS provider v5.68.0.

Actual Behavior

Attempting to set engine_version = "3.13.7" fails, claiming the patch version cannot be specified and that only 3.13 is valid.

Relevant Error/Panic Output

Error: creating MQ Broker (***-rabbitmq): operation error mq: CreateBroker, https response error StatusCode: 400, RequestID: 63fa9315-442b-4755-a895-fd5a379dd6a3, BadRequestException: Broker engine version [3.13.7] is invalid for broker engine type [RABBITMQ]. Valid values: [3.13]

Sample Terraform Configuration

Click to expand configuration

resource "aws_mq_broker" "rabbitmq" {
  broker_name                = local.name
  engine_type                = "RabbitMQ"
  engine_version             = "3.13.7"
  host_instance_type         = "mq.t3.micro"
  apply_immediately          = true
  auto_minor_version_upgrade = true
  deployment_mode            = "SINGLE_INSTANCE"

  subnet_ids      = [var.private_subnets[0]]
  security_groups = [module.security_group[0].security_group_id]

  user {
    username = var.rabbitmq_user
    password = var.rabbitmq_password
  }

  logs {
    general = true
  }

  encryption_options {
    use_aws_owned_key = true
  }

  maintenance_window_start_time {
    day_of_week = "SUNDAY"
    time_of_day = "05:00"
    time_zone   = "UTC"
  }

  tags = var.tags
}

Steps to Reproduce

1. Use Terraform v1.7.5 and AWS provider v5.97.0

2. Attempt to provision an aws_mq_broker resource with engine_version = "3.13.7"

3. Run terraform apply

Debug Logging

Click to expand log output

GenAI / LLM Assisted Development

n/a

Important Facts and References

Similar behavior previously reported in #38708 but was allegedly resolved. We are still experiencing the error even on LTS.

Would you like to implement a fix?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue 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.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.

[SignalWhisperer]

Since RabbitMQ 3.13, you cannot specify the engine patch version. In the example you've given, you have engine_version = "3.13.7" but it should instead be engine_version = "3.13". If you fix that in your configuration, do you still encounter the issue?