tag: Kafka · 5 items
Learn
archived
Amazon MSK Connect and Glue Schema Registry launch in AWS EU Sovereign Cloud (Germany)
- Platform/SRE — Skip
- CI/CD — Skip
- Leader — Learn: For organizations with German or EU data-sovereignty requirements already on the AWS European Sovereign Cloud, the managed Kafka Connect and Schema Registry stack is now complete in that region — worth noting if evaluating compliance-scoped streaming architectures.
- Platform/SRE — Learn: Newly GA OAuth support for Lambda Kafka ESM unblocks regulated-industry workloads that couldn’t use SASL/PLAIN or mTLS; worth noting if the team runs Kafka clusters consumed by Lambda, but no existing configuration needs to change.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: Platform teams running Tempo 3.0 in microservices mode with Kafka-based ingestion shipped without TLS support — a real security gap. Upgrading to 3.1 closes it with TLS and additional SASL mechanisms (SCRAM-SHA-256/512, OAUTHBEARER, AWS_MSK_IAM); schedule the upgrade this quarter if Kafka ingestion is in use.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Learn: Teams running MSK Connect can now restart connectors and individual failed tasks instead of deleting and recreating them, reducing recovery toil. No migration required — worth updating runbooks if you operate Kafka Connect pipelines on MSK.
- CI/CD — Skip
- Leader — Skip
- Platform/SRE — Plan: If you run MSK Provisioned clusters, enable Authorizer Log Delivery to route denied-access events (with client IP and API) to CloudWatch, S3, or Firehose — useful for security auditing and troubleshooting auth issues at no added cost.
- CI/CD — Skip
- Leader — Skip