Question
Tokyo Century Corporation
JP
Last activity: 20 Jan 2025 3:40 EST
About sharing MSK
I'm trying to deploy two environments with Pega 24.2.0 on EKS. Since this is a verification environment, I would like to use external MSK in common to reduce costs. Is it possible to use the same MSK from two Pegas?
Accepted Solution
Updated: 20 Jan 2025 3:40 EST
HCA Healthcare
US
Yes, you can use the same Amazon MSK cluster for two Pega environments deployed on EKS, but it requires proper configuration and caution. Each Pega environment should have separate Kafka topics to avoid conflicts, and you need to ensure proper topic naming conventions and isolation using unique prefixes for each environment. Additionally, configure access control using AWS IAM or Kafka ACLs to restrict permissions and ensure data security between the environments. Sharing MSK is cost-effective, but monitor the cluster’s performance to handle the combined load from both environments. This setup is feasible for verification purposes but may not be ideal for production
Updated: 31 Dec 2024 6:38 EST
Pegasystems Inc.
GB
@keisukek17309988 we can see you previously logged a similar question here: About sharing external components
MSK, or Amazon Managed Streaming for Apache Kafka, is an external Kafka that the Pega Platform can connect to. Pega can connect to any external Kafka, but it doesn't support vendor-specific security features like IAM roles.
Third-party externalized services Deployment Changes FAQs
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Accepted Solution
Updated: 20 Jan 2025 3:40 EST
HCA Healthcare
US
Yes, you can use the same Amazon MSK cluster for two Pega environments deployed on EKS, but it requires proper configuration and caution. Each Pega environment should have separate Kafka topics to avoid conflicts, and you need to ensure proper topic naming conventions and isolation using unique prefixes for each environment. Additionally, configure access control using AWS IAM or Kafka ACLs to restrict permissions and ensure data security between the environments. Sharing MSK is cost-effective, but monitor the cluster’s performance to handle the combined load from both environments. This setup is feasible for verification purposes but may not be ideal for production