Try our new research platform with insights from 80,000+ expert users

Pros & Cons summary

Buyer's Guide

Get pricing advice, tips, use cases and valuable features from real users of this product.
Get the report

Prominent pros & cons

PROS

Amazon MSK offers a private network as an out-of-box feature and provides significant integration capabilities.
It is noted for cost-effectiveness regarding workflow and contributes positively to real-time analytics capabilities.
Amazon MSK is stable with good scalability and usability, adding ease to creating and deploying new features.
The separation of concerns simplifies access to message consumption without complex communications.
Amazon MSK ensures minimal configuration needs, as it automatically checks broker functioning and resolves issues.

CONS

Amazon MSK lacks flexibility in integrations and autoscaling capabilities, increasing operational overhead when managing clusters.
Configuration and documentation are complex, with challenges in initial setup and outdated materials causing confusion.
Schema support requires enhancement to improve integration with various programming languages, especially environments using .NET.
High costs, with increases of 50% to 60%, are significant disadvantages without justifiable savings.
Adjusting configurations and limited options for unique use cases create difficulties in production environments.
 

Amazon MSK Pros review quotes

reviewer1500498 - PeerSpot reviewer
Team Lead at a tech services company with 10,001+ employees
Mar 16, 2021
MSK has a private network that's an out-of-box feature.
NK
Human Resources Executive at Sticky IO
Aug 22, 2022
The most valuable feature of Amazon MSK is the integration.
Keorapetse Naane - PeerSpot reviewer
Cloud DevOps Engineer at Restack
May 18, 2023
Overall, it is very cost-effective based on the workflow.
Learn what your peers think about Amazon MSK. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
879,259 professionals have used our research since 2012.
Aniruddh Kurundkar - PeerSpot reviewer
Lead Consultant at Neutrino Tech Systems
Jun 19, 2023
It is a stable product.
reviewer2268408 - PeerSpot reviewer
Software Team Lead at a tech services company with 201-500 employees
Sep 4, 2023
It offers good stability.
Gustavo-Barbosa Dos Santos - PeerSpot reviewer
Software Architect at C&A Brasil
Jan 8, 2024
Amazon MSK has significantly improved our organization by building seamless integration between systems.
reviewer2237604 - PeerSpot reviewer
Integration Solution Architect at a consultancy with 11-50 employees
May 24, 2024
Amazon MSK's scalability is very good.
FW
Senior Software Engineer at a recreational facilities/services company with 1,001-5,000 employees
Jun 12, 2024
Amazon MSK's separation of concerns and ease of creating and deploying new features are highly valuable. It just requires to assign them to the topic, and then anyone who needs to consume these messages can do so directly from Amazon MSK. This separation of concerns makes it very convenient, especially for new feature development, as developers can easily access the messages they need without having to deal with complex server communications or protocol setups.
AnkurShukla - PeerSpot reviewer
SDE at Mindtickle
Jul 10, 2024
The solution's technical support was helpful.
PP
CTO at Atulya Abhinav Tech Private Limited
Feb 25, 2025
It provides installations, scaling, and other functionalities straight out of the box.
 

Amazon MSK Cons review quotes

reviewer1500498 - PeerSpot reviewer
Team Lead at a tech services company with 10,001+ employees
Mar 16, 2021
It should be more flexible, integration-wise.
NK
Human Resources Executive at Sticky IO
Aug 22, 2022
Amazon MSK could improve on the features they offer. They are still lagging behind Confluence.
Keorapetse Naane - PeerSpot reviewer
Cloud DevOps Engineer at Restack
May 18, 2023
It does not autoscale. Because if you do keep it manually when you add a note to the cluster and then you register it, then it is scalable, but the fact that you have to go and do it, I think, makes it, again, a bit of some operational overhead when managing the cluster.
Learn what your peers think about Amazon MSK. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
879,259 professionals have used our research since 2012.
Aniruddh Kurundkar - PeerSpot reviewer
Lead Consultant at Neutrino Tech Systems
Jun 19, 2023
It would be really helpful if Amazon MSK could provide a single installation that covers all the servers.
reviewer2268408 - PeerSpot reviewer
Software Team Lead at a tech services company with 201-500 employees
Sep 4, 2023
The configuration seems a little complex and the documentation on the product is not available.
Gustavo-Barbosa Dos Santos - PeerSpot reviewer
Software Architect at C&A Brasil
Jan 8, 2024
The product's schema support needs enhancement. It will help enhance integration with many kinds of languages of programming languages, especially for environments using languages like .NET.
reviewer2237604 - PeerSpot reviewer
Integration Solution Architect at a consultancy with 11-50 employees
May 24, 2024
One of the reasons why we prefer Kafka is because the support is a little bit difficult to manage with Amazon MSK.
FW
Senior Software Engineer at a recreational facilities/services company with 1,001-5,000 employees
Jun 12, 2024
In my opinion, there are areas in Amazon MSK that could be improved, particularly in terms of configuration. Initially setting it up and getting it connected was quite challenging. The naming conventions for policies were updated by AWS, and some were undocumented, leading to confusion with outdated materials. It took us weeks of trial and error before discovering new methods through hidden tutorials and official documentation.
AnkurShukla - PeerSpot reviewer
SDE at Mindtickle
Jul 10, 2024
Horizontal scale-out is actually not easy, making it an area where improvements are required.
PP
CTO at Atulya Abhinav Tech Private Limited
Feb 25, 2025
The cost of using Amazon MSK is high, which is a significant disadvantage, as the increase in cloud costs by 50% to 60% does not justify the savings.