Skip to content

Location Services in a cloud-to-cloud setup

This page explains the requirements for Location Services in a cloud-to-cloud (C2C) setup.

A C2C setup requires a proxy server, which has additional requirements for nRF Cloud:

This page does not outline how to set up a proxy server, as this varies depending on your use case.

Access

These operations are available only to the team owner.

Declaring proxy server use

When you sign up for or upgrade to an nRF Cloud Pro plan, you are prompted to declare the number of devices that will access the different components of Location Services through a proxy server.

You can either declare this when you sign up or upgrade, or later from the Plan Settings page. See Managing your nRF Cloud plan.

Service key and token

Once you declare the number of devices using nRF Cloud services through a proxy server, you need to generate a service key.

When you generate the service key, nRF Cloud also generates a JWT signed with the service key. This service token is valid for one year. You can also generate your own JWT and sign it with the generated service key instead and define your own validity period.

A JWT signed with a service key gives you access to all Location Services through a proxy server.

Access

Only the team owner can generate a service key and token.

C2C example

See the C2C cellular location guide for an example implementation.