Amazon S3 trading partner |
Top Previous Next |
This trading partner exchanges data with an Amazon S3 Bucket. The MFT Server initiates the connection to the remote Amazon S3 Bucket. It is assumed that the administrator of the Amazon account has configured an S3 Bucket, and has provided you with the details needed to set up the trading partner.
Adding the Amazon S3 trading partner
In the desired domain, navigate to the AUTOMATION > Trading Partners module. Click on the Add button, or right click anywhere in the grid area and select Add from the pop-up menu. In the Add Trading Partner dialog window, select Amazon S3 as the Protocol, then click OK. The Add "Amazon S3" Trading Partner dialog will appear as depicted in the figure below.
Figure 462
Basic
Name - The unique name to assign to this trading partner. Enter a name that best describes the trading partner, as you will be selecting the name when using the partner in MFT Server features that support it.
Company - The name of the company that this trading partner represents.
E-mail - The primary email address for this trading partner.
Connection
Timeout - The timeout (in seconds) for establishing a connection to the remote service.
Proxy
This section is for MFT Server customers who have configured a proxy server that the trading partner connection is required to go through.
Proxy Type - The type of proxy service - either None or HTTP. If HTTP is selected, the following fields can be set:
Authentication
Use Credentials - If selected, enter the Username/Access key and Password/Secret key fields, which will be used to authenticate access to the Amazon S3 Bucket. These details would need to be provided to you by the administrator of the Amazon S3 Bucket. As a tip, this information can be generated by the S3 Bucket administrator using Amazon's IAM (Identity and Access Management) console. Using the console, navigate to the Access management heading, click on Users, then select the desired user. Next, click on the Security credentials tab and select the Create access key button. The key and password generated should be used in the fields below.
Use encryption - If checked, enables encryption for this trading partner connection.
Region - Select the Amazon region that the S3 Bucket belongs to.
Requester pays - If checked, configure an Amazon S3 bucket to be a Requester Pays bucket, meaning the requester pays the cost of the request and data download instead of the bucket owner.
Tags
Tags - If specified, this is the one or more tags that are used to limit which administrators have access to the network.
Example using the Amazon S3 Bucket trading partner in a trigger action
Triggers are created on the domain-level in AUTOMATION > Triggers. Triggers listen for events (e.g., a file upload) and respond with actions. There are many trading partner-specific trigger actions. This example does not provide all the steps when creating a trigger; it describes how a trigger action would be configured using the Amazon S3 Bucket trading partner. For a complete discussion about triggers, click here.
Assume, when a trigger event occurs, you would like a file to be automatically uploaded from the MFT Server to the Amazon S3 Bucket trading partner.
To accomplish this, you would need to add an action to the trigger, in the Trigger Actions area. The action to add is Trading Partner File Upload as depicted in figure 466 below.
Figure 466
Partner - This is the Amazon S3 Bucket trading partner name. A list of existing trading partners will appear in the dropdown list for you to choose from.
Local File - This is the local file on the MFT Server to upload to the Amazon S3 Bucket trading partner.
Remote Directory - This is the Amazon S3 Bucket name that identifies where to upload the file to. This is an existing bucket configured by the administrator of the Amazon S3 Bucket. It could consist of just the bucket name, or the bucket name followed by one or more folder names, as depicted in the above figure (mfttestbucket/FolderA),
Using the Amazon Console UI, the figure below depicts the results of the above Trading Partner File Upload action example, after the trigger runs.
Figure 467
|