# Error pushing Elastic Synthetic monitor: “Invalid locations specified” for private location

**URL:** https://discuss.elastic.co/t/error-pushing-elastic-synthetic-monitor-invalid-locations-specified-for-private-location/379326
**Category:** Synthetics
**Created:** [June 19, 2025, 1:32pm UTC](https://discuss.elastic.co/t/error-pushing-elastic-synthetic-monitor-invalid-locations-specified-for-private-location/379326 "2025-06-19T13:32:45Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![shrikant.dandge](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@shrikant.dandge](https://discuss.elastic.co/u/shrikant.dandge)
#### Post date: [June 19, 2025, 1:32pm UTC](https://discuss.elastic.co/t/error-pushing-elastic-synthetic-monitor-invalid-locations-specified-for-private-location/379326/1 "2025-06-19T13:32:45Z")

</div>

Hi team,

I'm trying to push a private location monitor using the Elastic Synthetics CLI to our Kibana instance, but consistently receive this error:

```auto
Couldn't save or update monitor because of an invalid configuration.: monitor(mema_test_cli)
Invalid locations specified. Elastic managed Location(s) 'AS_OB_Multistep' not found. No Elastic managed location available to use.

```

Here’s what I’ve tried:

✅ Our private location exists — as shown in Fleet and Synthetics UI:

```auto
{
  "label": "AS_OB_Multistep",
  "id": "30ec0047-5201-4115-b35b-d51fd30c938a",
  "agentPolicyId": "30ec0047-5201-4115-b35b-d51fd30c938a"
}

```

My `synthetics.config.ts` contains:

```auto
monitor: {
  schedule: 10,
  locations: ['30ec0047-5201-4115-b35b-d51fd30c938a'], // UUID from private location
  name: 'Mema Journey_cli',
  space: 'govmeetings-prod',
}

```

❌ I tried adding `privateLocations: true`, which resulted in a JS error:

```auto
_monitorLocations$pri.map is not a function

```

❌ Without that field, I get:

```auto
Invalid locations specified. Elastic managed Location(s) 'AS_OB_Multistep' not found.

```

I’m using:

- Elastic Synthetics CLI: `@elastic/synthetics` (latest via `npx`)
- Kibana URL: `https://elastic.granicuslabs.com`
- Kibana Space: `govmeetings-prod`

* * *

**🤔 Questions:**

- Is there a bug with private location UUIDs not being correctly recognized in the `push` flow?
- Is there any other required field for private location monitors?

* * *

**🧪 Bonus Info:**  
Running `curl` on the private location endpoint confirms it exists and matches the space:

```auto
curl -X GET "https://elastic.granicuslabs.com/s/govmeetings-prod/api/synthetics/private_locations" \
  -H "Authorization: ApiKey $SYNTHETICS_API_KEY" \
  -H "kbn-xsrf: true" | jq

```

* * *

---

<div class="post-metadata">

### Author: ![shahzad31](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shahzad31/32/51637_2.png) [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [June 19, 2025, 3:52pm UTC](https://discuss.elastic.co/t/error-pushing-elastic-synthetic-monitor-invalid-locations-specified-for-private-location/379326/2 "2025-06-19T15:52:25Z")

</div>

Hello,  
Welcome to elastic discuss forum.  
you need to specify private locations in private locations attribute not in locations  
` privateLocations: ["AS_OB_Multistep"],`

I hope this helps.