# Configuration settings to change environment

**URL:** <https://forum.yugabyte.com/t/configuration-settings-to-change-environment/565>\
**Category:** General\
**Created:** [November 18, 2019, 2:46pm UTC](https://forum.yugabyte.com/t/configuration-settings-to-change-environment/565 "2019-11-18T14:46:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Edward\_Ribbery](https://avatars.discourse-cdn.com/v4/letter/e/a88e57/32.png) [@Edward\_Ribbery](https://forum.yugabyte.com/u/Edward_Ribbery)\
**Post date:** [November 18, 2019, 2:46pm UTC](https://forum.yugabyte.com/t/configuration-settings-to-change-environment/565/1 "2019-11-18T14:46:02Z")

</div>

Are there any specific recommendations for configuration settings to run yugabyte in a multi-region environment compared to a multi-zone (AZ) environment in AWS or GCP?

I do expect the latency of operations to be higher in a multi-region deployment. But in terms of system configuration, are there any best practice settings for such deployments in order to handle transient network blips better?

---

<div class="post-metadata">

**Author:** ![dorian\_yugabyte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/dorian_yugabyte/32/206_2.png) [@dorian\_yugabyte](https://forum.yugabyte.com/u/dorian_yugabyte)\
**Post date:** [November 18, 2019, 3:55pm UTC](https://forum.yugabyte.com/t/configuration-settings-to-change-environment/565/2 "2019-11-18T15:55:03Z")

</div>

One configuration that will help is putting all leaders (if possible) in 1 region. This will lower latency of transactions: [yb-admin - command line tool for advanced YugabyteDB administration | YugabyteDB Docs](https://docs.yugabyte.com/latest/admin/yb-admin/#set-preferred-zones)

cc @neha for more