Table of Contents

Search

  1. Preface
  2. Runtime environments
  3. Hosted Agent
  4. Secure Agent groups
  5. Secure Agents
  6. Secure Agent installation in a cloud environment
  7. Secure Agent installation in a local environment
  8. Serverless runtime environment setup in AWS
  9. Serverless runtime environments

Runtime Environments

Runtime Environments

Creating a new VPC using the AWS CloudFormation template

Creating a new VPC using the AWS CloudFormation template

When you use the AWS CloudFormation template to create a new VPC, the stack creates a VPC and all required resources and configurations to connect to the serverless runtime environment in Informatica's VPC, including subnets and an IAM role with minimal policies.
To create the stack in AWS CloudFormation, specify the stack name and configure stack parameters.
The following table describes the stack parameters:
Parameter
Description
VPC CIDR
CIDR block that specifies where to create the VPC.
Public Subnet CIDR
CIDR block that specifies where to create the public subnet. The IP range of the public subnet must be within the IP range of the VPC.
Availability Zone for Public Subnet
Availability zone where you want to create the public subnet. You can select any availability zone in the current region.
Private Subnet CIDR
CIDR block that specifies where to create the private subnet. The IP range of the private subnet must be within the IP range of the VPC.
Availability Zone for Private Subnet
Availability zone where you want to create the private subnet. You can select any availability zone in the current region.
VPC Deployment Type
Select the NAT Gateway.
Informatica Cloud Region
Region where the Informatica POD resides.
You can identify the region through the URL that appears when you open any service in Informatica Intelligent Cloud Services. For example, if the URL starts with
usw3.dm-us.informaticacloud.com
, the POD resides in the US region.
External ID
External ID to associate with the IAM role.
AWS Tags
AWS tags to label the ENI.
Supplementary File Location
Location on Amazon S3 to store supplementary files, such as JAR files and external libraries that developers can use to access and process data.
S3 Location for JSON File
Location on Amazon S3 to generate the serverless configuration file.
The stack is not created if the parameters are not valid.

0 COMMENTS

We’d like to hear from you!