---
schema_version: "1"
id: 2cc3e2707638e72e46c655adf7d2a1cd147a1f1d849483bf06ac1921912925a9
title: Creating Private Locations
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-functional-monitoring/afm-create-private-location.md
canonical_url: https://docs.mulesoft.com/api-functional-monitoring/afm-create-private-location
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 8fbe563e3190ea8a0375b304c9438206189a7c06ca880bf826981919246c3375
description: MuleSoft Documentation Site
latest: true
---
---
product: API Functional Monitoring
---

# Creating Private Locations

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

A private location is a Mule application that runs in an environment in CloudHub 1.0 or Cloudhub
2.0. You can run tests against APIs that are accessible only within the private location. The
private location environment might have an Anypoint VPC associated with it. You can create multiple
private locations in a single instance of Anypoint VPC.

You can create a private location when you:

- [Create a monitor](https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor)

- [Add a schedule](https://docs.mulesoft.com/api-functional-monitoring/afm-add-schedule) to a monitor

- [Modify a schedule](https://docs.mulesoft.com/api-functional-monitoring/afm-modify-schedule) in a monitor

This procedure explains how to create a private location when you modify a schedule.

For information about private locations and their uses, see
[Monitoring the Endpoints of Private APIs](https://docs.mulesoft.com/api-functional-monitoring/afm-monitoring-private-apis).

## Before You Begin

- Ensure that your Anypoint Platform organization has a subscription to Anypoint Virtual Private
  Cloud.

- Ensure that you have the following permission set in Access Management:

  - **Runtime Manager > Create Applications**

An Anypoint Platform administrator for your organization grants permission. See
[Manage Permissions](https://docs.mulesoft.com/access-management/managing-permissions).

## Create a Private Location

To create a private location:

1.  When creating a test or schedule, click the field under **Select location** and select **Create
    new location**.

2.  Name the location.

    The name can be up to 255 characters, and can include spaces and special characters.

3.  Select the environment for the tests.

4.  Select the deployment target.

5.  Complete the creation of the test or schedule. By default, it uses a 0.2 vCores replica size.

> [!NOTE] If your deployment target is set to any variant of CloudHub 2.0, a connected app is
> created automatically.

\+ While API Functional Monitoring is registering the private location, the status indicator is
yellow. After the location is successfully registered, the status indicator is green.

\+ . If the status indicator is red: .. Navigate to Runtime Manager and restart the
application/worker cloudhub application. .. Check the logs for the application/worker cloudhub
application to troubleshoot the issue.

## What to Do Next

You can now run tests from the private location, either by adding a schedule that uses the location
or by modifying an existing schedule to use it.

## See Also

- [Creating Monitors](https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor)

- [Adding Schedules](https://docs.mulesoft.com/api-functional-monitoring/afm-add-schedule)

- [Modifying Schedules](https://docs.mulesoft.com/api-functional-monitoring/afm-modify-schedule)

- [Managing Permissions](https://docs.mulesoft.com/access-management/managing-permissions)

- [Virtual Private Cloud](https://docs.mulesoft.com/cloudhub/virtual-private-cloud)