Runtime Environments > Serverless runtime environments > Creating a serverless runtime environment in AWS
  

Creating a serverless runtime environment in AWS

Create a serverless runtime environment and configure properties on the Serverless Environments page. You can view properties for a serverless runtime environment by expanding the Actions menu for the environment and selecting View.
The following image shows the Serverless Environments page:
The Serverless Environments page shows all serverless runtime environments. For each serverless runtime environment, you can view the name, description, type, cloud platform, status, status message, updated time, created time, and an Actions menu.
  1. 1Option to create a serverless runtime environment
  2. 2Refresh icon
  3. 3Actions menu
To create a serverless runtime environment, you can enter the serverless runtime environment properties, or you can import a serverless configuration file to populate the properties. 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 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.

Serverless runtime environment properties

Configure properties for the serverless runtime environment. The basic properties define the serverless runtime environment. The platform configuration properties describe the AWS resources in your VPC that connect to the serverless runtime environment.

Basic Configuration

The Basic Configuration section of a serverless runtime environment contains general information about the environment, including its Informatica Account Number and its current status.
The following table describes the basic properties:
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 mappings outside of advanced mode.
  • - Select Advanced Data Integration to run mappings in advanced mode.
Cloud Platform
Cloud platform to host the serverless runtime environment.
You can use only Amazon Web Services (AWS).
Max Compute Units Per Task
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.
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.

Platform Configuration

The Platform Configuration section of a serverless runtime environment contains technical information about the platform, including the region, subnet, and security group.
The following table describes the platform properties:
Property
Description
Configuration Name
Name of the resource configuration.
Configuration Description
Description of the resource configuration.
The description can be up to 256 characters and can contain alphanumeric characters and the following special characters:
._-:/()#,@[]+=&;{}!$"*
Account Number
Your account number on the cloud platform.
Region
Region of your cloud environment. The sources and targets that you use in mappings should either reside in or be accessible from this 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.
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.
Use the format: s3://<bucket name>/<folder name>.
You must put script files in a folder named command_scripts. This folder can have subfolders. Informatica Intelligent Cloud Services synchronizes files at regular intervals within the command_scripts directory to the Secure Agent, specifically to the agent install directory apps/Common_Integration_Components/data/command/serverless/command_scripts. If you update files in Amazon S3, Informatica Intelligent Cloud Services automatically synchronizes them to the Secure Agent.

Runtime Configuration Properties

The Runtime Configuration Properties section of a serverless runtime environment determines how the environment behaves.
Note: Set the variables for the default directories, but don't change any other variables or properties unless directed by your system administrator or by Informatica Global Customer Support.
The following table lists the system variables that the serverless runtime environment uses for locations such as the source and target directories and temp files. Review the system defaults and update them as necessary.
Directory names can't contain these special characters: * ? < > " | ,
Tip: Filter the list to show "Service = Data_Integration_Server" and "Type = PMRDTM_CFG" to find the default directory variables more easily.
System Variable Name
Description
$PMLookupFileDir
Directory for lookup files.
Default is $PMRootDir
$PMBadFileDir
Directory for reject files.
Default is $PMRootDir/error
$PMCacheDir
Directory for index and data cache files.
Default is $PMRootDir/cache
$PMStorageDir
Directory for state of operation files. The Data Integration Service uses these files for recovery if you have the high availability option or if you enable a workflow for recovery. These files store the state of each workflow and session operation.
Default is $PMRootDir
$PMTargetFileDir
Directory for target files.
Default is $PMRootDir
$PMSourceFileDir
Directory for source files.
Default is $PMRootDir
$PMExtProcDir
Directory for external procedures.
Default is $PMRootDir
$PMTempDir
Directory for temporary files.
Default is $PMRootDir/temp

System Disk

Configuring a system disk can in the serverless runtime environment can improve mapping performance in Data Integration.
For rules and guidelines about configuring a system disk, see Configuring a system disk.
The following table describes the properties for a system disk:
Property
Description
Type
System disk type, either EFS or NFS.
File System
For EFS disks, the file system is the file system ID of the EFS disk.
For NFS disks, the file system is the DNS of the file system.
Source Mount
File system path to be mounted in the serverless runtime environment.
Access Point
The ID of the Amazon EFS file system access point.
The access point ensures isolation for tenants in a multi-tenant EFS file system.
Once an access point is set up, you can configure the file system policy to allow access only to the access point for the serverless IAM role.

Data Disk

Configuring a data disk in your serverless runtime environment allows you to access files in EFS or NFS directories.
For more information, see Using EFS or NFS directories as data disks and Configuring a data disk.
The following table describes the properties for a data disk:
Property
Description
Type
Data disk type, either EFS or NFS.
File System
For EFS disks, the file system is the file system ID of the EFS disk.
For NFS disks, the file system is the DNS of the file system.
Source Mount
File system path to be mounted in the serverless runtime environment.
Target Mount
File system to be mounted on the Secure Agent.
Access Point
The ID of the Amazon EFS file system access point.
The access point ensures isolation for tenants in a multi-tenant EFS file system.
Once an access point is set up, you can configure the file system policy to allow access only to the access point for the serverless IAM role.

Using a serverless configuration file

You can use a serverless configuration file to populate the serverless runtime environment properties.
Request the configuration file from your cloud administrator and import it in Administrator when you create a serverless runtime environment.

Requesting a serverless configuration file

Request the serverless configuration file from your cloud administrator.
    1On the Serverless Environments page, click New Serverless Runtime Environment.
    2Select Request a configuration file from your cloud administrator.
    The Configuration File Request dialog box appears.
    3Select the cloud region.
    The dialog box generates an email template.
    4Click Copy to Clipboard.
    5Using your preferred email service, use the template to compose an email and send it to your cloud administrator.
    The email contains URLs to the AWS CloudFormation templates that your cloud administrator can use to create a VPC or connect an existing VPC to a serverless runtime environment and generate the serverless configuration file. For more information, see Create a VPC using a template.

Importing a serverless configuration file

Import a serverless configuration file to populate serverless runtime environment properties.
    1On the Serverless Environments page, click New Serverless Runtime Environment.
    2Select Create a serverless runtime environment.
    3Enter the basic properties.
    4For the platform properties, click Import Configuration.
    The Import a Configuration File dialog box appears.
    5Click Choose File and navigate to the serverless configuration file on your local machine.
    6Click Import.

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 Create and configure your environment manually.
The following role permissions are required for validation:
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: