Generic S3 Connector

Options

Settings

Endpoint

http(s) URL of the S3-compatible service endpoint.

Authentication

The authentication to use:

• Anonymous: Use anonymous credentials to make anonymous requests to the S3-compatible endpoint.
• Access Key ID and Secret Access Key: Use an access key ID and secret to authenticate. Check Use credentials to select a credentials flow variable to supply the ID and secret.
• Default Credential Provider Chain: Supply credentials using environment variables or a credentials configuration file. For further details see the S3 documentation.

Working directory

Specifies the working directory using the path syntax explained above. The working directory must be specified as an absolute path. A working directory allows downstream nodes to access files/folders using relative paths, i.e. paths that do not have a leading slash. If not specified, the default working directory is "/".

Normalize paths

Determines if the path normalization should be applied. Path normalization eliminates redundant components of a path like, e.g. /a/../b/./c" can be normalized to "/b/c". When these redundant components like "../" or "." are part of an existing object, then normalization must be deactivated in order to access them properly.

Advanced

Use path-style requests

If chosen, buckets will be accessed by appending their name to the path of the endpoint URL. Otherwise, they will be accessed by prepending their name as a subdomain in the URL hostname. The correct choice depends on how your S3-compatible endpoint is set up, but in most cases you will want to use path-style requests. For further explanation see the S3 documentation.

Region

Optional region to set on the client. Might be empty, depending on how your S3-compatible endpoint is set up.

Connection timeout in seconds

The amount of time to wait when initially establishing a connection before giving up and timing out. For further details see the S3 documentation.

Read/write timeout in seconds

The socket read/write timeout. For further details see the S3 documentation.

Server-side encryption (SSE)

If selected, all data written to the endpoint will be encrypted with Server-side encryption (SSE) using SSE-S3, SSE-KMS or SSE-C.

Use default managed key

If SSE-KMS is selected as the SSE method, then this option specifies whether or not to encrypt data with the default managed CMK.

KMS key id

If SSE-KMS is selected as the SSE method and the default managed CMK should not be used, then this option allows to choose the KMS key with which to encrypt data written to the endpoint. Click on List keys to fetch the list of available keys (requires permissions kms:ListKeys, kms:DescribeKey and optionally kms:ListAliases).

Customer key

If SSE-C is selected as the SSE method it is necessary to provide an encryption key. There are multiple ways the key could be provided. The base64 encoded key could be entered directly or provided via credentials variable using the encoded key as password (username can be anything or left empty). The third way is to select a file that contains exactly 32 bytes (256 bit) that should be used as key.

Views

This node has no views

Workflows

• EC2_connectionKNIME Hub
• EC2_connectionKNIME Hub

Links

• No links available

Developers