Broker is the Schema for the Brokers API. Provides an MQ Broker Resource
Type
CRD
Group
mq.aws.upbound.io
Version
v1beta1
apiVersion: mq.aws.upbound.io/v1beta1
kind: Broker
BrokerSpec defines the desired state of Broker
No description provided.
Configuration block for broker configuration. Applies to engine_type of ActiveMQ and RabbitMQ only. Detailed below.
Reference to a Configuration in mq to populate id.
Policies for referencing.
Selector for a Configuration in mq to populate id.
Policies for selection.
Configuration block containing encryption options. Detailed below.
Configuration block for the LDAP server used to authenticate and authorize connections to the broker. Not supported for engine_type RabbitMQ. Detailed below. (Currently, AWS may not process changes to LDAP server metadata.)
List of a fully qualified domain name of the LDAP server and an optional failover server.
References to SecurityGroup in ec2 to populate securityGroups.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroups.
Policies for selection.
List of security group IDs assigned to the broker.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
List of subnet IDs in which to launch the broker. A SINGLE_INSTANCE deployment requires one subnet. An ACTIVE_STANDBY_MULTI_AZ deployment requires multiple subnets.
Configuration block for broker users. For engine_type of RabbitMQ, Amazon MQ does not return broker users preventing this resource from making user updates and drift detection. Detailed below.
List of groups (20 maximum) to which the ActiveMQ user belongs. Applies to engine_type of ActiveMQ only.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Configuration block for broker configuration. Applies to engine_type of ActiveMQ and RabbitMQ only. Detailed below.
Reference to a Configuration in mq to populate id.
Policies for referencing.
Selector for a Configuration in mq to populate id.
Policies for selection.
Configuration block containing encryption options. Detailed below.
Configuration block for the LDAP server used to authenticate and authorize connections to the broker. Not supported for engine_type RabbitMQ. Detailed below. (Currently, AWS may not process changes to LDAP server metadata.)
List of a fully qualified domain name of the LDAP server and an optional failover server.
References to SecurityGroup in ec2 to populate securityGroups.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroups.
Policies for selection.
List of security group IDs assigned to the broker.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
List of subnet IDs in which to launch the broker. A SINGLE_INSTANCE deployment requires one subnet. An ACTIVE_STANDBY_MULTI_AZ deployment requires multiple subnets.
Configuration block for broker users. For engine_type of RabbitMQ, Amazon MQ does not return broker users preventing this resource from making user updates and drift detection. Detailed below.
List of groups (20 maximum) to which the ActiveMQ user belongs. Applies to engine_type of ActiveMQ only.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
BrokerStatus defines the observed state of Broker.
No description provided.
Configuration block containing encryption options. Detailed below.
List of information about allocated brokers (both active & standby).
Broker's wire-level protocol endpoints in the following order & format referenceable e.g., as instances.0.endpoints.0 (SSL):
Configuration block for the LDAP server used to authenticate and authorize connections to the broker. Not supported for engine_type RabbitMQ. Detailed below. (Currently, AWS may not process changes to LDAP server metadata.)
List of a fully qualified domain name of the LDAP server and an optional failover server.
List of security group IDs assigned to the broker.
List of subnet IDs in which to launch the broker. A SINGLE_INSTANCE deployment requires one subnet. An ACTIVE_STANDBY_MULTI_AZ deployment requires multiple subnets.
Configuration block for broker users. For engine_type of RabbitMQ, Amazon MQ does not return broker users preventing this resource from making user updates and drift detection. Detailed below.
List of groups (20 maximum) to which the ActiveMQ user belongs. Applies to engine_type of ActiveMQ only.
Conditions of the resource.
example
apiVersion: mq.aws.upbound.io/v1beta1
kind: Broker
metadata:
annotations:
meta.upbound.io/example-id: mq/v1beta1/broker
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
brokerName: example-broker
engineType: ActiveMQ
engineVersion: 5.17.6
hostInstanceType: mq.t2.micro
region: us-west-1
securityGroupRefs:
- name: example
user:
- passwordSecretRef:
key: password
name: mq-secret
namespace: upbound-system
username: admin
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.