Skip to Content

Amazon S3 connector for Jitterbit Integration Studio

Summary

The Amazon S3 connector establishes access to Amazon S3.

The Amazon S3 connector provides an interface for creating an Amazon S3 connection, the foundation used for generating instances of Amazon S3 activities. These activities, once configured, interact with Amazon S3 through the connection.

The Amazon S3 connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure an Amazon S3 connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Amazon S3 connection and its activities are referred to as an Amazon S3 endpoint:

Amazon S3 activity types

  • Move Object: Moves an object from one Amazon S3 bucket to another and is intended to be used as a target in an operation.

  • Delete Object: Deletes an object from an Amazon S3 bucket and is intended to be used as a target in an operation.

  • Put Object: Places an object into an Amazon S3 bucket and is intended to be used as a target in an operation.

  • Get Object: Retrieves an object from an Amazon S3 bucket and is intended to be used as a source in an operation.

  • List Objects: Returns some or all (up to 100,000) of the objects in an Amazon S3 bucket and is intended to be used as a target in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

The Amazon S3 connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

To use the Amazon S3 connector's activities, the Amazon S3 instance must have certain permissions set. All of the connector's activities require the s3:ListAllMyBuckets permission. In addition, individual activities require additional specific permissions. The following table summarizes the necessary permissions:

Permission needed Functionality
s3:ListAllMyBuckets Testing the connection and retrieving activity metadata during activity configuration
s3:PutObject and s3:GetBucketLocation Put Object activity execution
s3:GetObject, s3:GetObjectTagging, and s3:ListBucket Get Object activity execution
s3:GetObject, s3:GetObjectTagging, and s3:ListBucket List Objects activity execution
s3:DeleteObject Delete Object activity execution
s3:GetObject and s3:PutObject Move Object activity execution

The Amazon S3 connector uses the AWS SDK for Java version 2.29.34. Refer to the API documentation for information on the schema nodes and fields.

Known issue

Amazon S3 operations are failing

  • Summary: Some existing operations using the Amazon S3 connector that were previously working have begun to fail around the timeframe of the 11.38 release.

  • Resolution: If you experience this issue, add the permission s3:GetObjectTagging to your AWS IAM policy to resolve this issue.

Troubleshooting

If you experience issues with the Amazon S3 connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.amazon" level="DEBUG"/>

  5. If using private agents, you can check the agent logs for more information.

  6. For additional troubleshooting considerations, see Operation troubleshooting.

Known issue

Amazon S3 operations are failing

  • Summary: Some existing operations using the Amazon S3 connector that were previously working have begun to fail around the timeframe of the 11.38 release.

  • Resolution: If you experience this issue, add the permission s3:GetObjectTagging to your AWS IAM policy to resolve this issue.