Бэкап для Amazon MSK:

https://aws.amazon.com/blogs/architecture/amazon-msk-backup-for-archival-replay-or-analytics/

#MSK

Kafka Connect для Amazon MSK = MSK Connect:

https://aws.amazon.com/blogs/aws/introducing-amazon-msk-connect-stream-data-to-and-from-your-apache-kafka-clusters-using-managed-connectors/

MSK Connect allows you to configure and deploy a connector using Kafka Connect with a just few clicks. MSK Connect provisions the required resources and sets up the cluster. It continuously monitors the health and delivery state of connectors, patches and manages the underlying hardware, and auto-scales connectors to match changes in throughput. As a result, you can focus your resources on building applications rather than managing infrastructure.
MSK Connect is fully compatible with Kafka Connect, which means you can migrate your existing connectors without code changes. You don’t need an MSK cluster to use MSK Connect. It supports Amazon MSK, Apache Kafka, and Apache Kafka compatible clusters as sources and sinks. These clusters can be self-managed or managed by AWS partners and 3rd parties as long as MSK Connect can privately connect to the clusters.

#MSK

Доступ в Amazon MSK (Kafka) через интернет:

https://docs.aws.amazon.com/msk/latest/developerguide/public-access.html

При публичном доступе доступны авторизации SASL/IAM, SASL/SCRAM, mTLS. Без авторизации использовать публичный доступ нельзя, равно как и без шифрования кластера.

Из-за того, что требуется доступ MSK к публичным подсетям, то наверняка потребуется пересоздание (для того, чтобы включить публичный доступ). В любом случае, проблематичные велосипеды с VPN можно убирать. Очень хорошо.

#MSK