logo

WANDISCO FUSION®
PLUGIN FOR LIVE S3

1. Welcome

1.1. Product overview

Use the Fusion Plugin for Live S3 to replicate data among S3 buckets. Fusion Plugin for Live S3 provides continuous, active replication of live data across multiple buckets, which can span regions in AWS, or can be a mix of on-premise S3-compatible storage systems and cloud-hosted services. Applications can modify and access S3 data in any of these buckets while the Fusion Plugin for Live S3 ensures data are available across all of them.

1.2. Documentation guide

This guide contains the following:

Welcome

this chapter introduces this user guide and provides help with how to use it.

Release Notes

details the latest software release, covering new features, fixes and known issues to be aware of.

Concepts

explains how Fusion Plugin for Live S3 through WANdisco Fusion uses WANdisco’s Live Data platform.

Installation

covers the steps required to install and set up Fusion Plugin for Live S3 into a WANdisco Fusion deployment.

Operation

the steps required to run, reconfigure and troubleshoot Fusion Plugin for Live S3.

Developer

a guide for developers looking to develop and incorporate their own software for Fusion Plugin for Live S3.

Reference

additional Fusion Plugin for Live S3 documentation, including documentation for the available REST API.

1.2.1. Symbols in the documentation

In the guide we highlight types of information using the following call outs:

The alert symbol highlights important information.
The STOP symbol cautions you against doing something.
Tips are principles or practices that you’ll benefit from knowing or using.
The KB symbol shows where you can find more information, such as in our online Knowledgebase.

1.3. Contact support

See our online Knowledgebase which contains updates and more information.

If you need more help raise a case on our support website.

1.4. Give feedback

If you find an error or if you think some information needs improving, raise a case on our support website or email docs@wandisco.com.

2. Release Notes

2.1. Live S3 1.0

WANdisco is pleased to present the 1.0 release of the Fusion Plugin for Live S3, available now from the WANdisco file distribution site. This release provides full functionality for S3 replication in a Live Data environment, with consistent replication of S3 objects among multiple buckets, and features to perform consistency checks and to bring buckets to a consistent state for initial transfer of data.

2.1.1. Known Issues

Some S3 concepts do not map directly to an environment that replicates buckets e.g., bucket creation or deletion, and operations that act on objects by unique identifier provided by the S3 endpoint. There are also some aspects of the S3 API that are not yet supported e.g., browser-based object upload/creation.

  1. The Fusion Plugin for Live S3 does not offer support for bucket deletion with the DELETE bucket operation.

  2. The Fusion Plugin for Live S3 does not support the PUT Bucket operation to create a new bucket.

  3. Deletion of specific object versions is not supported because independent S3 buckets assign different version identifiers to replicated instances of an object.

  4. Deletion of tagging for a specific object version is not supported because independent buckets assign different version identifiers to replicated instances of an object.

  5. POST is an alternative to PUT for browser-based uploads. The Fusion Plugin for Live S3 does not support coordination and replication of objects created through this operation.

  6. POST Object restore allows restoration of a temporary copy of an archived object. It is not supported by the Fusion Plugin for Live S3.

  7. Multi-chunk payloads are not yet supported.

  8. Authentication via an IAM role is not yet supported.

  9. Buckets configured with MFA serial security are not yet supported.

  10. Large uploads may fail while using AWS Java SDK because of an excessively small BlockingQueue timeout value.

3. Concepts

3.1. Product concepts

Familiarity with the following concepts will improve your use of the Fusion Plugin for Live S3.

Virtual Bucket

A virtual bucket is a bucket accessible through the Fusion Plugin for Live S3 that retains and shares data across multiple underlying buckets. Access your data with automatic, continuous and consistent replication using the Fusion Plugin for Live S3. Applications use the virtual bucket when interacting with S3 via the Fusion Plugin for Live S3.

S3 Proxy

Applications use the Fusion Plugin for Live S3 via one or more S3-compatible endpoints that it provides in the S3 proxy, which is the runtime component that proxies access to underlying S3-compatible storage services on behalf of the Fusion Plugin for Live S3.

WANdisco Fusion Plugin

The Fusion Plugin for Live S3 extends the WANdisco Fusion server to support the operation of the S3 proxy. Coordinate activities among multiple S3 proxy instances with the WANdisco Fusion Plugin that is installed for each WANdisco Fusion server.

3.2. S3 Plugin Architecture

Fusion Plugin for Live S3 provides a "Live Data" architecture, where data are stored and used in multiple locations, while data are replicated with guaranteed consistency across them all.

The Fusion Plugin for Live S3 is a distributed network proxy for the S3 API that uses WANdisco Fusion to replicate data. Replication is performed selectively for S3 buckets, allowing any bucket to have replicas in other locations or S3 providers, including Amazon S3, Dell EMC Elastic Cloud Storage, IBM Cloud Object Storage, Amazon Snowball, Snowball Edge, Virtustream Storage Cloud and more. Requests made from client applications to the S3 endpoints provided by the proxy are coordinated so that activities performed against a single S3 bucket make content consistent across multiple buckets. These buckets can span separate AWS regions, or even be provided by alternative S3 implementations.

Multiple applications can use any of the replicated S3 endpoints at the same time, while WANdisco Fusion ensures that all activities are replicated with active-active consistency across all environments. Each application need only communicate with its local replicated S3 endpoint for objects that it uses to be made consistent across all S3 buckets.

Live S3 Architecture
Figure 1. Live S3 Architecture

Build distributed systems that use S3 with the Fusion Plugin for Live S3. Applications can operate against the same set of S3 objects in multiple locations, reading and writing against their local endpoint, while WANdisco Fusion ensures that the objects are accessible in every location.

Unlike cross-region replication that is native to Amazon S3, the Fusion Plugin for Live S3 supports the use of object replicas:

  • across multiple regions without the use of Object Versioning

  • between buckets within the same region if needed

  • in a multi-directional manner among as many buckets as you need

  • without granting Amazon S3 IAM roles just for the purpose of replication

  • without any need for maintaining metadata information that is specific to replication

  • preventing conflicting modifications to the bucket

  • with S3-compatible systems other than Amazon S3

  • between different S3 providers

3.3. Supported Functionality

3.3.1. S3 Features

The Fusion Plugin for Live S3 supports a broad range of S3-compatible features, including:

Virtual-hosted style URLs

where the virtual bucket name is part of the domain name in a virtual-hosted–style URL. For example: http://virtualbucket.s3proxyhost.yourdomain.com.

Path style URLs

where the bucket name is not included in the domain unless as a region-specific endpoint. For example: http://s3proxyhost.yourdomain.com/virtualbucket.

Client request signature validation

Requests are validated for correct credentials before being executed against an underlying S3-compatible storage. Versions 2 and 4 of AWS signatures are supported:

  1. AWS V4 Path Style

  2. AWS V4 Virtual Hosted Style

  3. AWS V3 Pre-signed URLs

  4. AWS V2 Path Style

  5. AWS V2 Virtual Hosted Style

  6. AWS V2 Pre-signed URLs

Payload Options

S3 Payloads can be signed or unsigned in a single chunk. Multi-chunk payloads are not yet supported.

Server-side Encryption

AES-256 server-side encryption is supported. AWS KMS SSE is not yet supported.

IAM role authentication

IAM role-based authentication is not yet supported.

MFA Serial authentication

Buckets configured with MFA serial security are not yet supported.

3.3.2. WANdisco Live Data Features

The Fusion Plugin for Live S3 provide support for additional features beyond those of standard S3 endpoints as a result of supporting Live Data functionality. These include:

Consistency Check

Determine and report on differences in content between replicated buckets.

Repair

Resolve any differences in the content among multiple buckets automatically.

3.3.3. S3 API Support

Broad support for the S3 API is offered by the Fusion Plugin for Live S3. Details of the specific operations that clients of the Fusion Plugin for Live S3 can use are provided below. Of note are:

  • the inability to create or delete buckets via the Fusion Plugin for Live S3

  • operations that use object identifiers (not keys) being only partially supported

  • POST operations that are unsupported

Operations on Services
Operations on Buckets
Operations on Objects

3.4. Deployment models

3.4.1. Use Cases for the Fusion Plugin for Live S3

Use the Fusion Plugin for Live S3 for a variety of reasons, including:

Heterogenous storage

Your applications may benefit from accessing S3 data in different storage systems, perhaps both on-premises and in the cloud, or with multiple cloud providers to take advantage of cost arbitrage.

Multi-geo applications

Applications that operate in multiple, geographically-separate locations can work with a local S3 endpoint in each location, and ensure that each location has access to the same data.

Improving performance

By having a local replica of a bucket, applications can operate more efficiently than if they need to work with data that are not physically close.

Improved availability

The impact of the failure of a single source of S3 objects can be eliminated by having a strongly-consistent replica of those objects in another source.

Regulatory compliance

Your compliance needs may require that you store multiple copies of data in different locations, or with different service providers.

The Fusion Plugin for Live S3 automates the replication of data across S3 buckets and ensures that they store exactly the same information, even when applications change content in any of the replicated buckets.

4. Installation

4.1. Pre-requisites

Along with the standard product requirements that you can find on the WANdisco Fusion Deployment Checklist, you also need to ensure that you have available:

  • WANdisco Fusion 2.11.0.2 for Local File System or ASF Hadoop 2.7.0

  • Java 1.8

  • One or more compatible providers of an S3 endpoint: AWS S3, AWS Snowball, Virtustream Storage Cloud or HGST Activescale. Note that other providers may be fully compatible with the WANdisco Fusion, and WANdisco will continue to test and validate functionality for a broad range of S3 implementations.

  • Credentials for accessing the S3 endpoints among which replication is required. For AWS S3, this will be in the form of an Access Key and Secret Access Key.

  • Details of the endpoint URL by which applications access the S3 service normally, e.g. s3-us-west-1.amazonaws.com

  • The name of each bucket used

  • Access to the hosts on which each WANdisco Fusion server is operating for the purpose of installation

  • The names of the WANdisco Fusion zones across which replication will occur.

The Live S3 plugin must be installed in all zones
All WANdisco Fusion servers that participate in S3 replication need to have the plugin installed. While you can be selective about which WANdisco Fusion zones will have S3 objects replicated for each virtual bucket, every WANdisco Fusion server in the network needs the plugin in order to function.

4.2. Installation

Install the Fusion Plugin for Live S3 using a standard RPM- or DEB-based installation process. Configure the plugin with simple command-line tools or manual changes to configuration files that are specific to the plugin.

Ensure you have read all known issues and pre-requisites before beginning installation.

4.2.1. Locate installation components

There are two RPM files that provide installable components for the plugin:

  • fusion-s3-plugin-localfs-2.7.0-1.0-161.noarch.rpm

  • fusion-s3-proxy-localfs-2.7.0-1.0-161.noarch.rpm

Obtain the files so that you can distribute them to the appropriate hosts in your deployment for WANdisco Fusion. The fusion-s3-plugin-localfs-2.7.0-1.0-161.noarch.rpm needs to be installed on each WANdisco Fusion server host in your deployment, while the fusion-s3-proxy-localfs-2.7.0-1.0-161.noarch.rpm needs to be installed on each machine where you intend to operate an S3 Proxy.

Install as many S3 Proxy instances as you need in each WANdisco Fusion zone. Improve scalability and availability by operating more than one S3 Proxy instance per zone.

4.2.2. Install the plugin

Install fusion-s3-plugin-localfs-2.7.0-1.0-161.noarch.rpm on each WANdisco Fusion server host as the superuser:

Install the plugin on each WANdisco Fusion server:
# rpm -i fusion-s3-plugin-localfs-2.7.0-1.0-161.noarch.rpm Enter

4.2.3. Install the proxy

Install fusion-s3-proxy-localfs-2.7.0-1.0-161.noarch.rpm on each host where you want to operate a S3 Proxy.

Install the proxy on each host required:
# rpm -i fusion-s3-proxy-localfs-2.7.0-1.0-161.noarch.rpm Enter

4.2.4. Create a replication rule for each virtual bucket

The Fusion Plugin for Live S3 uses a replication rule to coordinate activities against each virtual bucket. Using the WANdisco Fusion UI or API, create a replication rule whose path matches the name for the virtual bucket. e.g. If your virtual bucket has the name vbucket, you should create a replication rule for the path /vbucket.

4.2.5. Configure the plugin

Change current directory to /opt/wandisco/fusion/plugins/s3proxy/config.dist:

# cd /opt/wandisco/fusion/plugins/s3proxy/config.dist Enter

Execute the configuration script configure-s3proxy-plugin. Provide details of how the plugin will operate:

Virtual bucket name

Choose a name that will be the single identifier for the proxy’s virtual bucket. This name will be used by client applications when interacting with replicate S3 objects, and will be available at the endpoints offered by each of the S3 proxy instances.

Number of zones

The configuration script will prompt for further information for each zone:

Zone name

The name of the zone as defined by the WANdisco Fusion configuration.

Bucket name

The name of the underlying S3 bucket for this zone.

Bucket access key

Credentials for the underlying bucket.

Bucket secret access key

Further credentials for the underlying bucket.

S3 Provider

Underylying storage provider.

Bucket region

The region by which the bucket is located.

Bucket endpoint URL

The endpoint by which the bucket can be accessed. This can be in any of the forms: <hostname>, <hostname>:<port>, http(s)://<hostname>, or http(s)://<hostname>:<port>.

An example:

# ./configure-s3proxy-plugin Enter
Enter the virtual bucket name: vbucket Enter
Number of zones associated with this virtual bucket: 2 Enter
Enter zone-1 values:
Enter the zone name: zone1 Enter
Enter bucket name: zone1bucket Enter
Enter the bucket access key: <zone1bucket access key> Enter
Enter the bucket secret access key: <zone1bucket secret access key> Enter
Enter underlying s3 provider (AWS_S3 | AWS_SNOWBALL | VIRTUSTREAM | ACTIVESCALE): AWS_S3 Enter
Enter the bucket region: us-east-1 Enter
Enter the bucket endpoint url: s3.amazonaws.com Enter
Enter zone-2 values:
Enter the zone name: zone2 Enter
Enter bucket name: zone2bucket Enter
Enter the bucket access key: <zone2bucket access key> Enter
Enter the bucket secret access key: <zone2bucket secret access key> Enter
Enter underlying s3 provider (AWS_S3 | AWS_SNOWBALL | VIRTUSTREAM | ACTIVESCALE): AWS_S3 Enter
Enter the bucket region: us-east-1 Enter
Enter the bucket endpoint url: s3-eu-west-1.amazonaws.com Enter
Do you want to add another virtual bucket (yes/no): no Enter
 -----------------------------------------------------------------------------------------------
 * Bucket details *
      <bucket name="zone1bucket">
        <zonename>zone1</zonename>
        <virtualbucket>vbucket</virtualbucket>
        <accesskey>REDACTED_ACCESS_KEY1</accesskey>
        <secretaccesskey>REDACTED_SECRET_ACCESS_KEY1</secretaccesskey>
        <provider>AWS_S3</provider>
        <region>us-east-1</region>
        <endpoint-url>s3.amazonaws.com</endpoint-url>
      </bucket>
      <bucket name="zone2bucket">
        <zonename>zone2</zonename>
        <virtualbucket>vbucket</virtualbucket>
        <accesskey>REDACTED_ACCESS_KEY2</accesskey>
        <secretaccesskey>REDACTED_ACCESS_KEY2</secretaccesskey>
        <provider>AWS_S3</provider>
        <region>us-east-1</region>
        <endpoint-url>s3-eu-west-1.amazonaws.com</endpoint-url>
      </bucket>
 ------------------------------------------------------------------------------------------------
Confirm the s3proxy plugin configuration details (yes/no): yes Enter
S3Proxy plugin configuration done successfully, restart 'fusion-server' to load the plugin
 --------------------------------------------------------------------------------------------
 Note: You can edit the configuration values anytime in: /etc/wandisco/fusion/server/s3proxy-plugin-site.xml
       The fusion server must be restarted for the changes to take effect
 --------------------------------------------------------------------------------------------

Once completed, the script will produce the configuration file at /etc/wandisco/fusion/server/s3proxy-plugin-site.xml. You can modify this file later if required. If changed, restart the WANdisco Fusion server as configuration properties are obtained on WANdisco Fusion server startup only.

4.2.6. Configure the proxy

Change current directory to /opt/wandisco/s3proxy-server/bin:

# cd /opt/wandisco/s3proxy-server/bin Enter

Execute the configuration script configure-s3proxy-server. Provide details for the operation of the S3 proxy:

Server listen host

The network interface on which the proxy should listen for client connections. This can be a specific IP address, network name, or the 0.0.0.0 value if the proxy should listen on all available interfaces.

Server listen port

The IP port used by the proxy to accept client connections.

Enable SSL

The proxy supports HTTP or HTTPS access. SSL should be enabled to offer clients the option of communicating with the proxy via HTTPS. Specifying yes to this setting will require further information on the keystore path and password.

Fusion server host name

The host name of the WANdisco Fusion server associated with this proxy instance.

Fusion server request port

The request port offered by the WANdisco Fusion server.

Virtual bucket name

Use the same virtual bucket name as when configuring the plugin.

An example:

# ./configure-s3proxy-server Enter
Enter the S3Proxy server listen host [0.0.0.0]: 0.0.0.0 Enter
Enter the S3Proxy server listen port [8081]: 8081 Enter
Do you want to enable ssl (yes/no)?
  [If yes, you need to provide the keystore path and password]: no Enter
Enter the fusion server host name: s3proxydemo.wandisco.com Enter
Enter the fusion server request port [8023]: 8023 Enter
Enter the virtual bucket name: vbucket Enter
[Note: Ensure that the replication path for this virtual bucket is '/vbucket']
Do you want to add another virtual bucket (yes/no): no Enter
 ------------------------------------------------------------------------------------------------
 * S3Proxy server details *
S3Proxy server listen host: 0.0.0.0
S3Proxy server listen port: 8081
S3Proxy server SSL: false
 * Fusion server details *
Fusion server host name: s3proxydemo.wandisco.com
Fusion server request port: 8023
 * Bucket details *
<virtualbucket name="vbucket" repl-path="/vbucket" />
 ------------------------------------------------------------------------------------------------
Do you confirm the s3proxy server configuration details (yes/no): yes Enter
S3Proxy server configuration done successfully, start 's3proxy-server' to load the configuration
--------------------------------------------------------------------------------------------------------
 Note: You can edit the configuration values anytime in: /opt/wandisco/s3proxy-server/bin/core-site-zone1.xml, /opt/wandisco/s3proxy-server/bin/s3proxy-server-site.xml
       The s3proxy-server must be restarted for the changes to take effect
  -------------------------------------------------------------------------------------------------------

5. Operation

5.1. Configuration

Once configured, restart the WANdisco Fusion server to use the configuration applied:

# service fusion-server restart Enter

Then start each instance of the S3 proxy:

# service s3proxy-server start Enter

You can validate operation against the virtual buckets defined for the environment using standard S3 client applications, such as the AWS CLI tools, or tools like s3cmd.

5.1.1. Configuring Applications to use the Fusion Plugin for Live S3

Client applications can be configured to use the virtual buckets provided by the Fusion Plugin for Live S3 in multiple ways:

As an HTTP(S) proxy

Applications that would normally communicate directly with the underlying S3 bucket can be directed to use the proxy through standard HTTP(S) proxy configuration. The benefit of this approach is that it requires no change to application code to direct them to the Fusion Plugin for Live S3.

Ensure that the plugin has been configured to accept requests for the original hostname used by client applications. Specify the DNS compatible host names to match when configuring the proxy. Applications can continue to use the original bucket name if it matches the underlying bucket referred to by the proxy.

As a new S3 endpoint

Applications can direct S3 requests directly to the proxy, which provides virtual buckets. Configure your application to refer to the proxy as the S3 endpoint, and use the virtual bucket name.

5.2. Administration

Once configured, applications interact with the virtual buckets that have been configured. Standard S3 API operations are replicated with strong consistency among the underlying buckets, and content associated with objects created is replicated between these buckets.

Use the Fusion Plugin for Live S3 to provide a Live Data environment, where applications can interact with any of the replicated buckets, and each bucket will provide access to the same content regardless of where change is initiated.

5.2.1. Regular Application Operation

Operate your applications without change, whether they are custom applications, standard command line or other tools for working with S3.

5.2.2. Consistency Check

Because applications that do not interact with the Live S3 environment via the Fusion Plugin for Live S3 can modify bucket content without coordination or replication, the product provides a consistency check feature. Use consistency check to report on any differences among the replicated buckets.

For this release, consistency check is provided as a REST API. A consistency check is a potentially long-running task, initiated with a specific REST operation. Provide the path associated with the virtual bucket when initiating the check to specify which virtual bucket to review. e.g.

# curl -i -X POST "http://localhost:8082/plugin/s3proxy/cc?path=/vbucket" Enter
HTTP/1.1 202 Accepted
Content-Location: http://localhost:8082/fusion/task/84b417f3-ec60-11e7-aa4b-0242ac120002
Content-Length: 0
Server: Jetty(6.1.26)

Access the status of the consistency check task at the location referenced. e.g.

# curl -i -X GET "http://localhost:8082/fusion/task/84b417f3-ec60-11e7-aa4b-0242ac120002" Enter
HTTP/1.1 200 OK
Content-Length: 938
Content-Type: application/xml
Server: Jetty(6.1.26)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><task><taskId>84b417f3-ec60-11e7-aa4b-0242ac120002</taskId><timeCreated>1514528494614</timeCreated><creatorNodeId>400b7699-56d2-44c5-b07c-f42a760b966f</creatorNodeId><timeUpdated>1514528530417</timeUpdated><isDone>true</isDone><aborted>false</aborted><properties><entry><key>CC_REPORT_PATH</key><value>/vbucket/.fusion/4fc19ba7-e744-11e7-85c7-0242ac120003/metadata/84b417f3-ec60-11e7-aa4b-0242ac120002/cc-report</value></entry><entry><key>TOTAL_INCONSISTENCIES_FOUND</key><value>0</value></entry><entry><key>TASK_TYPE</key><value>S3PROXY_CONSISTENCY_CHECK</value></entry><entry><key>LOCAL_COMPLETE</key><value>1514528530417</value></entry><entry><key>LOCAL_START</key><value>1514528494614</value></entry><entry><key>CONSISTENCY_CHECK_STATUS</key><value>CONSISTENT</value></entry></properties><previousTask xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/></task>

Access the results of the consistency check at the location referenced. e.g.

# curl -i -X GET "http://localhost:8082/plugin/s3proxy/cc/report/84b417f3-ec60-11e7-aa4b-0242ac120002?path=/vbucket&withConsistencyReport=true" Enter
HTTP/1.1 200 OK
Content-Length: 301
Content-Type: application/xml
Server: Jetty(6.1.26)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><consistencyReport><path>/vb1</path><state>CONSISTENT</state><taskId>84b417f3-ec60-11e7-aa4b-0242ac120002</taskId><checksumMethod>MD5</checksumMethod><noInconsistencies>0</noInconsistencies><lastCheck>1514548334438</lastCheck></consistencyReport>

5.2.3. Repair

Resolve inconsistencies among buckets with the Repair feature. Initate a repair with a single REST API invocation, and access the status of the potentially long-running repair task at the location provided in response.

Specify the path of the virtual bucket and the name of the zone that will be used as the source of truth for repair. Repair ensures that each replicated bucket has the same content as the source of truth. This may introduce object deletion and creation in all other replicated zones, so use this feature with care. e.g.

# curl -i -X PUT "http://localhost:8082/plugin/s3proxy/repair?path=/vbucket&srcZone=zone1" Enter
HTTP/1.1 202 Accepted
Content-Location: http://localhost:8082/plugin/fusion/task/0088e14d-ec62-11e7-aa4b-0242ac120002
Content-Length: 0
Server: Jetty(6.1.26)

Access the status of the repair task at the location referenced. e.g.

# curl -i -X GET "http://localhost:8082/fusion/task/0088e14d-ec62-11e7-aa4b-0242ac120002" Enter
HTTP/1.1 200 OK
Content-Length: 679
Content-Type: application/xml
Server: Jetty(6.1.26)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><task><taskId>0088e14d-ec62-11e7-aa4b-0242ac120002</taskId><timeCreated>1514548109259</timeCreated><creatorNodeId>400b7699-56d2-44c5-b07c-f42a760b966f</creatorNodeId><timeUpdated>1514528530417</timeUpdated><isDone>true</isDone><aborted>false</aborted><properties><entry><key>TASK_TYPE</key><value>REPAIR_TASK</value></entry><entry><key>REPAIR_STATUS</key><value>COMPLETED</value></entry><entry><key>LOCAL_COMPLETE</key><value>1514548109903</value></entry><entry><key>LOCAL_START</key><value>1514548109259</value></entry></properties><previousTask xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/></task>

5.3. Troubleshooting

Observe information in the log files generated for the WANdisco Fusion server and the Fusion Plugin for Live S3 to troubleshoot issues at runtime. Exceptions or log entries with a SEVERE label may represent information that can assist in determining the cause of any problem.

As a distributed system, the Fusion Plugin for Live S3 will be impacted by the operation of the underlying S3 endpoints with which it communicates. You may also find it useful to review log or other information from these endpoints.


1. The Fusion Plugin for Live S3 does not offer support for bucket deletion with this operation.
2. The specified API contains payload as xml configuration with the dependency on destination bucket which has to be in the same region as the source bucket.
3. The specified API contains payload as xml configuration with the dependency on destination bucket which has to be in the different region from the source bucket.
4. The Fusion Plugin for Live S3 does not support the PUT Bucket operation to create a new bucket.
5. PUT Bucket Notification has payload as xml configuration containing topic arn which has the region that has to be same as the bucket region.
6. Deletion of specific object versions is not supported because independent S3 buckets assign different version identifiers to replicated instances of an object.
7. Deletion of tagging for a specific object version is not supported because independent buckets assign different version identifiers to replicated instances of an object.
8. POST is an alternative to PUT for browser-based uploads. The Fusion Plugin for Live S3 does not support coordination and replication of objects created through this operation.
9. POST Object restore allows restoration of a temporary copy of an archived object. It is not supported by the Fusion Plugin for Live S3.