Answers: <p>I cannot back it up with links to the documentation, but my strong assumption is that it is not possible. AWS MSK forces cross availability-zone deployments. (In most cases, it is a good idea, anyway. I understand that the scenario in my question is not so common.)</p>
  
  <p>The only option to stay in the same availability zone is to use only one broker. However, it is not recommended to run Kafka with a single broker. Therefore it is not an attractive option.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-05-04T23:45:31.230Z
Answers: 2020-05-04T23:45:31.230Z
Answers: Philipp Claßen
Body: <p>When using <a href="https://aws.amazon.com/msk/" rel="nofollow noreferrer">AWS MSK</a>, is it possible to deploy Kafka brokers in the same AWS availability zone?</p>
  
  <p>From what I read, AWS enforces deployments across availability zones. If you use three brokers, it will require three subnets in different availability zones. Is that true or is there a way to bypass that restriction?</p>
  
  <hr>
  
  <p>Background: for most situations, deploying across zones is a good idea, but we are operating a subsystem where availability is not crucial and where all services are running in the same availability zone. Traffic in the same AZ is free, so we would prefer that if possible. If Kafka is unavailable if the whole data center behind that AZ goes down, would be acceptable. Most likely, the whole subsystem would not work in that scenario anyway.</p>
  
Tags: <amazon-web-services><kafka>
Title: AWS MSK: deploying all Kafka brokers in the same availability zone
UserDisplayName: Philipp Claßen
ThreadText: # AWS MSK: deploying all Kafka brokers in the same availability zone
  
  (Asked by: username_0 on 2020-01-10)
  
  When using [AWS MSK](https://aws.amazon.com/msk/), is it possible to deploy Kafka brokers in the same AWS availability zone?
  
  From what I read, AWS enforces deployments across availability zones. If you use three brokers, it will require three subnets in different availability zones. Is that true or is there a way to bypass that restriction?
  
  ---
  
  Background: for most situations, deploying across zones is a good idea, but we are operating a subsystem where availability is not crucial and where all services are running in the same availability zone. Traffic in the same AZ is free, so we would prefer that if possible. If Kafka is unavailable if the whole data center behind that AZ goes down, would be acceptable. Most likely, the whole subsystem would not work in that scenario anyway.
  
  **Tags:** amazon-web-services, kafka
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-05-04. Score: 0 | Accepted answer
  
  I cannot back it up with links to the documentation, but my strong assumption is that it is not possible. AWS MSK forces cross availability-zone deployments. (In most cases, it is a good idea, anyway. I understand that the scenario in my question is not so common.)
  
  The only option to stay in the same availability zone is to use only one broker. However, it is not recommended to run Kafka with a single broker. Therefore it is not an attractive option.
  
  
  ---
  
  