Configure private connectivity for enhanced security.
Google Cloud Platform to Google Cloud Platform
Implement private connectivity between your services running on Google Cloud and your commercetools Projects hosted in one of the Google Cloud Regions.
Private Service Connect
With Private Service Connect you can configure a secure, private connection to commercetools APIs. By creating a connection endpoint that targets the commercetools Private Service Connect service, you ensure that traffic between commercetools and your services remains private.
Create a Private Service Connect endpoint
Before setting up a Private Service Connect endpoint, ensure that you have:
- A functioning Google Cloud Platform (GCP) project with Compute Engine and Cloud DNS APIs enabled.
- Configured the correct firewall rules: ensure egress firewall rules allow traffic to the Private Service Connect endpoint's internal IP address. If you have deny rules or hierarchical policies, adjust them accordingly.
When creating a new endpoint, you must have the URI of the service attachment for the service you want to connect to. For connecting to the commercetools service attachment, use the following URIs depending on the Region your commercetools Project is hosted in:
| Region | Target service attachment URI |
|---|---|
| North America (Google Cloud, Iowa) | projects/ctp-production-us/regions/us-central1/serviceAttachments/api-private-service-connect-ilb |
| Europe (Google Cloud, Belgium) | projects/ctp-production-eu/regions/europe-west1/serviceAttachments/api-private-service-connect-ilb |
| Australia (Google Cloud, Sydney) | projects/ctp-production-au/regions/australia-southeast1/serviceAttachments/api-private-service-connect-ilb |
Configure DNS
The commercetools service attachment is configured to accept requests under the
private.commercetools.com domain in your GCP Region. This means that API calls must resolve DNS names to the private IP provided by the Private Service Connect endpoint you created. The recommended solution in GCP is to configure a DNS private zone that resolves the API URLs.As an example, if your service is running in the Europe (Google Cloud, Belgium) Region, your DNS zone would have the following entries mapped to your endpoint's IP address:
auth.europe-west1.gcp.private.commercetools.comfor authentication.api.europe-west1.gcp.private.commercetools.comfor HTTP API requests.import.europe-west1.gcp.private.commercetools.comfor Import API requests.
Private Service Connect provides private connectivity for your applications running in GCP to commercetools APIs. However, requests to your commercetools Projects are still possible from the public internet.
For further help in setting up and testing Private Service Connect, refer to the Access published services through endpoints guide.
Extend with other clouds
If you want to use API Extensions implemented on your own infrastructure hosted on-premises or clouds other than the Google Cloud Platform (GCP), you can do this with the help of GCP project acting as a bridge between your Composable Commerce Project and your own cloud.
This section explains how you setup and configure the Cloud Run service on your own GCP project to forward all extension requests from the commercetools GCP platform to your extension API through the private network. The final setup will look like this:
Loading...
Deploy a reverse proxy service on Cloud Run
Before setting up, ensure that you have:
- A functioning Google Cloud Platform (GCP) project with Compute Engine and Cloud Run APIs enabled.
- The
accesscontextmanager.*permissions in your GCP organization. - Configured network connections between your internal API network and your VPC on GCP via Google Cloud Connectivity.
Follow the Deploy container images and Frontend proxying using Nginx guides to deploy a Nginx reverse proxy on Cloud Run.
server {
listen 8080;
server_name _;
location / {
proxy_pass http://your.api.example.com;
proxy_set_header Host $proxy_host;
proxy_set_header X-Real-Ip $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_redirect off;
}
}
upstream your.api.example.com {
server x.x.x.x:80 fail_timeout=10s;
}
VPC Service Control
Follow the create a service perimeter guide to restrict the source GCP project for which only commercetools can accesss your Cloud Run Admin API by configuring the ingress policy.
To configure the ingress policy, specify the commercetools GCP project number as the source of your ingress policy rule.
Contact your Customer Success Manager to obtain the required commercetools GCP project number.
To ensure your user accounts have access on Cloud Run service, create an ingress policy for identities in your organization to have access to the Cloud Run Admin API.
Create API Extension
Create an API Extension with a HTTP Destination targeting the extension API in your own cloud.
After successful completion of these steps, the commercetools GCP platform can call your extension API in your own cloud through the private network.