Create a new serverless runtime environment and configure properties on the Serverless Environments page. To view properties for a serverless runtime environment, expand the Actions menu for the environment and select View.
The following image shows the Serverless Environments page:
1Option to create a new serverless runtime environment
2Refresh icon
3Actions menu
Basic configuration
The following table describes the basic properties that you configure for the serverless runtime environment:
Property
Description
Name
Name of the serverless runtime environment.
Description
Description of the serverless runtime environment.
Task Type
Type of tasks that run in the serverless runtime environment.
- Select Data Integration to run tasks that are created using Data Integration.
- Select Data Integration Elastic to run tasks that are created using Data Integration Elastic.
Cloud Platform
Cloud platform to host the serverless runtime environment.
You can use only Amazon Web Services (AWS).
Max Compute Units
Maximum number of serverless compute units corresponding to machine resources that a task can use.
Task Timeout
Amount of time in minutes to wait for a task to complete before it is terminated. The timeout ensures that serverless compute units are not unproductive when a task hangs.
By default, the timeout is 2880 minutes (48 hours). You can set the timeout to a value that is less than 2880 minutes.
Cloud Data Integration configuration
The following table describes the properties that you use to create an IAM role for the serverless runtime environment:
Property
Description
Informatica Account Number
Informatica's account number on the cloud platform where the serverless runtime environment will be created. The account number is populated automatically.
External ID
External ID to associate with the role that you create for the serverless runtime environment. You can use the generated external ID or specify your own external ID.
AWS resource configuration
The AWS resource configuration specifies how the serverless runtime environment connects to your AWS account and the sources and targets that you use in mappings.
The following table describes the properties:
Property
Description
Configuration Name
Name of the AWS resource configuration.
Configuration Description
Description of the AWS resource configuration.
Account Number
Your account number on the cloud platform.
Region
Region on your cloud platform. The sources and targets that you use in mappings must either reside or be accessible from the region.
AZ ID
Identifier for the availability zone. The sources and targets that you use in mappings must either reside or be accessible from the availability zone.
VPC ID
ID of the Amazon Virtual Private Cloud (VPC). The VPC must be configured with an endpoint to access the sources and targets that you use in mappings.
For example, vpc-2f09a348.
Subnet ID
ID of the subnet within the VPC. The subnet must be have an entry point to access the sources and targets that you use in mappings.
For example, subnet-b46032ec.
Security Group ID
ID of the security group that the serverless runtime environment will attach to the ENI. The security group allows access to the sources and targets that you use in tasks.
For example, sg-e1fb8c9a.
Role Name
Name of the IAM role that the serverless runtime environment can assume on your AWS account.
The role must have permissions to create, read, delete, list, detach, and attach an ENI. It also requires read and write permissions on supplementary file location.
Use the Informatica account number and the external ID when you create a policy for the role.
AWS Tags
AWS tags to label the ENI that is created in your AWS account.
Each tag must be a key-value pair in the format: Key=string,Value=string where Key and Value are case-sensitive. Use a space to separate tags.
Note: Follow the rules and guidelines for tagging that AWS specifies. For more information, refer to the AWS documentation.
Supplementary File Location
Location on Amazon S3 to store supplementary files, such as JAR files and external libraries for certain transformations and connectors.
For example, if you use third-party or custom Java packages in the Java transformation, add the JAR files to an S3 location and specify the S3 location for the serverless runtime environment.
Use the format: s3://<bucket name>/<folder name>.
Serverless runtime validation
The validation process validates the AWS resource configuration properties and some network settings on the serverless runtime environment when you perform specific tasks.
The validation process connects to your AWS account using the IAM role to verify and list the resource properties, such as the subnet ID, availability zone ID, and role name. The IAM role establishes trust between your AWS account and the Informatica AWS account so that the serverless runtime environment can create an ENI and securely connect to data sources in your cloud environment. The IAM role must have permission to view the resource. For more information about setting up the IAM role, see Step 3. Set up an IAM role.
The following role permissions are required for validation:
•ec2:DescribeRegions
•ec2:DescribeAvailabilityZones
•ec2:DescribeVpcs
•ec2:DescribeSubnets
•ec2:DescribeSecurityGroups
If validation fails for any resource, the serverless runtime environment fails to start. You can download the detailed validation messages using the download option on the Serverless Environments page or the specific serverless runtime environment configuration page. Validation results and messages are available for failed environments only.
In addition to the serverless runtime environment properties, the validation process also checks for the number of IP addresses available on the subnet. The serverless runtime environment creation fails if there are insufficient IP addresses available on the subnet.
Note: The validation process does not validate the Amazon Virtual Private Cloud (VPC) ID if the subnet ID does not exist in your Amazon account.
Serverless runtime environment properties and network settings are validated when you perform the following tasks on a serverless runtime environment:
•Create a new serverless runtime environment.
•Edit a failed serverless runtime environment and save the updates.
•Clone a serverless runtime environment and save the configurations.
•Redeploy a failed serverless runtime environment.
Editing a serverless runtime environment
You can edit properties in a serverless runtime environment based on the environment status:
•Up and Running. You can update the maximum number of serverless compute units or the task timeout.
If you edit the maximum number of serverless compute units or the task timeout, the updated values take effect for subsequent task runs.
•Failed. You can update any of the properties. Redeploy the serverless runtime environment for the properties to take effect.
If the serverless runtime environment has a different status, you must delete the serverless runtime environment and create a new one to edit the properties.
Before you delete a serverless runtime environment, complete the following tasks:
•Use Monitor to make sure that the environment is not running any jobs.
•Remove the serverless runtime environment from any connections and tasks that use it.
Redeploying a serverless runtime environment
You might redeploy the serverless runtime environment in the following situations:
•You change your licenses.
•The serverless runtime environment shut down because the organization ran out of serverless compute units. You can add more compute units to your organization and redeploy the serverless runtime environment.
•You update the configuration in your cloud environment. For example, you update the JAR files in the supplementary file location, or you update the policy that is attached to the IAM role.
Before you redeploy a serverless runtime environment, use Monitor to make sure that the environment is not running any jobs. Then, in Administrator, expand the Actions menu for the serverless runtime environment and click Redeploy.
Cloning a serverless runtime environment
You might clone a serverless runtime environment to create another environment that has a similar configuration. For example, you might want to create a similar serverless runtime environment that connects to a different subnet in your cloud environment or uses a different security group.
To clone a serverless runtime environment, you can expand the Actions menu for the serverless runtime environment and click Clone.
Rules and guidelines
Consider the following rules and guidelines when you create a serverless runtime environment:
•You can create a maximum of 10 serverless runtime environments in your organization. If you have a trial license, you can create a maximum of two environments.
•A serverless runtime environment can run a maximum of 10 tasks at the same time.
•It takes at least five minutes for the serverless runtime environment to become available. Use the Serverless Environments page to track the status of the environment and review any status messages.
•You can not access the Driver and Agent Job logs and Advanced log after you delete a serverless runtime environment.
