Skip to main content

Overview

This quickstart demonstrates how workloads communicate internally with automatic mTLS encryption. By default, workloads are isolated and reject internal traffic. You’ll configure firewall rules to enable secure service-to-service calls. What you’ll accomplish:
  • Deploy a new workload that calls an existing service
  • Observe the default deny behavior
  • Configure internal firewall rules to allow communication
  • Verify secure service-to-service calls

Prerequisites

How Internal Communication Works

Workloads communicate using internal endpoints following this pattern:
http://WORKLOAD_NAME.GVC_NAME.cpln.local:PORT
All internal traffic is automatically encrypted with mTLS. No certificates to manage. So far, you’ve created a GVC (quickstart-gvc) and deployed a workload (hello-world). Now you’ll create a new workload that communicates with the existing hello-world workload.

Step 1: Create the Caller Workload

1

Navigate to Workloads

Click Workloads in the left menu, then click New.
2

Configure workload basics

  1. Name: caller
  2. Make sure quickstart-gvc is selected in the GVC dropdown
3

Configure container

  1. Click Containers in the left pane
  2. Select External and enter the image: cplnquickstarts/service-to-service-quick-start:1.1
  3. Under Ports, set Protocol to http and Number to 8080
4

Configure firewall and create

  1. Click Firewall in the left pane
  2. Click Make Public
  3. Click Create

Step 2: Observe Default Deny Behavior

1

Wait for workload to be ready

The caller workload shows Ready in Workload Health.
2

Open the caller workload

Navigate to the caller workload and click Open next to the Global Endpoint.
3

Test internal call

Add this query parameter to the caller URL:
?url=http://hello-world.quickstart-gvc.cpln.local:8080
The request will timeout and fail because the hello-world workload blocks internal traffic by default.

Step 3: Configure Internal Firewall

1

Navigate to hello-world workload

Click Workloads in the left menu and select hello-world.
2

Configure firewall

  1. Click Firewall in the left pane
  2. Under the Internal tab, select Same GVC for the Inbound Allow Type
  3. Click Update

Step 4: Verify Communication

1

Wait for redeployment

The hello-world workload redeploys with new firewall rules (1-2 minutes).
2

Test again

Refresh the caller page with the URL parameter. The hello-world workload now responds:
Response from URL:

---
Hello World!
---

Internal Firewall Options

OptionDescription
None (default)Block all internal traffic
same-gvcAllow from any workload in the same GVC
same-orgAllow from any workload in the organization
workload-listAllow from specific workloads only
The workload-list option requires view permission on the allowed workloads.

Internal Endpoint Format

Workloads communicate using internal DNS:
http://WORKLOAD.GVC.cpln.local:PORT
Examples:
  • http://api.production-gvc.cpln.local:8080
  • http://cache.quickstart-gvc.cpln.local:6379

What You’ve Learned

  • Workloads are isolated by default - internal traffic is blocked
  • mTLS is automatic - no certificate configuration needed
  • Firewall rules control which workloads can communicate
  • Internal endpoints use the .cpln.local domain

Clean Up

To delete all resources created in the quickstart series:
  1. Navigate to GVCs, select quickstart-gvc, and from Actions click Delete
  2. Navigate to Domains, select your domains, and from Actions click Delete
Remember to remove the DNS records from your DNS provider after deleting the domains.

Next Steps