> ## Documentation Index
> Fetch the complete documentation index at: https://docs.automq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Client Configuration

> Optimize cloud-native data flow with AutoMQ using zone identification for seamless Kafka-compatible scalability and efficient data fetching based on client zone ID.

## Setting Zone Identification

In addition to identifying client zones through server-side configuration rules [Broker Configuration▸](/automq/eliminate-inter-zone-traffics/broker-configuration), AutoMQ also supports clients specifying zone information. This can be achieved by appending `automq_az=$zoneId` to `client.id`, indicating the zone to which the client belongs. The `client.id` format is as follows:

```properties theme={null}
client.id=automq_az=$zoneId&existing-client-id
```

<Tip>
  On AWS, it is recommended to use [zoneId](https://docs.aws.amazon.com/ram/latest/userguide/working-with-az-ids.html) instead of zoneName, as zoneId is consistent across all accounts.
</Tip>

## Follower Fetching

Consumers can set zone identification via `client.id`. Additionally, for clients with versions greater than 2.4.0, the [KIP-329 fetch from closest replicas](https://cwiki.apache.org/confluence/display/KAFKA/KIP-392%3A+Allow+consumers+to+fetch+from+closest+replica) feature can be utilized to configure zone affinity for consumption. The configuration method is as follows:

```properties theme={null}
client.rack=$zoneId
```