published on Thursday, Apr 23, 2026 by Volcengine
published on Thursday, Apr 23, 2026 by Volcengine
In a RocketMQ instance, a Topic is the basic unit for sending and consuming messages. RocketMQ Message Queue categorizes and manages different types of messages using Topics. Producers send messages to RocketMQ Topics, and consumers consume messages by subscribing to those Topics.
Example Usage
Example coming soon!
Example coming soon!
Example coming soon!
Example coming soon!
Example coming soon!
resources:
rocketMQTopicDemo:
type: volcenginecc:rocketmq:Topic
name: RocketMQTopicDemo
properties:
instanceId: rocketmq-cnngxxxxx3c2d
topicName: ccapi-test-test-2
messageType: 0
description: this is a test
queueNumber: 6
accessPolicies:
- access_key: TPl1xxxxxxblh5Gpxa79
authority: ALL
Create Topic Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Topic(name: string, args: TopicArgs, opts?: CustomResourceOptions);@overload
def Topic(resource_name: str,
args: TopicArgs,
opts: Optional[ResourceOptions] = None)
@overload
def Topic(resource_name: str,
opts: Optional[ResourceOptions] = None,
instance_id: Optional[str] = None,
message_type: Optional[int] = None,
queue_number: Optional[int] = None,
topic_name: Optional[str] = None,
access_policies: Optional[Sequence[TopicAccessPolicyArgs]] = None,
description: Optional[str] = None)func NewTopic(ctx *Context, name string, args TopicArgs, opts ...ResourceOption) (*Topic, error)public Topic(string name, TopicArgs args, CustomResourceOptions? opts = null)type: volcenginecc:rocketmq:Topic
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args TopicArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args TopicArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args TopicArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args TopicArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args TopicArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Topic Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The Topic resource accepts the following input properties:
- Instance
Id string - Instance ID.
- Message
Type int - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- Queue
Number int - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- Topic
Name string - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- Access
Policies List<Volcengine.Topic Access Policy> - Description string
- Topic description, length: 0–128 characters.
- Instance
Id string - Instance ID.
- Message
Type int - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- Queue
Number int - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- Topic
Name string - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- Access
Policies []TopicAccess Policy Args - Description string
- Topic description, length: 0–128 characters.
- instance
Id String - Instance ID.
- message
Type Integer - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue
Number Integer - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- topic
Name String - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies List<TopicAccess Policy> - description String
- Topic description, length: 0–128 characters.
- instance
Id string - Instance ID.
- message
Type number - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue
Number number - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- topic
Name string - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies TopicAccess Policy[] - description string
- Topic description, length: 0–128 characters.
- instance_
id str - Instance ID.
- message_
type int - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue_
number int - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- topic_
name str - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access_
policies Sequence[TopicAccess Policy Args] - description str
- Topic description, length: 0–128 characters.
- instance
Id String - Instance ID.
- message
Type Number - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue
Number Number - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- topic
Name String - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies List<Property Map> - description String
- Topic description, length: 0–128 characters.
Outputs
All input properties are implicitly available as output properties. Additionally, the Topic resource produces the following output properties:
- Created
Time string - Topic creation time.
- Groups
Infos List<Volcengine.Topic Groups Info> - Id string
- The provider-assigned unique ID for this managed resource.
- Instance
Name string - Instance name.
- Queues
Infos List<Volcengine.Topic Queues Info> - Read
Access List<Volcengine.Policies Topic Read Access Policy> - Service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- Created
Time string - Topic creation time.
- Groups
Infos []TopicGroups Info - Id string
- The provider-assigned unique ID for this managed resource.
- Instance
Name string - Instance name.
- Queues
Infos []TopicQueues Info - Read
Access []TopicPolicies Read Access Policy - Service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- created
Time String - Topic creation time.
- groups
Infos List<TopicGroups Info> - id String
- The provider-assigned unique ID for this managed resource.
- instance
Name String - Instance name.
- queues
Infos List<TopicQueues Info> - read
Access List<TopicPolicies Read Access Policy> - service
Status String - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- created
Time string - Topic creation time.
- groups
Infos TopicGroups Info[] - id string
- The provider-assigned unique ID for this managed resource.
- instance
Name string - Instance name.
- queues
Infos TopicQueues Info[] - read
Access TopicPolicies Read Access Policy[] - service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- created_
time str - Topic creation time.
- groups_
infos Sequence[TopicGroups Info] - id str
- The provider-assigned unique ID for this managed resource.
- instance_
name str - Instance name.
- queues_
infos Sequence[TopicQueues Info] - read_
access_ Sequence[Topicpolicies Read Access Policy] - service_
status str - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- created
Time String - Topic creation time.
- groups
Infos List<Property Map> - id String
- The provider-assigned unique ID for this managed resource.
- instance
Name String - Instance name.
- queues
Infos List<Property Map> - read
Access List<Property Map>Policies - service
Status String - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
Look up Existing Topic Resource
Get an existing Topic resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: TopicState, opts?: CustomResourceOptions): Topic@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
access_policies: Optional[Sequence[TopicAccessPolicyArgs]] = None,
created_time: Optional[str] = None,
description: Optional[str] = None,
groups_infos: Optional[Sequence[TopicGroupsInfoArgs]] = None,
instance_id: Optional[str] = None,
instance_name: Optional[str] = None,
message_type: Optional[int] = None,
queue_number: Optional[int] = None,
queues_infos: Optional[Sequence[TopicQueuesInfoArgs]] = None,
read_access_policies: Optional[Sequence[TopicReadAccessPolicyArgs]] = None,
service_status: Optional[str] = None,
topic_name: Optional[str] = None) -> Topicfunc GetTopic(ctx *Context, name string, id IDInput, state *TopicState, opts ...ResourceOption) (*Topic, error)public static Topic Get(string name, Input<string> id, TopicState? state, CustomResourceOptions? opts = null)public static Topic get(String name, Output<String> id, TopicState state, CustomResourceOptions options)resources: _: type: volcenginecc:rocketmq:Topic get: id: ${id}- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Access
Policies List<Volcengine.Topic Access Policy> - Created
Time string - Topic creation time.
- Description string
- Topic description, length: 0–128 characters.
- Groups
Infos List<Volcengine.Topic Groups Info> - Instance
Id string - Instance ID.
- Instance
Name string - Instance name.
- Message
Type int - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- Queue
Number int - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- Queues
Infos List<Volcengine.Topic Queues Info> - Read
Access List<Volcengine.Policies Topic Read Access Policy> - Service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- Topic
Name string - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- Access
Policies []TopicAccess Policy Args - Created
Time string - Topic creation time.
- Description string
- Topic description, length: 0–128 characters.
- Groups
Infos []TopicGroups Info Args - Instance
Id string - Instance ID.
- Instance
Name string - Instance name.
- Message
Type int - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- Queue
Number int - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- Queues
Infos []TopicQueues Info Args - Read
Access []TopicPolicies Read Access Policy Args - Service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- Topic
Name string - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies List<TopicAccess Policy> - created
Time String - Topic creation time.
- description String
- Topic description, length: 0–128 characters.
- groups
Infos List<TopicGroups Info> - instance
Id String - Instance ID.
- instance
Name String - Instance name.
- message
Type Integer - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue
Number Integer - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- queues
Infos List<TopicQueues Info> - read
Access List<TopicPolicies Read Access Policy> - service
Status String - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic
Name String - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies TopicAccess Policy[] - created
Time string - Topic creation time.
- description string
- Topic description, length: 0–128 characters.
- groups
Infos TopicGroups Info[] - instance
Id string - Instance ID.
- instance
Name string - Instance name.
- message
Type number - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue
Number number - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- queues
Infos TopicQueues Info[] - read
Access TopicPolicies Read Access Policy[] - service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic
Name string - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access_
policies Sequence[TopicAccess Policy Args] - created_
time str - Topic creation time.
- description str
- Topic description, length: 0–128 characters.
- groups_
infos Sequence[TopicGroups Info Args] - instance_
id str - Instance ID.
- instance_
name str - Instance name.
- message_
type int - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue_
number int - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- queues_
infos Sequence[TopicQueues Info Args] - read_
access_ Sequence[Topicpolicies Read Access Policy Args] - service_
status str - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic_
name str - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies List<Property Map> - created
Time String - Topic creation time.
- description String
- Topic description, length: 0–128 characters.
- groups
Infos List<Property Map> - instance
Id String - Instance ID.
- instance
Name String - Instance name.
- message
Type Number - Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
- queue
Number Number - Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
- queues
Infos List<Property Map> - read
Access List<Property Map>Policies - service
Status String - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic
Name String - Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores () are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
Supporting Types
TopicAccessPolicy, TopicAccessPolicyArgs
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access_
key str - AccessKey of the RocketMQ key.
- str
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
TopicGroupsInfo, TopicGroupsInfoArgs
- Group
Id string - Group ID of the consumer group.
- Message
Model string - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- Sub
String string - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- Group
Id string - Group ID of the consumer group.
- Message
Model string - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- Sub
String string - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group
Id String - Group ID of the consumer group.
- message
Model String - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub
String String - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group
Id string - Group ID of the consumer group.
- message
Model string - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub
String string - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group_
id str - Group ID of the consumer group.
- message_
model str - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub_
string str - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group
Id String - Group ID of the consumer group.
- message
Model String - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub
String String - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
TopicQueuesInfo, TopicQueuesInfoArgs
- End
Offset int - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- Last
Update intTimestamp - The time of the most recent message written to this queue.
- Message
Count int - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- Queue
Id string - Queue ID.
- Start
Offset int - The earliest message offset in the current queue.
- End
Offset int - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- Last
Update intTimestamp - The time of the most recent message written to this queue.
- Message
Count int - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- Queue
Id string - Queue ID.
- Start
Offset int - The earliest message offset in the current queue.
- end
Offset Integer - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last
Update IntegerTimestamp - The time of the most recent message written to this queue.
- message
Count Integer - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue
Id String - Queue ID.
- start
Offset Integer - The earliest message offset in the current queue.
- end
Offset number - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last
Update numberTimestamp - The time of the most recent message written to this queue.
- message
Count number - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue
Id string - Queue ID.
- start
Offset number - The earliest message offset in the current queue.
- end_
offset int - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last_
update_ inttimestamp - The time of the most recent message written to this queue.
- message_
count int - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue_
id str - Queue ID.
- start_
offset int - The earliest message offset in the current queue.
- end
Offset Number - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last
Update NumberTimestamp - The time of the most recent message written to this queue.
- message
Count Number - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue
Id String - Queue ID.
- start
Offset Number - The earliest message offset in the current queue.
TopicReadAccessPolicy, TopicReadAccessPolicyArgs
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access_
key str - AccessKey of the RocketMQ key.
- str
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
Import
$ pulumi import volcenginecc:rocketmq/topic:Topic example "instance_id|topic_name"
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- volcenginecc volcengine/pulumi-volcenginecc
- License
- MPL-2.0
- Notes
- This Pulumi package is based on the
volcengineccTerraform Provider.
published on Thursday, Apr 23, 2026 by Volcengine
