1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. Reducing the Ingress Range for Siebel Cloud Manager

Reducing the Ingress Range for Siebel Cloud Manager

Before you run SCM to create an environment, you can optionally reduce the ingress range to tighten network security for SCM. The procedure below uses siebel-cm as the example compartment name.

Related Topics

Downloading and Installing Siebel Cloud Manager

Using Advanced Network Configuration

To reduce the ingress range for SCM

  1. Navigate to Instances.

  2. Select the prefix-siebel-cm compartment in the left side of screen to list the newly created instances.

  3. Drill down to the prefix-siebel-cm instance with public IP specified.

  4. Drill down to the link prefix-siebel-cm-subnet given as subnet under Primary VNIC header.

  5. Drill down on the link security-list-for-cm.

  6. Click Edit Ingress Rules.

  7. (Optional) Change the 0.0.0.0/0 for Source CIDR for Destination Port 16690 to the desired IP Addresses/Range.

    Note: Ingress port 16690 is by default added to the security list with 0.0.0.0/0 to open for internet. It is recommended to change this CIDR block to the required limited IP addresses or CIDR blocks.

    Stack apply job logs have the URL endpoint for the REST application, or you can get the IP address info from the Compute instance of SCM (prefix-siebel-cm) inside prefix-siebel-cm compartment, where prefix is the input given during stack creation.