Skip to content

Deployment

Since the connector is designed as a Docker microservice, it can be deployed in any cloud, for example, using a cloud-specific utility. Below there are examples of scripts that you can use, but you can write your own that are simpler or more complex to suit your needs.

Important!

  • Hosting expenses for your connectors deployed in cloud platforms won't be covered by PortaOne.
  • There is a local deployment option, at no extra cost, to consider:

Example for GCP: deploy as a Cloud Run. Official guide on how to deploy Cloud Run services you can find here.

A Cloud Run service URL typically follows the format https://[TAG---]SERVICE_IDENTIFIER.run.app. The SERVICE_IDENTIFIER is a unique, stable identifier for the service, and the TAG refers to the traffic tag of the specific revision. The SERVICE_IDENTIFIER includes a random string and the region shortcut.

https://[TAG---]SERVICE_NAME-PROJECT_NUMBER.REGION.run.app

where:

  • TAG is the optional traffic tag for the revision that you are requesting.
  • PROJECT_NUMBER is the Google Cloud project number.
  • SERVICE_NAME is the name of the Cloud Run service.
  • REGION is the name of the region, such as us-central1.

Example for AWS: deploy as an App Runner. Official guide on how to deploy App Runner services you can find here.

An App Runner service URL typically follows the format https://[service-id].[region].awsapprunner.com where service-id is a unique identifier for your service and region is the AWS region where your service is hosted.

For example: https://abcd1234efgh.us-east-1.awsapprunner.com

Infrastructure Considerations

The default deployment of NSPS, PortaBilling, and Connector/Core is intended to run in a public internet environment, where services can communicate freely over the network. However, in specific cases, it may be necessary to restrict public access to components for security reasons.

At this time, we can provide a static IP address used by NSPS to make requests to both the connector and PortaBilling.

VPN connectivity is not currently supported and is under consideration.