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

Connecting to an existing VPC using the AWS CloudFormation template

Connecting to an existing VPC using the AWS CloudFormation template

You specify a template in AWS CloudFormation, and then AWS CloudFormation creates a stack based on this template.
When you log in to AWS CloudFormation, you can create a new stack. When you create the stack, you specify a template to use. This template populates the stack parameters that you need to fill in. Once the parameters are complete, AWS CloudFormation creates the stack based on the parameter values.
The following table describes the stack parameters:
Parameter
Description
VPC ID
ID of the VPC. For example, vpc-2f09a348.
The stack assumes that the VPC is in the same AWS region where the stack is created.
Subnet ID
ID of the subnet within the VPC. For example, subnet-b46032ec.
Security Group ID
Optional. ID of the security group. For example, sg-e1fb8c9a.
Should Security Group be created if it does not exist?
Indicates whether the stack will create a security group if a security group doesn't exist. Select
Yes
or
No
.
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.
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 for certain transformations and connectors.
S3 Location for JSON File
Location on Amazon S3 to generate the serverless configuration file.
If the parameters are not valid, the stack fails to be created.

Configurations that the stack performs

The stack performs the following configurations:
  • Detects the region based on the VPC ID and checks if a serverless runtime environment can connect to the region.
  • Checks if the subnet exists.
  • Fetches the availability zone ID from the subnet ID.
  • Checks the inbound and outbound rules in the security group. If a security group is not provided or does not exist, the stack creates a security group.
  • Creates an IAM role and assigns the following policy to the role:
    { "Version":"2012-10-17", "Statement":[ { "Sid":"VisualEditor0", "Effect":"Allow", "Action":[ "ec2:DetachNetworkInterface", "ec2:DeleteTags", "ec2:DescribeTags", "ec2:CreateTags", "ec2:DeleteNetworkInterface", "ec2:DescribeSecurityGroups", "ec2:CreateNetworkInterface", "ec2:DeleteNetworkInterfacePermission", "ec2:DescribeNetworkInterfaces", "ec2:DescribeAvailabilityZones", "ec2:CreateNetworkInterfacePermission", "ec2:AttachNetworkInterface", "ec2:DescribeNetworkInterfacePermissions", "ec2:DescribeSubnets", "ec2:DescribeNetworkAcls" ], "Resource":"*" }, { "Sid":"VisualEditor1", "Effect":"Allow", "Action":[ "s3:PutObject", "s3:GetObject", "s3:ListBucket", "s3:DeleteObject", "s3:GetBucketAcl" ], "Resource":[ "arn:aws:s3:::<S3 location for supplementary files>", "arn:aws:s3:::<S3 location for supplementary files>/*" ] } ] }
  • Creates the following trust relationship in the IAM role:
    { "Version":"2012-10-17", "Statement":[ { "Effect":"Allow", "Principal":{ "AWS":"arn:aws:iam::<Informatica's account number>:root" }, "Action":"sts:AssumeRole", "Condition":{ "StringEquals":{ "sts:ExternalId":"<external ID>" } } } ] }

0 COMMENTS

We’d like to hear from you!