Table of Contents

Search

  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Licenses
  5. Ecosystem single sign-on
  6. SAML single sign-on
  7. Source control and service upgrade settings
  8. Users and user groups
  9. User roles
  10. Permissions
  11. Runtime environments
  12. Serverless runtime environments
  13. Secure Agent services
  14. Secure Agent installation
  15. Schedules
  16. Bundle management
  17. Event monitoring
  18. File transfer
  19. Troubleshooting

Administrator

Administrator

Serverless runtime environment properties

Serverless runtime environment properties

Configure properties for a new serverless runtime environment 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:
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.

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.
Mapping Type
Mapping type to process using the serverless runtime environment.
Select Hybrid to process data in mappings.
Select Elastic to process data in
elastic mappings
.
Cloud Platform
Cloud platform to host the serverless runtime environment.
You can use only Amazon Web Services (AWS).

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.
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
.
Make sure that the subnet uses a NAT gateway.
Security Group ID
ID of the security group that allows access to the sources and targets that you use in mappings.
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 the S3 location that stores supplementary files.
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
. Use a space to separate tags.
S3 Location for JAR Files
Location on Amazon S3 that stores supplementary files, such as JAR files and external libraries for use with 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>
.


Updated August 03, 2020