How to: Install and Configure

Informatica Intelligent Cloud

Services in Google Cloud

© Copyright Informatica LLC 2019, 2023. Informatica and the Informatica logo are trademarks or registered
trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of
Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html
Abstract
You can use all the features of Informatica Intelligent Cloud Services℠ through the Secure Agent on a Google Cloud
Platform (GCP) instance. This article describes how to install and set up a Secure Agent with a GCP virtual instance to
use Informatica Intelligent Cloud Services.

Supported Versions
• Informatica Intelligent Cloud Services GCP Beta (Dec 2019)

Table of Contents
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Cost and licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Deployment prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Supported configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
IICS on GCP architecture diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
IICS deployment in the GCP Cloud with the GCP Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Deployment parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Steps to generate an install token. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Steps to register a new user with an Informatica Intelligent Cloud Services account. . . . . . . . . . . . . . . . . 11
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Overview
Use the Informatica Secure Agent on a GCP virtual instance to connect to your Informatica Intelligent Cloud Services
(IICS) account to leverage your computing needs. You can deploy as many Secure Agents as your license permits using

2
this solution. This article explains how to provide IICS registration account details and add a new agent in your IICS
account.

Intended audience
This article is written for users that are familiar with Google Cloud Platform services and Informatica Intelligent Cloud
Services. Users should have a basic understanding of how identity and access work in Google Cloud Platform.

Cost and licensing

Users need to acquire Informatica Intelligent Cloud Services license before deploying this product from Google Cloud
Marketplace. Users are responsible for Google Cloud service usage charges such as compute engine, network egress,
public IP allocation, etc. Google Cloud service charges are separate from the Informatica licensing fee.

Deployment prerequisites
Before you deploy Informatica Intelligent Cloud Services in the GCP cloud, verify that you have performed the
prerequisite steps and that the network requirements are met.

Verify that you have performed the following steps:

• You have a valid account with Google Cloud Marketplace.

• You have a valid IICS account.
• Apart from roles and network, to work with GCP, you have enabled the following APIs in the Google cloud
project:
- Compute Engine API

- Cloud Deployment Manager V2 API

- Cloud Runtime Configuration API

- Identity and Access Management (IAM) API

- Cloud Resource Manager API

- Google Cloud DNS API

- Service Usage API

- Google Cloud APIs

- Google Cloud Storage JSON API

- IAM Service Account Credentials API

• The <project-number>@cloudservices.gserviceaccount.com service account has the owner role attached to it
or that it has at least the following roles:
- Deployment Manager Editor

- Deployment Manager Type Editor

- Project IAM Admin

- Service Account Admin

- Service Account Key Admin

- Compute Admin

- Cloud Runtime Config Admin

3
 - Compute Storage Admin

Note: The service account mentioned above is used by the deployment manager, so specified roles are required. All
VMs created by the deployment will be attached to a different service account (custom created role attached) which is
also created at the time of deployment.

The custom role has the following permissions:

runtimeconfig.configs.create
runtimeconfig.configs.delete
runtimeconfig.configs.get
runtimeconfig.configs.getIamPolicy
runtimeconfig.configs.list
runtimeconfig.configs.setIamPolicy
runtimeconfig.configs.update
runtimeconfig.operations.get
runtimeconfig.operations.list
runtimeconfig.variables.create
runtimeconfig.variables.delete
runtimeconfig.variables.get
runtimeconfig.variables.getIamPolicy
runtimeconfig.variables.list
runtimeconfig.variables.setIamPolicy
runtimeconfig.variables.update
runtimeconfig.variables.watch
runtimeconfig.waiters.create
runtimeconfig.waiters.delete
runtimeconfig.waiters.get
runtimeconfig.waiters.getIamPolicy
runtimeconfig.waiters.list
runtimeconfig.waiters.setIamPolicy
runtimeconfig.waiters.update
logging.logEntries.create

The network must meet the following requirements:

• Google Network must have one subnetwork created in the intended deployment region.
• At least one route must be present with destination to the selected subnetwork CIDR range.
• The selected subnetwork must have Google Cloud private access enabled if you do not intend to use public IPs
for the VM, and it must have access to the Internet via any gateway.

Supported configurations
Operating systems:

• Windows Server 2016 Datacenter

• Red Hat Enterprise Linux 7.6

4
Instance size:

• Default n1-standard-4
The following table lists all resources created with sizing details:

Resource Sizing

Firewall rule 1 firewall rule

Service account 1 service account

Custom rule 1 custom rule

Cloud function 1 cloud function

Runtime config 1 runtime config

Runtime waiter 1 runtime waiter

VM instance 1 (4 vCPU and 15 GB RAM) Informatica Secure Agent VM.

CPU and RAM can be increased by the user.

IICS on GCP architecture diagram

The following diagram shows Informatica Intelligent Cloud Services on GCP architecture with the GCP Marketplace:

5
IICS deployment in the GCP Cloud with the GCP Marketplace
1. Search for Informatica IICS Secure Agent on the Google Cloud Marketplace and click the found product link.
2. An overview page appears, as shown in the following image:

3. Click Launch on Compute Engine.

4. Select the appropriate project.

6
 The New Informatica Intelligent Cloud Services Secure Agent deployment page is displayed, as shown in the
following image:

5. Enter the deployment parameters including the deployment name, VM configuration properties, networking
properties, and Informatica Intelligent Cloud Services account details.
6. Click Deploy to start the deployment.

7
When the deployment finishes successfully, the output screen displays the following field:

Field Description

Secure Agent Public IP / Private DNS DNS or IP to access the Informatica Secure Agent instance.

Deployment parameters
Configure the deployment parameters on the New Informatica Intelligent Cloud Services Secure Agent deployment
page.

The following tables describe the deployment parameters:

Deployment Name

Parameter Description

Deployment Name Google Cloud deployment manager managed field.

Virtual Machine Configuration properties

Parameter Description

Region Google Cloud Platform zone in which the deployment should take place.

Operating System Operating system for the Secure Agent to deploy.

Select Microsoft Windows Server 2016 or Red Hat Linux 7.6.

Machine Type Select the CPUs and RAM sizing for the instance of the Secure Agent machine.

Networking properties

Parameter Description

Network Select the network in which all resources will be created.

Subnetwork Select the subnetwork within the zone.

Informatica Intelligent Cloud Services Account Details

Parameter Description

Username IICS account user name.

Token Install token used to deploy the Secure Agent.

To get the token, log in to your Informatica Intelligent Cloud Services account, open the Administrator
service, and click Generate Install Token on the Runtime Environments page.

8
Steps to generate an install token
To deploy a Secure Agent in Google Cloud Platform, you need an install token. Get the install token from the Runtime
Environments page in the Administrator service, and paste it in the Token field in the New Informatica Intelligent Cloud
Services Secure Agent deployment page in Google Cloud Platform.

1. Log in to your Informatica Intelligent Cloud Services account.

You will see the My Services page, as shown in the following image:

2. Choose Administrator.
3. Open the Runtime Environments page, as shown in the following image:

4. Click Generate Install Token.

9
 An install token is generated, as shown in the following image:

5. Click Copy to copy the token.

After you copy the token, you can paste it in the Token field on the New Informatica Intelligent Cloud Services Secure
Agent deployment page in Google Cloud Platform.

10
Steps to register a new user with an Informatica Intelligent Cloud
Services account
1. Go to https://dm2p-us.informaticacloud.com/ma/register and fill in the form, as shown in the following
image:

You will get a registration confirmation email that contains a link to create your password.

11
2. After you have created your password, log in to your account using the region of the POD you chose at the
time of registration.

Troubleshooting

I encountered a deployment error related to APIs or permissions.

If you encounter an error related to API or permission, the deployment manager will clearly show those during
deployment. Rectify those and try again.

The deployment timed out.

In rare cases, if the deployment doesn't receive a success signal within 30 minutes, it goes into a failed state.
However, that doesn't mean that the Secure Agent didn't get created or added to IICS.

Log in into the VM using a public IP (if available) or private DNS from other VMs connected to the same network
and check for logs.

The Informatica Secure Agent didn't get added in the IICS account.
Check the following logs for details:

• C:\agent_setup.log (Windows OS)

• /home/agent_setup.log (Linux OS)

If these logs are not present, check the individual VM logs listed on the VM detail page.

Author
Informatica Marketplace R&D Team

12