Skip to content
KiweelyKiweelyKiweely

Running a Stateless Workday MCP Container Inside Your Own AWS, GCP, or Azure VPC

Enterprises that prohibit HR API payloads from traversing a third-party vendor cloud don’t have to build a custom Workday MCP server from scratch. Deploy Kiweely Bridge’s signed, stateless container inside your own AWS, GCP, Azure, or Kubernetes VPC and lock egress in Workday Maintain IP Ranges.

  • By Kiweely
  • 5 min read
On this page

Regulated enterprises in banking, healthcare, defense, and public infrastructure often have a non-negotiable perimeter rule: live Workday HR, payroll, and staffing responses cannot pass through a third-party SaaS network hop, even in memory. Running a signed, stateless Workday MCP container inside your own AWS, GCP, Azure, or Kubernetes VPC satisfies that boundary without spending months writing SOAP XML parsers, WQL pagination, MCP OAuth 2.1 with PKCE, and semiannual Workday release patches in-house.

Because Kiweely Bridge (coming next) stores zero employee credentials and zero Workday payloads at rest, self-hosting it does not mean operating a sprawling stateful platform. You deploy one stateless container image behind your existing HTTPS load balancer and route outbound traffic through a static NAT IP allowlisted directly inside Workday.

Reference Architecture: Network Path Inside Your Cloud Perimeter

In a self-hosted VPC deployment, every network leg stays under your cloud security team’s direct inspection:

  1. Inbound MCP leg (TLS 1.3): Claude, ChatGPT, or Gemini (across Mac, Windows, web, and phone) connects to https://workday-mcp.internal-or-edge.yourcompany.com through your AWS ALB, Google Cloud Load Balancer, or Azure Application Gateway protected by your WAF rules.
  2. Stateless compute tier: One or more replicas of the signed Bridge container run in a private subnet with readOnlyRootFilesystem: true, no persistent volumes, and an AES-256-GCM token-sealing key injected from AWS Secrets Manager, GCP Secret Manager, or Azure Key Vault.
  3. Outbound Workday leg (Static NAT IP): Outbound requests to your Workday tenant’s REST, WQL (/wql/v1/data), SOAP, and custom RaaS endpoints route through a VPC NAT Gateway pinned to a reserved static Elastic/External IPv4 address.
  4. Workday tenant perimeter: Workday validates both the employee’s user-delegated OAuth Bearer token (Register API Client with PKCE) and the source IP against Maintain IP Ranges and Manage Authentication Policies.

Cloud-by-Cloud Deployment Matrix

Because the container requires no attached SQL database or cache cluster, it maps cleanly onto standard managed container services across all three major clouds plus Kubernetes:

Target Platform Compute Service Ingress & TLS Secret Injection Static Egress IP for Workday
Target PlatformAWS Compute ServiceAmazon ECS (Fargate) or EKS Ingress & TLSApplication Load Balancer + AWS WAF Secret InjectionAWS Secrets Manager / KMS Static Egress IP for WorkdayVPC Public NAT Gateway with Elastic IP
Target PlatformGoogle Cloud Compute ServiceCloud Run (Gen 2) or GKE Ingress & TLSExternal HTTPS Load Balancer + Cloud Armor Secret InjectionSecret Manager Static Egress IP for WorkdayCloud NAT with reserved static External IP
Target PlatformMicrosoft Azure Compute ServiceAzure Container Apps or AKS Ingress & TLSApplication Gateway + WAF v2 Secret InjectionAzure Key Vault (Managed Identity) Static Egress IP for WorkdayAzure NAT Gateway with Public IP Prefix
Target PlatformKubernetes Compute ServiceStandard Deployment (2+ replicas) Ingress & TLSGateway API / Ingress Controller Secret InjectionExternal Secrets Operator Static Egress IP for WorkdayEgress Gateway or cloud VPC NAT

Hardened Kubernetes Deployment Manifest Pattern

Security engineers reviewing a self-hosted container look first at filesystem mutability, Linux capabilities, and volume mounts. A truly stateless Workday MCP worker runs unprivileged with zero writable disk paths:

Works
apiVersion: apps/v1
kind: Deployment
metadata:
  name: kiweely-bridge-mcp
  namespace: workday-ai
spec:
  replicas: 2
  selector:
    matchLabels:
      app: kiweely-bridge-mcp
  template:
    metadata:
      labels:
        app: kiweely-bridge-mcp
    spec:
      automountServiceAccountToken: false
      containers:
        - name: bridge
          image: registry.kiweely.com/bridge/mcp-worker@sha256:verified_cosign_digest
          ports:
            - containerPort: 8443
          envFrom:
            - secretRef:
                name: bridge-sealing-keys
          resources:
            requests:
              cpu: "500m"
              memory: "512Mi"
            limits:
              cpu: "1000m"
              memory: "1Gi"
          securityContext:
            runAsNonRoot: true
            runAsUser: 65532
            readOnlyRootFilesystem: true
            allowPrivilegeEscalation: false
            capabilities:
              drop: ["ALL"]
      volumes: []

Three details matter operationally:

  • Cosign / digest pinning: Pinning @sha256:... alongside container signature verification guarantees your cluster runs the exact audited binary.
  • readOnlyRootFilesystem: true and volumes: []: The Linux kernel itself denies any attempt to write worker records, WQL rows, or temporary files to disk.
  • Predictable memory ceiling: Because responses stream through RAM and apply deterministic field stripping on the fly without caching historical sessions, a 512 MiB–1 GiB limit handles high-concurrency employee queries cleanly.

Locking Workday Egress with Maintain IP Ranges

Running the container inside your VPC gives you full ownership of the outbound IP address that hits Workday. Lock your Workday API client to that exact IP in four steps (always test in Sandbox first):

  1. Verify image signature and deploy to Sandbox subnet: Start the container pointing at your Workday Sandbox host and record the /32 IPv4 address of your VPC NAT Gateway.
  2. Register the range in Workday: Run the Maintain IP Ranges task in Workday, add an entry (for example, Corp_VPC_Workday_AI_NAT), and enter your static /32 CIDR.
  3. Bind in Manage Authentication Policies: Open Manage Authentication Policies in Workday. Ensure your top-priority administrator break-glass rule remains intact so you never lock out human SSO admins, then configure the authentication condition governing API client traffic to require the Corp_VPC_Workday_AI_NAT IP range.
  4. Activate and verify negative tests: Run Activate Pending Authentication Policy Changes. Test an OAuth Authorization Code + PKCE call through your VPC container (expect 200 OK), then attempt to replay a valid Bearer token from a workstation outside the VPC (expect immediate Workday rejection—see troubleshooting 401 and authentication policy blocks).

Comparing Hosting Modes: Kiweely Cloud vs. Dedicated vs. Self-Hosted vs. DIY

Before committing engineering headcount to building a custom Workday MCP server in-house, compare what your team owns across each model (full vendor comparison on /bridge/compare):

Operational Responsibility Kiweely Cloud Dedicated Single-Tenant Self-Hosted Container Build In-House From Scratch
Operational ResponsibilityStored HR payloads / tokens Kiweely CloudZero Dedicated Single-TenantZero Self-Hosted ContainerZero Build In-House From ScratchYours to design and audit
Operational ResponsibilityWorkday data network hop Kiweely CloudStateless Kiweely Cloud RAM Dedicated Single-TenantIsolated single-tenant pool Self-Hosted Container100% inside your VPC Build In-House From ScratchInside your VPC
Operational ResponsibilityStatic IP for Maintain IP Ranges Kiweely CloudShared multi-region egress Dedicated Single-TenantIncluded (dedicated IP) Self-Hosted ContainerIncluded (your VPC NAT IP) Build In-House From ScratchYour VPC NAT IP
Operational ResponsibilityMCP OAuth 2.1, PKCE & browser write cards Kiweely CloudBuilt in Dedicated Single-TenantBuilt in Self-Hosted ContainerBuilt in Build In-House From ScratchWeeks of engineering + AppSec review
Operational ResponsibilityREST, WQL, SOAP & RaaS adapters Kiweely CloudBuilt in Dedicated Single-TenantBuilt in Self-Hosted ContainerBuilt in Build In-House From ScratchWeeks of WSDL/WQL pagination code
Operational ResponsibilitySemiannual Workday release upkeep Kiweely CloudAutomatic Dedicated Single-TenantAutomatic Self-Hosted ContainerSigned container updates Build In-House From ScratchOngoing engineering maintenance
Operational ResponsibilityPricing Kiweely Cloud$499 / $1,499 / $3,999 per mo by company size (free on personal dev tenant) Dedicated Single-TenantEnterprise (by quote) Self-Hosted ContainerEnterprise (by quote) Build In-House From ScratchEngineering salaries + on-call

Choosing the Right Deployment Tier

  • Choose Kiweely Cloud ($499/mo up to 1,000 Workday employees, $1,499/mo for 1,001–5,000, $3,999/mo for 5,001–20,000, unlimited calls across Production and all Sandbox/implementation tenants; free for one person on their own Workday developer tenant) when you want zero infrastructure to manage alongside zero stored payloads and credentials.
  • Choose Dedicated single-tenant (Enterprise, by quote) when you want Kiweely to operate the runtime while giving your Workday security team an isolated worker pool and a dedicated static outbound IP for Maintain IP Ranges.
  • Choose Self-hosted container (Enterprise, by quote) when corporate policy mandates zero external network hops for Workday data—giving your cloud team a signed, stateless container inside AWS, GCP, Azure, or Kubernetes while keeping Kiweely Bridge’s AI admin setup, field-level RAM redaction, and out-of-band browser write checks (see /bridge/security, coming next).

Frequently asked questions

Does self-hosting the Kiweely Bridge container require provisioning PostgreSQL, Redis, or persistent disks?

No. Because Bridge seals user-delegated Workday OAuth grants inside the client token with AES-256-GCM and streams responses in RAM without storing payloads, the container requires zero database tables, zero Redis caches, and zero persistent volume mounts.

How do cloud-hosted AI assistants like Claude, ChatGPT, and Gemini reach a container inside our VPC?

Remote MCP servers expose an HTTPS endpoint over TLS 1.3 via your existing enterprise ingress (AWS ALB + WAF, GCP Cloud Load Balancing + Cloud Armor, or Azure Application Gateway), while all outbound calls to Workday exit through your dedicated VPC NAT static IP.

How do we lock Workday so API tokens only work from our VPC?

Reserve a static Elastic/External IP on your VPC NAT gateway, add that IPv4/32 address in Workday's Maintain IP Ranges task, and attach it to an authentication rule in Manage Authentication Policies before running Activate Pending Authentication Policy Changes.

Do we lose the AI admin setup workflow or twice-yearly Workday release updates if we self-host?

No. Self-hosted Enterprise deployments keep the same AI admin agent workflow for Sandbox Register API Client setup, field redaction rules, and persona testing, and pull signed container image updates calibrated for Workday's semiannual releases.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.