Table of Contents

Search

  1. Preface
  2. Advanced clusters
  3. Setting up AWS
  4. Setting up Google Cloud
  5. Setting up Microsoft Azure
  6. Setting up a self-service cluster
  7. Setting up a local cluster
  8. Advanced configurations
  9. Troubleshooting
  10. Appendix A: Command reference

Advanced Clusters

Advanced Clusters

Step 6. Allow domains in AWS

Step 6. Allow domains in AWS

When the Secure Agent creates an
advanced cluster
in an AWS environment, the cluster nodes need access to certain domains to fetch artifacts, such as machine images, and to access sources and targets.
Add the following domains to the outbound allowlists for your security groups:
artifacthub.informaticacloud.com .s3.amazonaws.com .s3.<staging bucket region>.amazonaws.com awscli.amazonaws.com
You need to install AWS CLI as part of the cluster creation.
If you use an Amazon S3 or Amazon Redshift object as a source or target, allow inbound traffic to each source and target bucket that the agent will access.
If you use GPU-enabled worker instances, also allow the following domains:
.docker.com .docker.io .nvidia.com .nvidia.github.io
Also allow the appropriate region for AWS:
sts.amazonaws.com
To enable a regional endpoint connection, contact Informatica Global Customer Support to get the required custom property setting.
If your organization does not use an outgoing proxy server, contact Informatica Global Customer Support to disable the proxy settings used for S3 access.

0 COMMENTS

We’d like to hear from you!