Custom SMT for Confluent Cloud Limitations and Support¶
This page describes the limitations and support for Custom SMTs. Be sure to review all the information in this page before proceeding with the Quick start.
Limitations¶
- Custom SMTs can only be used with fully-managed Connectors.
- Custom SMTs are scoped to a specific Environment and CSP (i.e. AWS).
- Only available for clusters within Private Networking setups (Peering, Transit Gateway, Private Network Interface, Privatelink) on AWS.
- Default limit for Custom SMTs per fully-managed connector is 3.
- Default limit for uploaded Custom SMT artifact files is 5 per Confluent environment.
- Default limit for Custom artifact file size is 100 MB.
- Message size limit of ~2MB (4MB on the wire size).
Reach out to Confluent Support to request limit increase for any of the current limitations.
Important
Confluent regularly scans files uploaded through the Custom SMT product to detect if uploaded Custom SMT artifact files present a security risk to Confluent. If malicious activity is detected, Confluent may immediately delete the Custom SMT artifact file.
Supported AWS regions¶
You can use Custom SMTs with fully-managed connectors in the following AWS regions supported by Confluent Cloud.
AWS regions¶
- Asia Pacific:
- ap-southeast-1 (Singapore)
- ap-southeast-2 (Sydney)
- ap-south-1 (Mumbai)
- Canada:
- ca-central-1 (Canada Central)
- Europe:
- eu-central-1 (Frankfurt)
- eu-west-1 (Ireland)
- eu-west-2 (London)
- United States:
- us-east-1 (N. Virginia)
- us-east-2 (Ohio)
- us-west-2 (Oregon)
Observability / Logs¶
You can view the Confluent Cloud Custom SMT events alongside fully-managed connector events in the Confluent Cloud Console. For more details on how to view these events, see View Connector Events for Confluent Cloud.