Amazon MSK Connect now supports updating connector plugins and worker configurations
- Announced
- Tags
- amazon-msk
- Severity
- info, set by
reef/rss-rule-v1 - Source
- https://aws.amazon.com/about-aws/whats-new/2026/10/amazon-msk-connect-update-plugin-worker-configurations
<p><a href="https://aws.amazon.com/msk/features/msk-connect/"><u>Amazon MSK Connect</u></a> (Amazon Managed Streaming for Apache Kafka Connect) now lets you update the custom plugin and worker configuration of an existing connector. This is useful when you need to update the custom plugin to run a new version of your connector code, for example one with updated dependencies. You can also update the worker configuration to change worker-level settings, such as switching key and value converters or tuning producer and consumer properties for throughput and latency.</p> <p>Amazon MSK Connect is a fully managed service that allows you to deploy, monitor, and scale Apache Kafka Connect connectors with <a href="https://aws.amazon.com/msk/"><u>Amazon MSK</u></a> (Managed Streaming for Apache Kafka). Previously, updating a connector's plugin or worker configuration meant deleting the connector and recreating it - a disruptive operation that added risk and operational overhead. With this launch, you can update a connector's plugin and worker configuration in place. The connector keeps its committed offsets, so its tasks continue processing from where they left off once the update completes.</p> <p>This capability is available at no additional cost in all AWS Regions where Amazon MSK Connect is supported. To learn more, visit <a href="https://docs.aws.amazon.com/msk/latest/developerguide/msk-connect.html"><u>Amazon MSK Connect developer guide</u></a>.</p>
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.