Skip to content

KNOWN_LIMITATIONS.md

Latest commit

 

History

History
25 lines (14 loc) · 1.58 KB

KNOWN_LIMITATIONS.md

File metadata and controls

25 lines (14 loc) · 1.58 KB
Raw

Known Limitations

Immutability Constraints

Most MSK Connect resources force replacement on any change:

  • aws_mskconnect_custom_plugin: ALL arguments force replacement. Any change destroys and recreates.
  • aws_mskconnect_worker_configuration: ALL arguments force replacement.
  • aws_mskconnect_connector: Only capacity and connector_configuration can be updated in-place. Everything else (name, kafka_cluster, plugins, worker_config, service_execution_role, encryption, auth) forces replacement.

Single Plugin Per Connector

AWS MSK Connect supports multiple plugins per connector, but this module only supports one.

No S3 Bucket Management

This module does not create S3 buckets or upload plugin artifacts. The S3 bucket and plugin ZIP must exist before the connector is created. The service_execution_role must have s3:GetObject permissions on the plugin bucket and appropriate S3 permissions on any data buckets used by the connector (e.g., s3:PutObject for sink connectors).

IAM Authentication Only

This module hardcodes IAM authentication (SASL/SCRAM is not supported). The MSK cluster must have IAM auth enabled (client_authentication.sasl.iam = true) so that bootstrap_brokers_sasl_iam (port 9098) is available. The service_execution_role must have the necessary kafka-cluster:* permissions.

No IAM Role Management

This module does not create IAM roles. The service_execution_role must reference a pre-existing IAM role with appropriate permissions (e.g., kafka-cluster:Connect, kafka-cluster:ReadData, kafka-cluster:WriteData, etc.).