Skip to content

[new-product] AWS MSK #7817

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

aljoshare
Copy link

This PR adds the Amazon Managed Streaming for Apache Kafka.

Copy link

welcome bot commented Jul 4, 2025

Thank you for opening this pull request 👍. If you are not familiar with the project, please check out our Contributing Guidelines and our Guiding Principles. Also take a look at our Hacking Guide if you intend to work on site internals.

@aljoshare aljoshare force-pushed the feat/new-product-amazon-msk branch from 9743228 to 3c1e3c9 Compare July 4, 2025 14:52
@aljoshare aljoshare force-pushed the feat/new-product-amazon-msk branch from 3c1e3c9 to f8caa57 Compare July 4, 2025 16:05
@aljoshare aljoshare marked this pull request as ready for review July 4, 2025 16:08
@BiNZGi BiNZGi added the new-product This PR adds a new product to the website. label Jul 9, 2025
@captn3m0
Copy link
Member

I made a few minor tone changes in the description (we can't use "you" as a third-party). Overall, this is looking good, but I have one concern: AWS documents Support Life cycle on a patch version basis, while this page is using minor releases.

This causes issues wherever multiple patch releases are simultaneously supported:

VERSION EOL
3.3.1 2024-09-11
3.3.2 2024-09-11

On 2024-09-01, both 3.3.1 and 3.3.2 clusters were supported. But the table currently lists a single 3.3 row, which has an EOL.

Since there aren't multiple patch releases supported right now, this works well though, but only for now. But we might have to split a row in the future, and that would result in a breakage (say if 3.6.2 was released tomorrow).

It would be better to avoid that breakage if we can split currently supported release cycles into patch-levels instead (So 3.4 -> 3.4.0, 3.5 -> 3.5.1 and so on). We can ignore EOL releases, which are okay to be merged.

Also, if we can check what 4.0.x really means in terms of patchlevel that will be great - Can we try creating a cluster and seeing what version it reports? Is it 4.0.x or 4.0.0, and whether AWS really means 4.0 as the release cycle here?

@captn3m0 captn3m0 self-assigned this Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-product This PR adds a new product to the website.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants