---
title: Advanced configuration for Elastic Maps Server on Elastic Cloud on Kubernetes
description: If you already looked at the Elasticsearch on ECK documentation, some of these concepts might sound familiar to you. The resource definitions in ECK share...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/deploy-manage/deploy/cloud-on-k8s/advanced-configuration-maps-server
products:
  - Elastic Cloud on Kubernetes
---

# Advanced configuration for Elastic Maps Server on Elastic Cloud on Kubernetes
<warning>
  This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
</warning>

If you already looked at the [Elasticsearch on ECK](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4236/deploy-manage/deploy/cloud-on-k8s/elasticsearch-configuration) documentation, some of these concepts might sound familiar to you. The resource definitions in ECK share the same philosophy when you want to:
- Customize the Pod configuration
- Customize the product configuration
- Manage HTTP settings


## Elastic Maps Server configuration

You can add any valid Elastic Maps Server setting as documented on the [product](/elastic/docs-content/pull/4236/explore-analyze/visualize/maps/maps-connect-to-ems#elastic-maps-server-configuration) page to the `spec.config` section.
The following example demonstrates how to set the log level to `debug`:
```yaml
apiVersion: maps.k8s.elastic.co/v1alpha1
kind: ElasticMapsServer
metadata:
  name: quickstart
spec:
  version: 9.2.2
  count: 1
  config:
     logging.level: debug
```

Alternatively, settings can be provided through a Secret specified in the `configRef` element:
```yaml
apiVersion: maps.k8s.elastic.co/v1alpha1
kind: ElasticMapsServer
metadata:
  name: quickstart
spec:
  version: 9.2.2
  configRef:
    secretName: maps-config
---
apiVersion: v1
kind: Secret
metadata:
  name: maps-config
stringData:
  elastic-maps-server.yml: |-
    logging.level: debug
```

Refer to [Set compute resources for Kibana, Elastic Maps Server, APM Server and Logstash](/elastic/docs-content/pull/4236/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources#k8s-compute-resources-kibana-and-apm) for adjusting compute resources for Elastic Maps Server.

## Scale out an Elastic Maps Server deployment

To deploy more than one instance of maps, all the instances must mount the data volume containing the basemap read only. When this is the case, scaling out is just a matter of increasing the `count` attribute.