Builder

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. Set to true by default, if no value is specified.

Required. The broker's name. This value must be unique in your Amazon Web Services account, 1-50 characters long, must contain only letters, numbers, dashes, and underscores, and must not contain white spaces, brackets, wildcard characters, or special characters.

A list of information about the configuration.

The unique ID that the requester receives for the created broker. Amazon MQ passes your ID with the API action.

Defines whether this broker is a part of a data replication pair.

The Amazon Resource Name (ARN) of the primary broker that is used to replicate data from in a data replication pair, and is applied to the replica broker. Must be set when dataReplicationMode is set to CRDR.

Required. The broker's deployment mode.

Encryption options for the broker.

Required. The type of broker engine. Currently, Amazon MQ supports ACTIVEMQ and RABBITMQ.

Required. The broker engine's version. For a list of supported engine versions, see Supported engines.

Required. The broker's instance type.

Optional. The metadata of the LDAP server used to authenticate and authorize connections to the broker. Does not apply to RabbitMQ brokers.

Enables Amazon CloudWatch logging for brokers.

The parameters that determine the WeeklyStartTime.

Enables connections from applications outside of the VPC that hosts the broker's subnets. Set to false by default, if no value is provided.

The list of rules (1 minimum, 125 maximum) that authorize connections to brokers.

The broker's storage type.

The list of groups that define which subnets and IP ranges the broker can use from different Availability Zones. If you specify more than one subnet, the subnets must be in different Availability Zones. Amazon MQ will not be able to create VPC endpoints for your broker with multiple subnets in the same Availability Zone. A SINGLE_INSTANCE deployment requires one subnet (for example, the default subnet). An ACTIVE_STANDBY_MULTI_AZ Amazon MQ for ActiveMQ deployment requires two subnets. A CLUSTER_MULTI_AZ Amazon MQ for RabbitMQ deployment has no subnet requirements when deployed with public accessibility. Deployment without public accessibility requires at least one subnet.

Create tags when creating the broker.

The list of broker users (persons or applications) who can access queues and topics. For Amazon MQ for RabbitMQ brokers, one and only one administrative user is accepted and created when a broker is first provisioned. All subsequent broker users are created by making RabbitMQ API calls directly to brokers or via the RabbitMQ web console.

construct an aws.sdk.kotlin.services.mq.model.ConfigurationId inside the given block

construct an aws.sdk.kotlin.services.mq.model.EncryptionOptions inside the given block

construct an aws.sdk.kotlin.services.mq.model.LdapServerMetadataInput inside the given block

construct an aws.sdk.kotlin.services.mq.model.Logs inside the given block

construct an aws.sdk.kotlin.services.mq.model.WeeklyStartTime inside the given block