Does this tool connect to my OCI account?

No. This tool runs entirely in your browser and generates configuration JSON that you can copy and paste into your infrastructure-as-code templates, CLI commands, or cloud console. It never connects to any cloud account or sends data externally.

Are the generated configurations production-ready?

The tool produces syntactically valid configurations based on current OCI service specifications. Always review generated configs against your organization security policies and test in a non-production environment before deploying.

OCI Service Mesh Config Builder

MonitoringOCI

Build OCI Service Mesh virtual service configurations with mTLS and traffic routing.

OCI Service Mesh Configuration

Build OCI Service Mesh virtual service configurations with mTLS, traffic routing, ingress gateways, and access policies.

Required Fields

compartmentIddisplayNamemesh.displayNamevirtualServices

{
  "compartmentId": "ocid1.compartment.oc1..aaaaaaaexample",
  "displayName": "prod-service-mesh",
  "description": "Service mesh configuration for microservices with mTLS and traffic management",
  "mesh": {
    "displayName": "prod-mesh",
    "compartmentId": "ocid1.compartment.oc1..aaaaaaaexample",
    "certificateAuthorities": [
      {
        "id": "ocid1.certificateauthority.oc1.iad.aaaaaaaexample"
      }
    ],
    "mtls": {
      "minimum": "STRICT"
    }
  },
  "virtualServices": [
    {
      "displayName": "orders-service",
      "meshId": "ocid1.mesh.oc1.iad.aaaaaaaexample",
      "hosts": ["orders.prod.mesh"],
      "defaultRoutingPolicy": {
        "type": "UNIFORM"
      },
      "mtls": {
        "mode": "STRICT",
        "maximumValidity": 45
      },
      "virtualDeployments": [
        {
          "displayName": "orders-v1",
          "serviceDiscovery": {
            "type": "DNS",
            "hostname": "orders-v1.prod.svc.cluster.local",
            "port": 8080,
            "protocol": "HTTP"
          },
          "accessLogging": {
            "isEnabled": true
          },
          "listeners": [
            {
              "port": 8080,
              "protocol": "HTTP",
              "idleTimeoutInMs": 300000,
              "requestTimeoutInMs": 15000
            }
          ]
        },
        {
          "displayName": "orders-v2",
          "serviceDiscovery": {
            "type": "DNS",
            "hostname": "orders-v2.prod.svc.cluster.local",
            "port": 8080,
            "protocol": "HTTP"
          },
          "listeners": [
            {
              "port": 8080,
              "protocol": "HTTP"
            }
          ]
        }
      ],
      "routeTable": {
        "displayName": "orders-route-table",
        "routeRules": [
          {
            "type": "HTTP",
            "path": "/api/v2/orders",
            "pathType": "PREFIX",
            "destinations": [
              { "virtualDeployment": "orders-v2", "weight": 90 },
              { "virtualDeployment": "orders-v1", "weight": 10 }
            ]
          }
        ]
      }
    }
  ],
  "ingressGateway": {
    "displayName": "prod-ingress",
    "meshId": "ocid1.mesh.oc1.iad.aaaaaaaexample",
    "hosts": [
      {
        "name": "api-host",
        "hostnames": ["api.example.com"],
        "listeners": [
          {
            "port": 443,
            "protocol": "TLS_PASSTHROUGH",
            "tls": {
              "mode": "TLS",
              "serverCertificate": {
                "certificateId": "ocid1.certificate.oc1.iad.aaaaaaaexample"
              }
            }
          }
        ]
      }
    ]
  },
  "accessPolicies": [
    {
      "displayName": "orders-access-policy",
      "rules": [
        {
          "action": "ALLOW",
          "source": { "type": "INGRESS_GATEWAY", "ingressGateway": "prod-ingress" },
          "destination": { "type": "VIRTUAL_SERVICE", "virtualService": "orders-service" }
        }
      ]
    }
  ],
  "freeformTags": {
    "platform": "service-mesh",
    "team": "platform-engineering"
  }
}

Generated Output

Output will appear here...

About This Tool

Build OCI Service Mesh virtual service configurations with mTLS and traffic routing. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

When to Use This Tool

•Generating oci service mesh configurations for new infrastructure deployments.
•Validating existing configurations against best practices before applying changes.
•Learning OCI service configuration patterns through interactive examples.
•Accelerating infrastructure-as-code development by producing correct JSON/YAML starting points.

Frequently Asked Questions

Does this tool connect to my OCI account?: No. This tool runs entirely in your browser and generates configuration JSON that you can copy and paste into your infrastructure-as-code templates, CLI commands, or cloud console. It never connects to any cloud account or sends data externally.
Are the generated configurations production-ready?: The tool produces syntactically valid configurations based on current OCI service specifications. Always review generated configs against your organization security policies and test in a non-production environment before deploying.

Related Learning Guides

Autonomous Database on OCI20 min read
OCI Cost Optimization Strategies18 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.