FME Flow: 2024.1

Creating and Managing Resource Connections

You can create and manage your own connections to network resources and Amazon Web Services (AWS) S3 buckets. When you create these connections, they appear on the Resources page.

Note  AWS S3 buckets cannot be accessed from workspaces run from FME Flow, unless that access is through an S3-related transformer, such as S3Uploader, S3Downloader, S3Deleter, or S3ObjectLister. For more information, see the FME Workbench Transformers help.

To Create a Resource Connection

  1. Choose one of the following:
    • Click Create: Creates a new connection from scratch.
    • Check an existing connection and click Duplicate: Creates a new connection from the settings of an existing connection.
  2. On the Create New Resource Connection page, complete or edit the fields as needed. When finished, click OK.
    • Name: Specify the system name for the connection, which is generated based on your Display Name. The name must be unique among your connections, and cannot contain spaces or certain other special characters. This name cannot be changed after saving.
    • Display Name: Specify how you want the name of the connection to display in the Web User Interface.
    • Type:
      • Amazon S3 bucket:
        • bucket name: The Amazon S3 bucket name.
        • Folder: (Optional) Path to the folder within the Amazon S3 bucket. For example, /folder1 or /folder1/folder2. If blank, a connection is established at the bucket's root.
        • Access key and Secret key: The security credentials for your Amazon Web Services account. This account must have full privileges to access the specified Bucket. For more information, see AWS Security Credentials.
      • Network based resource:
        • Directory: Enter the UNC path to a file-based resource on the network.
        • Warning  We advise against specifying a root directory (that is, an entire drive) as a network resource. Doing so may cause the following when performed from FME Flow:
          • Slow performance when browsing the network resource.
          • Errors when writing to the network resource, due to security constraints.