tag: Amazon-Msk · 4 items
- Platform/SRE — Plan: If you run Amazon MSK, this GA feature lets managed Prometheus collectors scrape consumer-group lag metrics without self-operated agents; evaluate adopting it this quarter to replace any self-managed Kafka exporters in your observability pipeline.
- CI/CD — Skip
- Leader — Skip
- Signals: GA announcement
- Platform/SRE — Plan: MSK Provisioned clusters now support TLS 1.3 as a GA opt-in via named security policies — evaluate applying a TLS 1.3-capable policy this quarter, particularly if your org has compliance frameworks requiring TLS 1.3 or if post-quantum readiness is on the roadmap.
- CI/CD — Skip
- Leader — Learn: MSK’s new TLS 1.3 support is a step toward post-quantum cryptography readiness and aligns with tightening compliance standards; no strategic or licensing decision is forced, but worth knowing if your security policy roadmap includes post-quantum preparedness.
- Platform/SRE — Plan: If on-prem Kafka migration to MSK is on the roadmap, evaluate AWS Transform’s new assessment agent this quarter — it automates topology mapping, compatibility checks, broker right-sizing, and cost projection that otherwise takes weeks.
- CI/CD — Skip
- Leader — Learn: This tool generates AI-assisted TCO business cases for Kafka-to-MSK migrations, which could inform a build-vs-buy or cloud-migration decision, but it doesn’t force one — useful context for orgs still running self-managed Kafka.
- 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