aws mq create-broker

Creates a broker. Note: This API is asynchronous

Options

NameDescription
--authentication-strategy <string>The authentication strategy used to secure the broker
--auto-minor-version-upgradeRequired. Enables automatic upgrades to new minor versions for brokers, as Apache releases the versions. The automatic upgrades occur during the maintenance window of the broker or after a manual broker reboot
--no-auto-minor-version-upgradeRequired. Enables automatic upgrades to new minor versions for brokers, as Apache releases the versions. The automatic upgrades occur during the maintenance window of the broker or after a manual broker reboot
--broker-name <string>Required. The name of the broker. This value must be unique in your AWS account, 1-50 characters long, must contain only letters, numbers, dashes, and underscores, and must not contain whitespaces, brackets, wildcard characters, or special characters
--configuration <structure>A list of information about the configuration
--creator-request-id <string>The unique ID that the requester receives for the created broker. Amazon MQ passes your ID with the API action. Note: We recommend using a Universally Unique Identifier (UUID) for the creatorRequestId. You may omit the creatorRequestId if your application doesn't require idempotency
--deployment-mode <string>Required. The deployment mode of the broker
--encryption-options <structure>Encryption options for the broker
--engine-type <string>Required. The type of broker engine. Note: Currently, Amazon MQ supports ACTIVEMQ and RABBITMQ
--engine-version <string>Required. The version of the broker engine. For a list of supported engine versions, see https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/broker-engine.html
--host-instance-type <string>Required. The broker's instance type
--ldap-server-metadata <structure>The metadata of the LDAP server used to authenticate and authorize connections to the broker
--logs <structure>Enables Amazon CloudWatch logging for brokers
--maintenance-window-start-time <structure>The parameters that determine the WeeklyStartTime
--publicly-accessibleRequired. Enables connections from applications outside of the VPC that hosts the broker's subnets
--no-publicly-accessibleRequired. Enables connections from applications outside of the VPC that hosts the broker's subnets
--security-groups <list>The list of security groups (1 minimum, 5 maximum) that authorizes connections to brokers
--storage-type <string>The broker's storage type
--subnet-ids <list>The list of groups that define which subnets and IP ranges the broker can use from different Availability Zones. A SINGLE_INSTANCE deployment requires one subnet (for example, the default subnet). An ACTIVE_STANDBY_MULTI_AZ deployment (ACTIVEMQ) requires two subnets. A CLUSTER_MULTI_AZ deployment (RABBITMQ) has no subnet requirements when deployed with public accessibility, deployment without public accessibility requires at least one subnet
--tags <map>Create tags when creating the broker
--users <list>Required. The list of broker users (persons or applications) who can access queues and topics. 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. This value can contain only alphanumeric characters, dashes, periods, underscores, and tildes (- . _ ~). This value must be 2-100 characters long
--cli-input-json <string>Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally
--generate-cli-skeleton <string>Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command