Amazon S3 Connector Example

The AmazonS3 Connector allows you to access the Amazon Simple Storage Service (Amazon S3) via the AWS SDK.

What you'll build

This example depicts how to use AmazonS3 connector to:

  1. Create a S3 bucket (a location for storing your data) in Amazon cloud.
  2. Upload a message into the created bucket as a text file.
  3. Retrieve created text file back and convert into a message in the integration runtime.

All three operations are exposed via an API. The API with the context /s3connector has three resources:

  • /createbucket - Once invoked, it will create a bucket in Amazon with the specified name
  • /addobject - The incoming message will be stored into the specified bucket with the specified name
  • /info - Once invoked, it will read the specified file from the specified bucket and respond with the content of the file

Following diagram shows the overall solution. The user creates a bucket, stores some message into the bucket, and then receives it back.

To invoke each operation, the user uses the same API.

Amazon S3 use case

If you do not want to configure this yourself, you can simply get the project and run it.

Setting up the environment

Please follow the steps mentioned at Setting up Amazon S3 document in order to create a Amazon S3 account and obtain credentials you need to access the Amazon APIs. Keep them saved to be used in the next steps.

Configure the connector in WSO2 Integration Studio

Follow these steps to set up the Integration Project and import AmazonS3 connector into it.

  1. Open WSO2 Integration Studio and create an Integration Project. Creating a new Integration Project

  2. Right-click the project that you created and click on Add or Remove Connector -> Add Connector. You will get directed to the WSO2 Connector Store.

  3. Search for the specific connector required for your integration scenario and download it to the workspace. Search Connector in the Connector Store

  4. Click Finish, and your Integration Project is ready. The downloaded connector is displayed on the side palette with its operations.

  5. You can drag and drop the operations to the design canvas and build your integration logic. Drag connector operations

  6. Right click on the created Integration Project and select New -> Rest API to create the REST API.

  7. Right click on the created Integration Project and select, -> New -> Rest API to create the REST API. Adding a Rest API

  8. Specify the API name as S3ConnectorTestAPI and API context as /s3connector. You can go to the source view of the XML configuration file of the API and copy the following configuration.

<?xml version="1.0" encoding="UTF-8"?>
<api context="/s3connector" name="S3ConnectorTestAPI" xmlns="">
    <resource methods="PUT" uri-template="/createbucket">
            <log description="identifier log" level="custom">
                <property name="message" value="Create bucket if not exists"/>
            <propertyGroup description="message inputs">
                <property expression="//bucketName" name="bucketName" scope="default" type="STRING"/>
                <property expression="//bucketRegion" name="bucketRegion" scope="default" type="STRING"/>
    <resource methods="POST PUT" uri-template="/addobject">
            <log description="identifier log" level="custom">
                <property name="message" value="Store into S3 bucket"/>
            <propertyGroup description="message properties">
                <property expression="//bucketName/text()" name="bucketName" scope="default" type="STRING"/>
                <property expression="//objectKey" name="objectKey" scope="default" type="STRING"/>
                <property name="filePath" value="/Users/mine/Desktop/S3_img.jpg" scope="default" type="STRING"/>
            <propertyGroup description="init properties">
                <property name="awsAccessKeyId" scope="default" type="STRING" value="AKIXXXXXXXXXXA"/>
                <property name="awsSecretAccessKey" scope="default" type="STRING" value="qHZXXXXXXQc4oMQMnAOj+340XXxO2s"/>
                <property name="region" scope="default" type="STRING" value="us-east-2"/>
                <property name="connectionName" scope="default" type="STRING" value="amazons3"/>
            <!-- initialize multiPart upload -->
            <!-- We need to interpret the response as application/xml-->
            <property name="ContentType" scope="axis2" type="STRING" value="application/xml"/>
            <log level="full"/>
            <!-- Extract generated uploadId -->
            <property expression="//UploadId/text()" name="uploadId" scope="default" type="STRING"/>
            <log level="custom">
                <property expression="$ctx:uploadId" name="Upload Id"/>
            <!-- Execute multiPart upload -->
            <property name="partNumber" scope="default" type="STRING" value="1"/>
            <property expression="//ETag/text()" name="eTag" scope="default" type="STRING"/>
            <log level="custom">
                <property expression="$ctx:eTag" name="e Tag"/>
            <payloadFactory media-type="xml">
                    <CompletedPartDetails xmlns="">
                    <arg evaluator="xml" expression="$ctx:eTag"/>
            <!--complete multiPart upload-->
    <resource methods="POST" uri-template="/info">
            <log description="identifier log" level="custom">
                <property name="message" value="getting information from amazon S3"/>
            <property expression="//bucketName/text()" name="bucketName" scope="default" type="STRING"/>
            <property expression="//objectKey/text()" name="objectKey" scope="default" type="STRING"/>


  • As awsAccessKeyId use the access key obtained from Amazon S3 setup and update the above API configuration.
  • As awsSecretAccessKey use the secret key obtained from Amazon S3 setup and update the above API configuration.
  • Note that When you configure the addobject resource, there are three parts to it. You need to use three operations of the connector in order.
    • initMultipartUpload - initialize the upload to the bucket. In the response of this operation you will receive generated uploadId by amazon S3
    • uploadPart - upload message part. There can be multiple parts to the same object. When you invoke the operation, feed uploadId and the correct partNumber.
    • completeMultipartUpload - once all parts are done uploading, call this operation. It will add up all the parts and create the object in the requested bucket.
  • Note that region, connectionName and credentials are hard coded. Please change them as per the requirement.
  • For more information please refer the reference guide for Amazon S3 connector.

Now we can export the imported connector and the API into a single CAR application. CAR application is the one we are going to deploy to server runtime.

Exporting Integration Logic as a CApp

CApp (Carbon Application) is the deployable artifact on the integration runtime. Let us see how we can export integration logic we developed into a CApp along with the connector.

Creating Connector Exporter Project

To bundle a Connector into a CApp, a Connector Exporter Project is required.

  1. Navigate to File -> New -> Other -> WSO2 -> Extensions -> Project Types -> Connector Exporter Project.
    Add Connector Exporter Project

  2. Enter a name for the Connector Exporter Project.

  3. In the next screen select, Specify the parent from workspace and select the specific Integration Project you created from the dropdown. Naming Connector Exporter Project

  4. Now you need to add the Connector to Connector Exporter Project that you just created. Right-click the Connector Exporter Project and select, New -> Add Remove Connectors -> Add Connector -> Add from Workspace -> Connector

  5. Once you are directed to the workspace, it displays all the connectors that exist in the workspace. You can select the relevant connector and click Ok. Selecting Connector from Workspace

Creating a Composite Application Project

To export the Integration Project as a CApp, a Composite Application Project needs to be created. Usually, when an Integration project is created, this project can be created as part of that project by Integration Studio. If not, you can specifically create it by navigating to File -> New -> Other -> WSO2 -> Distribution -> Composite Application Project.

Exporting the Composite Application Project

  1. Right-click the Composite Application Project and click Export Composite Application Project. Export as a Carbon Application

  2. Select an Export Destination where you want to save the .car file.

  3. In the next Create a deployable CAR file screen, select both the created Integration Project and the Connector Exporter Project to save and click Finish. The CApp is created at the specified location provided at the previous step. Create a deployable CAR file

Now the exported CApp can be deployed in the integration runtime so that we can run it and test.

Get the project

You can download the ZIP file and extract the contents to get the project code.

Download ZIP


You may need to update the value of the access key and make other such changes before deploying and running this project.


Follow these steps to deploy the exported CApp in the integration runtime.

Deploying on Micro Integrator

You can copy the composite application to the <PRODUCT-HOME>/repository/deployment/server/carbonapps folder and start the server. Micro Integrator will be started and the composite application will be deployed.

You can further refer the application deployed through the CLI tool. See the instructions on managing integrations from the CLI.

Click here for instructions on deploying on WSO2 Enterprise Integrator 6
  1. You can copy the composite application to the <PRODUCT-HOME>/repository/deployment/server/carbonapps folder and start the server.

  2. WSO2 EI server starts and you can login to the Management Console https://localhost:9443/carbon/ URL. Provide login credentials. The default credentials will be admin/admin.

  3. You can see that the API is deployed under the API section.


We can use Curl or Postman to try the API. The testing steps are provided for curl. Steps for Postman should be straightforward and can be derived from the curl requests.

Creating a bucket in Amazon S3

  1. Create a file called data.xml with the following content. Note that the bucket region is us-east-2. If you need to create the bucket in a different region, modify the hard coded region of the API configuration accordingly.
  2. Invoke the API as shown below using the curl command. Curl Application can be downloaded from here.

    curl -H "Content-Type: application/xml" --request PUT --data @data.xml
    Expected Response:

    You should receive 200OK response. Please navigate to Amazon AWS S3 console[] and see if a bucket called wso2engineers is created. If you tried to create a bucket with a name that already exists, it will reply back with a message indicating the conflict.

    Creating Amazon S3 bucket

Post a message into Amazon S3 bucket

  1. Create a file called data.xml with the following source file path (/Users/mine/Desktop/Julian.txt).
  2. Invoke the API as shown below using the curl command. Curl Application can be downloaded from here.
    curl -H "Content-Type: application/xml" --request POST --data @data.xml
    Expected Response: You will receive a response like below containing the details of the object created.
    <?xml version="1.0" encoding="UTF-8"?>
    <CompleteMultipartUploadResult xmlns="">
    Navigate to AWS S3 console and click on the bucket wso2engineers. You will note that a file has been created with the name Julian.txt. Upload object to Amazon S3 bucket

Read objects from Amazon S3 bucket

Now let us read the information on wso2engineers that we stored in the Amazon S3 bucket.

  1. Create a file called data.xml with the following content. It specifies which bucket to read from and what the filename is. This example assumes that the object is stored at root level inside the bucket. You can also read a object stored in a folder inside the bucket.
  2. Invoke the API as shown below using the curl command.

    curl -H "Content-Type: application/xml" --request POST --data @data.xml
    Expected Response: You receive a response similar to the following. The Content element contains the contents of the file requested.


    The Content element is available only with Amazon S3 connector v2.0.1 and above.

            <Content>Julian Garfield, Software Engineer, Integration Group</Content>
            <ContentType>text/plain; charset=utf-8</ContentType>

In this example Amazon S3 connector is used to perform operations with Amazon S3 storage. You can receive details of the errors that occur when invoking S3 operations using the S3 responses itself. Please read the Amazon S3 connector reference guide to learn more about the operations you can perform with the Amazon S3 connector.