0 / 0
Firewall access for DataStage
Last updated: Jan 12, 2024
Firewall access for DataStage

With DataStage, you can access data that is located behind a firewall. For example, you can access data stores that are hosted by a third-party cloud provider. Use the cloud provider’s inbound firewall rules to allow the IP addresses for the DataStage subnet and for the Cloud Pak for Data as a Service IP addresses.

In addition to the IP addresses for Cloud Pak for Data as a Service, DataStage requires the IP addresses for the DataStage subnet for your region to be added to inbound firewall access rules.

DataStage subnet IP addresses

You can allow inbound access through a firewall for DataStage subnets in the Dallas and Frankfurt regions. Use the following CIDR ranges:

Dallas:

  • 169.48.218.176/28
  • 150.238.4.224/28
  • 169.62.176.16/28

Frankfurt:

  • 149.81.108.32/28
  • 161.156.88.16/28
  • 158.177.22.176/28

Configure inbound traffic through a firewall

You configure inbound traffic through a firewall in the security configuration screens for the cloud provider. The procedure will vary for each cloud provider and network. Enter the subnet IP ranges for your region into the appropriate inbound firewall rules.

Parent topic: Configuring firewall access

Generative AI search and answer
These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more