Payara Cloud

Private Cloud Subscriptions

Deploy Payara Cloud applications in your own Azure infrastructure while maintaining full control over your cloud resources and costs. This guide walks through Azure Private Cloud setup for deploying Jakarta EE applications across multiple regions in your Azure account.

Estimated setup time: 30 minutes

Before You Begin

Prerequisites
  • Azure subscription with Contributor role permissions to deploy managed applications

  • A public DNS domain that you control, where you can manage DNS zones

Technical Terms
AKS

Azure Kubernetes Service - managed container orchestration

vCPU

Virtual CPU core unit for computing resources

DNS Zone

Domain name system records for routing traffic

Pricing

Your costs will include:

  • Azure infrastructure costs for deployed resources

  • Payara Cloud runtime fee: $0.04 per vCPU-hour (minimum 0.25 core)

Setup Instructions

1. Payara Cloud Setup

  1. Create your Private Cloud Subscription:

    1. Visit Payara Cloud Signup

      image
    2. Accept terms and click Subscribe

      Terms confirmation
  2. Set up your first region:

    1. Enter a descriptive, unique region name

      Region setup
      Region names cannot be changed after creation
    2. Click Save Setting

  3. Locate connection details:

    1. Find and copy the connection string from Account Information

    Connection string

2. Azure Configuration

  1. Access Azure Marketplace:

    1. Search for Payara Cloud Customer Managed Region

    2. Select the available plan

      Plan selection
  2. Configure basic settings:

    Basic configuration
    Subscription

    Azure subscription for deployment

    Resource Group

    Container for managed application

    Region

    Azure deployment location

    Connection String

    Value copied from Payara Cloud

    Domain

    Your DNS subdomain

    Let’s Encrypt Email

    SSL certificate notifications

    Application Name

    Managed Application identifier

    Managed Resource Group

    Resource container name

  3. Set infrastructure options (Optional):

    Infrastructure settings
    AKS Cluster Name

    Azure Kubernetes Service cluster identifier

    Kubernetes Version

    Platform version selection

    Node Size

    VM type (4+ vCPUs recommended)

    Cluster Size Range
    • Minimum: Base node count

    • Maximum: Scale limit

    Log Analytics Workspace

    Monitoring workspace name

  4. Review and create:

    1. Verify all settings

      Review settings
    2. Click Create

  5. Monitor deployment:

    1. Watch progress indicators

      Deployment progress
    2. Check outputs after completion

      Deployment outputs
      Note the dns_nameservers values for the next step

3. DNS Setup

  1. Configure domain settings:

    1. Create NS records for your subdomain

    2. Add all dns_nameservers values

      DNS configuration

      Example DNS Configuration
      Subdomain: [your-region-name]
      Record type: NS
      TTL: 3600
      Values: [dns_nameservers values]

4. Final Verification

  1. Check Payara Cloud dashboard:

    1. Monitor region status

    2. Wait for "Active" indication

      Region verification
This subscription will only show your private regions. Public cloud regions are not accessible.

Troubleshooting Guide

Common Issues
  • Region activation delay

    • Normal time: 10-15 minutes

    • If exceeding 30 minutes, verify:

      • DNS configuration accuracy

      • Azure deployment status

      • Connection string correctness

Next Steps

  1. Create namespaces in your new region

  2. Deploy your first application

  3. Monitor Azure portal metrics

Keep your Azure infrastructure costs optimized by monitoring resource usage regularly.

Support

For technical assistance:

  • Check Payara Cloud documentation

  • Contact support through your subscription portal

  • Monitor Azure health dashboard for infrastructure status

Remember to:

  • Keep connection strings secure

  • Monitor resource usage

  • Review Azure security recommendations

Back to Top