Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Runtime environments
  3. Hosted Agent
  4. Secure Agent groups
  5. Elastic runtime environments
  6. Serverless runtime environments
  7. Secure Agents
  8. Secure Agent installation

Runtime Environments

Runtime Environments

Step 4. Create a system disk

Step 4. Create a system disk

Create a system disk to improve mapping performance in
Data Integration
.
You can create a system disk using Amazon EFS or an NFS. File system connections in Amazon EFS use TLS by default. File system connections in NFS use NFSv4.
When you use a system disk, the serverless runtime environment creates the following directory on the system disk to store job metadata and logs:
<organization ID>/<serverless runtime environment ID>

Creating a system disk on Amazon EFS

To create a system disk on Amazon EFS, use the following guidelines:
  • Create any folder required by an access point before creating the access point itself. For example, if the access point refers to the folder
    /my-company/dev
    , then define this folder first before you set up the access point.
  • Configure connectivity between the subnet in the serverless runtime environment and the EFS file system.
  • Configure the EFS security group to allow inbound access from the security group of the serverless runtime environment.
  • Create an IAM role with full access to the EFS file system.
    For example, the following file system policy allows root access to the serverless role for file system fs-12345 and allows SecureTransport only:
    "Version": "2012-10-17", "Id": "efs-policy-wizard-<EFS policy wizard ID>", "Statement": [ { "Sid": "efs-statement-<EFS statement ID>", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::<ARN ID>:role/<serverless role>" }, "Action": [ "elasticfilesystem:ClientWrite", "elasticfilesystem:ClientMount", "elasticfilesystem:ClientRootAccess" ], "Resource": "arn:aws:elasticfilesystem:us-west-2:<ARN ID>:file-system/fs-12345", "Condition": { "Bool": { "elasticfilesystem:AccessedViaMountTarget": "true" } } }, { "Sid": "efs-statement-<EFS statement ID>", "Effect": "Deny", "Principal": { "AWS": "*" }, "Action": "*", "Resource": "arn:aws:elasticfilesystem:us-west-2:123456789:file-system/fs-12345", "Condition": { "Bool": { "aws:SecureTransport": "false" } } } ] }
    The following table describes the actions in the policy:
    Action
    Description
    elasticfilesystem:ClientMount
    Provides read-only access to a file system.
    elasticfilesystem:ClientWrite
    Provides write permissions on a file system.
    elasticfilesystem:ClientRootAccess
    Provides use of the root user when accessing a file system.
  • Configure the IAM role to restrict access to specific access points on the file system. For more information, see the AWS documentation.

Creating a system disk using an NFS

To create a system disk using an NFS, use the following guidelines:
  • Set the file system to the DNS of the NFS server.
  • Configure connectivity between the subnet in the serverless runtime environment and the NFS file server.
  • Configure the NFS security group to allow inbound access from the security group of the serverless runtime environment.

0 COMMENTS

We’d like to hear from you!