http://mq.{region}.amazonaws.com/v1/brokers/{broker-id}Adds a pending configuration change to a broker.
The unique ID that Amazon MQ generates for the broker.
The list of information about logs to be enabled for the specified broker.
<p>A list of information about the configuration.</p> <important><p>Does not apply to RabbitMQ brokers.</p></important>
The broker engine version. For a list of supported engine versions, see <a href="https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/broker-engine.html">Supported engines</a>.
The list of security groups (1 minimum, 5 maximum) that authorizes connections to brokers.
The broker's host instance type to upgrade to. For a list of supported instance types, see <a href="https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/broker.html#broker-instance-types">Broker instance types</a>.
<p>Optional. The metadata of the LDAP server used to authenticate and authorize connections to the broker.</p> <important><p>Does not apply to RabbitMQ brokers.</p></important>
Optional. The authentication strategy used to secure the broker. The default is SIMPLE.
Enables automatic upgrades to new minor versions for brokers, as new versions are released and supported by Amazon MQ. Automatic upgrades occur during the scheduled maintenance window of the broker or after a manual broker reboot.
The scheduled time period relative to UTC during which Amazon MQ begins to apply pending updates or patches to the broker.
{
"success": true,
"data": {
"id": "abc123",
"created_at": "2025-01-01T00:00:00Z"
}
}{
"success": false,
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid request parameters"
}
}1curl --request PUT \2 --url 'http://mq.{region}.amazonaws.com/v1/brokers/{broker-id}' \3 --header 'accept: application/json' \4 --header 'content-type: application/json'1{2 "success": true,3 "data": {4 "id": "abc123",5 "created_at": "2025-01-01T00:00:00Z"6 }7}http://mq.{region}.amazonaws.com/v1/brokers/{broker-id}Adds a pending configuration change to a broker.
The unique ID that Amazon MQ generates for the broker.
The list of information about logs to be enabled for the specified broker.
<p>A list of information about the configuration.</p> <important><p>Does not apply to RabbitMQ brokers.</p></important>
The broker engine version. For a list of supported engine versions, see <a href="https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/broker-engine.html">Supported engines</a>.
The list of security groups (1 minimum, 5 maximum) that authorizes connections to brokers.
The broker's host instance type to upgrade to. For a list of supported instance types, see <a href="https://docs.aws.amazon.com//amazon-mq/latest/developer-guide/broker.html#broker-instance-types">Broker instance types</a>.
<p>Optional. The metadata of the LDAP server used to authenticate and authorize connections to the broker.</p> <important><p>Does not apply to RabbitMQ brokers.</p></important>
Optional. The authentication strategy used to secure the broker. The default is SIMPLE.
Enables automatic upgrades to new minor versions for brokers, as new versions are released and supported by Amazon MQ. Automatic upgrades occur during the scheduled maintenance window of the broker or after a manual broker reboot.
The scheduled time period relative to UTC during which Amazon MQ begins to apply pending updates or patches to the broker.
{
"success": true,
"data": {
"id": "abc123",
"created_at": "2025-01-01T00:00:00Z"
}
}{
"success": false,
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid request parameters"
}
}1curl --request PUT \2 --url 'http://mq.{region}.amazonaws.com/v1/brokers/{broker-id}' \3 --header 'accept: application/json' \4 --header 'content-type: application/json'1{2 "success": true,3 "data": {4 "id": "abc123",5 "created_at": "2025-01-01T00:00:00Z"6 }7}