How to Remote Upload File to Amazon Cloud Drive

Arc simplifies the process of uploading and downloading from secure deject storage platforms similar Amazon S3, Google Drive, OneDrive, Box, Dropbox, and more. This article serves as a guide for configuring automatic uploads and downloads from the deject with Arc.

• Create a Connector
• Establish a Connection
  • OAuth Authentication
• Configure Remote Folders
• Configure Automation
• Next Steps

Create a Connector

Arc has dedicated connectors for many different cloud storage platforms. To brainstorm integrating with a particular platform, discover the appropriate connector in the toolbar on the left of the Flows page and elevate it into the flow sail to create an instance of the connector:

This guide will utilize Amazon S3 as an instance cloud storage platform, simply the same principles apply regardless of the specific cloud storage service you want to use.

This connector volition handle both uploading and/or downloading from the cloud, depending on how y'all configure it.

Establish a Connexion

The first step in configuring our new S3 Connector is to institute a working connection with the cloud storage service.

For almost connections, the only thing that needs to be configured to constitute a connection is a set up of credentials that grant access to a deject storage account.

For S3 specifically, these credentials come up in the form of an Admission Key and Undercover Key:

Some cloud storage connectors volition have a bluish Connect button, indicating that this cloud storage provider requires OAuth authentication. This process is described below.

OAuth Hallmark

This section can be skipped for cloud storage providers that do non utilize OAuth: S3, Azure Blob, and Wasabi.

Using OAuth authentication requires a bit of actress piece of work when establishing the initial connexion. Notwithstanding, this applies only to the first time you connect; all successive connections are authenticated behind-the-scenes with no user interaction required.

Outset, you lot need to generate two OAuth values: a Client ID and a Customer Surreptitious. These values are generated using the panel/portal/GUI for the service you are trying to admission; for instance, if yous want to connect to Google Drive, you'll need to generate these values within the Google developer's console.

In one case you have the Customer ID and Client Secret values, you can plug these into the connector settings in Arc:

Then, clicking the Connect button volition take you to a portal where you can enter user credentials directly in the deject storage platform yous want to access.

Later on authenticating in this portal, the connector is granted an access token (and a refresh token) that it tin use in future connection attempts; this manual process is but required once.

Configure Remote Folders

Each connector targets a specific folder on the cloud storage platform to upload files to and a specific folder to download files from.

Some deject storage platforms, such as S3, also have a 'bucket' concept that groups these folders together. Offset, configure the bucket that should contain the relevant files and folders (if necessary).

Configuring the remote folders is washed in the Upload and Download sections of the Settings tab. The Remote Path field in these sections should be set to the folder path (on the cloud service) where files should be uploaded to (if applicable) and downloaded from (if applicable).

Note: S3 uses a pseudo-folder system with file prefixes, and so this Remote Path field is called Prefix in the S3 Connector.

These connectors support boosted download options, like filtering files that are downloaded and caching file details to ensure files are not downloaded more than one time. You can ignore these options for our unproblematic automatic setup.

Configure Automation

With the current configuration steps, the connector is able to communicate with the cloud storage platform and knows where files should be uploaded or downloaded. Adjacent, you lot'll configure the Automation settings to define precisely how the data flows.

In the Automation tab, there are checkboxes for enabling Upload and Download automation separately. This is how you tell the connector whether its job is to pull files down, push files out, or both.

When Upload automation is enabled, the connector will upload files to the cloud, including any files routed to the connector via the blue menstruum arrows in Arc'southward Flows canvass as well as any files added to its Input/Send folder (either via the Input tab or by placing files directly in the folder via the filesystem).

When Download automation is enabled, the connector volition poll the configured binder in the cloud at a specified interval to observe files to download. Files that are plant and downloaded will exist placed in the Output/Receive folder for the connector. If the connector is connected to others via blue catamenia arrows, then these files will not remain in this Output/Receive binder only will instead be passed along to the next connector in the Flow.

If you're ever not certain where the Input/Send or Output/Receive folders are on the filesystem, y'all tin cheque the Input and Output tabs of the connector, which have these filepaths at the acme of the tab panel.

Next Steps

If you haven't already, you lot tin can get started with Arc for free by downloading the awarding here. Arc comes with a free, fully-functional 30-day trial license, so you can confirm for yourself that the FTP and SFTP automation is as simple equally described in this commodity.

Hither in the cognition base, you tin can likewise find articles on Getting ArcESB Up and Running, Hosting Your Own FTP and SFTP Server, and more.

If you demand assistance working on your custom Arc solution, delight don't hesitate to reach out to our technical team at support@arcesb.com.

housesurrive91.blogspot.com

Source: https://www.arcesb.com/kb/articles/uploading-downloading-cloud.rst

Share this post