Table of Contents

Search

  1. Preface
  2. Introduction to Amazon S3 V2 Connector
  3. Connections for Amazon S3 V2
  4. Amazon S3 V2 sources and targets
  5. Mappings and mapping tasks with Amazon S3 V2
  6. Migrating a mapping
  7. Upgrading to Amazon S3 V2 Connector
  8. Data type reference
  9. Troubleshooting

Amazon S3 V2 Connector

Amazon S3 V2 Connector

Bypass the proxy server

Bypass the proxy server

If your organization uses an outgoing proxy server to connect to the internet, the Secure Agent connects to Informatica Intelligent Cloud Services through the proxy server.
However, if you want to exclude certain IP addresses and host names from the proxy, you can bypass the proxy. Set the
InfaAgent.NonProxyHost
property in the
proxy.ini
file and the
-Dhttp.nonProxyHosts
property in the JVM options of the Secure Agent properties and include the IP addresses and host names that you want to exclude.
The following table shows the proxy setting for configuring proxy using the
proxy.ini
file and the JVM options.
Proxy configuration
Proxy Flag Setting
Proxy.ini
InfaAgent.NonProxyHost=localhost|
<your_bucket_name>.s3.
|127.*|[\:\:1]
For example, to bypass a single S3 Bucket
iam.qa.bucket
, use the following proxy setting:
InfaAgent.NonProxyHost=localhost|
iam.qa.bucket.s3.
|127.*|[\:\:1]
To bypass all S3 buckets, use the following proxy setting:
InfaAgent.NonProxyHost=localhost|
*.s3.*
|127.*|[\:\:1]
JVM option
-Dhttp.nonProxyHosts=localhost|
<your_bucket_name>.s3.
|127.* |[\:\:1]
For example, to bypass a single S3 Bucket,
iam.qa.bucket
, use the following proxy setting:
-Dhttp.nonProxyHosts=localhost|
iam.qa.bucket.s3.
|127.*|[\:\:1]
To bypass all S3 buckets, use the following proxy setting:
-Dhttp.nonProxyHosts=localhost|
*.s3.*
|127.*|[\:\:1]

Bypass the proxy server in advanced mode

To bypass the proxy server, you must update the
NonProxyHost
in
proxy.ini
file. You can set the property in the agent core path to configure the
NonProxyHost
in the advanced cluster configuration.
To bypass the proxy at the Amazon S3 endpoint, perform the following steps:
  1. Edit the
    proxy.ini
    file and set the property in the
    NonProxyHost
    with the cluster region.
  2. Enter the appropriate region name in the property in the following format:
    InfaAgent.NonProxyHost=localhost|127.*|[\:\:1]|169.254.169.254|.<REGION_NAME>.elb.amazonaws.com|*.<REGION_NAME>.elb.amazonaws.com
    For the US West region, the following example shows how you can update the non-proxy host for a specific region in the
    proxy.ini
    file:
    InfaAgent.NonProxyHost=localhost|127.*|[\:\:1]|169.254.169.254|.us-west-2.elb.amazonaws.com|*.us-west-2.elb.amazonaws.com|s3.us-west-2.amazonaws.com|*.s3.us-west-2.amazonaws.com|s3.amazonaws.com
  3. After you edit the
    proxy.ini
    file, you must set the property
    ccs.enable.storage.proxy.settings
    to false in the runtime properties of the advanced cluster. Perform the following steps to set the property:
    1. Go to the
      Administrator
      service.
    2. In the
      Advanced Clusters
      page, select the name of the configuration that you want to edit from the list of advanced configurations.
    3. Set the property
      ccs.enable.storage.proxy.settings
      to false and save the cluster configuration in the
      Runtime Properties
      for the particular cluster.
      The following image shows the cluster runtime properties:
      proxy ini flag for S3 bypass

0 COMMENTS

We’d like to hear from you!