Contact Us 1-800-596-4880

Upgrading and Migrating Amazon S3 Connector to Version 6.x

Upgrade Anypoint Connector for Amazon S3 (Amazon S3 Connector) to version 6.x.

Supported Upgrade Paths

From Version To Version

5.8.0

6.1.x

Changes in This Release

This connector is now migrated to AWS SDK for Java 2.x. This release contains the following changes:

  • Connection Types

    • The Basic and Role connection types are no longer available. Now, the new Connection (S3) connection type covers both connection types.

    • The Session Token parameter is removed.

    • The Try Default AWSCredentials Provider Chain parameter is removed. Use properties instead to avoid embedding secrets in Mule XML files.

  • Operations

    • The following operations are added:

      • Head Object

      • List Object Versions

      • Restore Object

      • Select Object Content

    • Some operation names are changed:

      • Create Object is now Put Object.

      • Delete Bucket Tagging Configuration is now Delete Bucket Tagging.

      • Delete Bucket Website Configuration is now Delete Bucket Website.

      • Get Bucket Cors Configuration is now Get Bucket Cors.

      • Get Bucket Logging Configuration is now Get Bucket Logging.

      • Get Bucket Tagging Configuration is now Get Bucket Tagging.

      • Get Bucket Versioning Configuration is now Get Bucket Versioning.

      • Get Bucket Website Configuration is now Get Bucket Website.

      • Get Object Metadata is now Get Object Attributes.

      • Initiate Multipart Upload is now Create Multipart Upload.

      • List Versions is now List Object Versions.

      • Set Bucket Acl is now Put Bucket Acl.

      • Set Bucket Cors Configuration is now Put Bucket Cors.

      • Set Bucket Lifecycle Configuration is now Put Bucket Lifecycle Configuration.

      • Set Bucket Logging Configuration is now Put Bucket Logging.

      • Set Bucket Notification Configuration is now Put Bucket Notification Configuration.

      • Set Bucket Policy is now Put Bucket Policy.

      • Set Bucket Tagging Configuration is now Put Bucket Tagging.

      • Set Bucket Versioning Configuration is now Put Bucket Versioning.

      • Set Bucket Website Configuration is now Put Bucket Website.

      • Set Object Acl is now Put Object ACL.

  • Parameters

    • Some operations now contain the following parameters:

      • Bucket Tags

      • Bytes range

      • Config Ref

      • Completed Parts

      • Location Constraint

      • Not matching ETag

      • Notification Configuration

      • Object ACL

      • Object identifiers

      • Page size

      • Part Number

      • Target Value

      • Target Variable

    • Some operations no longer contain the following parameters:

      • Content

      • Delimiter

      • Encoding Type

      • End

      • File Offset

      • First Byte

      • Force

      • Is Last Part

      • Last Byte

      • Max Uploads

      • Md5 Digest

      • Modified Since

      • Part ETags

      • Part Size

      • Region

      • Start

      • Tag Sets

      • Topic Configurations

      • Unmodified Since

      • Version Id

    • Some parameter names are changed:

      • Key is now Object key.

      • Source Key is now Source object key.

      • Destination Key is now Destination object key.

      • Canned ACL is now Acl or Object ACL. Acl in Create bucket now contains less enumerations.

      • Bucket Name is now Bucket.

      • Version Id is now Object version id.

      • Policy Text is now Policy.

      • Bucket Website Configuration is now Website Config.

      • Matching ETag Constraints is now Matching ETag.

    • Some parameter names are changed from title case to sentence case, for example, Bucket Name is changed to Bucket name.

  • Sources

    • The On Deleted Object source now contains the Folder and Config Ref parameters.

    • The On New Object source now contains the Folder, Queue Name, and Config Ref parameters.

  • Object Types

    • The following object types are added:

      • Api Checksum

      • Api Copy Object Result

      • Api Copy Part Result

      • Api Csv Input

      • Api Csv Output

      • Api Get Object Attributes Parts

      • Api Initiator

      • Api Input Serialization

      • Api Object Part

      • Api Object Version

      • Api Output Serialization

      • Api S3 Object

      • Api Scan Range

      • Bucket Acl Response

      • Bucket Cors Response

      • Bucket Notification Response

      • Bucket Policy Response

      • Bucket Response

      • Bucket Tagging Response

      • Bucket Versioning Response

      • Bucket Website Response

      • Complete Multipart Upload Response

      • Condition

      • Copy Object Response

      • Create Multipart Upload Response

      • Filter Rule

      • Get Object Acl Response

      • Get Object Attributes Response

      • Head Object Response

      • Lambda Function Configuration

      • Lifecycle Configuration

      • Lifecycle Rule

      • Lifecycle Rule Filter

      • List Buckets Response

      • Logging Status

      • Multipart Part

      • Notification Configuration Filter

      • Proxy Configuration

      • Put Object Response

      • Queue Configuration

      • Restore Object Response

      • Role

      • S3 Key Filter

      • S3 Object Trigger Response

      • Tag

      • Topic Configuration

      • Upload Part Copy Response

      • Upload Part Response

      • WebsiteConfiguration

    • The following object types are removed:

      • Access Control List Attributes

      • BLC Rule

      • Bucket

      • Bucket Logging Configuration

      • Bucket Website Configuration

      • Complete Multipart Upload Result

      • Copy Part Result

      • Key Version

      • Multipart Upload Listing

      • Object Metadata Parameter Group

      • Object Result

      • Part ETag

      • Part Listing

      • Part Summary

      • Routing Rule Condition

      • S3 Object Attributes

      • S3 Object Summary

      • S3 Version Summary

      • Upload Part Result

  • Error Types

    • The following error types are added:

      • S3:BAD_REQUEST

      • S3:CONNECTIVITY

      • S3:FORBIDDEN

      • S3:GLACIER_EXPEDITED_RETRIEVAL_NOT_AVAILABLE

      • S3:NO_SUCH_TAG_SET

      • S3:OBJECT_ALREADY_IN_ACTIVE_TIER

      • S3:RETRY_EXHAUSTED

      • S3:S3_ERROR

      • S3:SERVER_BUSY

      • S3:SERVICE_ERROR

    • The following error types are removed:

      • S3:ACCESS_DENIED

      • S3:ACCOUNT_PROBLEM

      • S3:AMBIGUOUS_GRANT_BY_EMAIL_ADDRESS

      • S3:BAD_DIGEST

      • S3:BUCKET_ALREADY_EXISTS

      • S3:BUCKET_ALREADY_OWNED_BY_YOU

      • S3:BUCKET_NOT_EMPTY

      • S3:CREDENTIALS_NOT_SUPPORTED

      • S3:CROSS_LOCATION_LOGGING_PROHIBITED

      • S3:ENTITY_TOO_LARGE

      • S3:ENTITY_TOO_SMALL

      • S3:EXPIRED_TOKEN

      • S3:ILLEGAL_VERSIONING_CONFIGURATION_EXCEPTION

      • S3:INCOMPLETE_BODY

      • S3:INCORRECT_NUMBER_OF_FILES_IN_POST_REQUEST

      • S3:INLINE_DATA_TOO_LARGE

      • S3:INTERNAL_ERROR

      • S3:INVALID_ACCESS_KEY_ID

      • S3:INVALID_ADDRESSING_HEADER

      • S3:INVALID_ARGUMENT

      • S3:INVALID_BUCKET_NAME

      • S3:INVALID_BUCKET_STATE

      • S3:INVALID_DIGEST

      • S3:INVALID_ENCRYPTION_ALGORITHM_ERROR

      • S3:INVALID_LOCATION_CONSTRAINT

      • S3:INVALID_OBJECT_STATE

      • S3:INVALID_PART

      • S3:INVALID_PART_ORDER

      • S3:INVALID_PAYER

      • S3:INVALID_POLICY_DOCUMENT

      • S3:INVALID_RANGE

      • S3:INVALID_REQUEST

      • S3:INVALID_RESPONSE_PRESIGNEDURL_MALFORMED

      • S3:INVALID_SOAP_REQUEST

      • S3:INVALID_SECURITY

      • S3:INVALID_STORAGE_CLASS

      • S3:INVALID_TARGET_BUCKET_FOR_LOGGING

      • S3:INVALID_TOKEN

      • S3:INVALID_URI

      • S3:KEY_TOO_LONG

      • S3:MALFORMED_ACL_ERROR

      • S3:MALFORMED_POST_REQUEST

      • S3:MALFORMED_XML

      • S3:MAX_MESSAGE_LENGTH_EXCEEDED

      • S3:MAX_POST_PRE_DATA_LENGTH_EXCEEDED_ERROR

      • S3:METADATA_TOO_LARGE

      • S3:METHOD_NOT_ALLOWED

      • S3:MISSING_ATTACHMENT

      • S3:MISSING_CONTENT_LENGTH

      • S3:MISSING_REQUEST_BODY_ERROR

      • S3:MISSING_SECURITY_ELEMENT

      • S3:MISSING_SECURITY_HEADER

      • S3:NO_LOGGING_STATUS_FOR_KEY

      • S3:NO_SUCH_BUCKET

      • S3:NO_SUCH_BUCKET_POLICY

      • S3:NO_SUCH_KEY

      • S3:NO_SUCH_LIFECYCLE_CONFIGURATION

      • S3:NO_SUCH_UPLOAD

      • S3:NO_SUCH_VERSION

      • S3:NOT_IMPLEMENTED

      • S3:NOT_SIGNED_UP

      • S3:OPERATION_ABORTED

      • S3:PERMANENT_REDIRECT

      • S3:PRECONDITION_FAILED

      • S3:REDIRECT

      • S3:REQUEST_IS_NOT_MULTI_PART_CONTENT

      • S3:REQUEST_TIME_TOO_SKEWED

      • S3:REQUEST_TORRENT_OF_BUCKET_ERROR

      • S3:RESTORE_ALREADY_IN_PROGRESS

      • S3:SERVICE_UNAVAILABLE

      • S3:SIGNATURE_DOES_NOT_MATCH

      • S3:SLOW_DOWN

      • S3:TEMPORARY_REDIRECT

      • S3:TOKEN_REFRESH_REQUIRED

      • S3:TOO_MANY_BUCKETS

      • S3:UNEXPECTED_CONTENT

      • S3:UNKNOWN

      • S3:UNRESOLVABLE_GRANT_BY_EMAIL_ADDRESS

      • S3:USER_KEY_MUST_BE_SPECIFIED

Requirements

Ensure your system meets the following compatibility requirements before you perform the upgrade:

Application/Service Version

Mule

4.3.0 and later

AWS SDK for Java

2.17.148

Upgrade Prerequisites

Before you perform the upgrade, create a backup of your files, data, and configuration in case you need to restore to the previous version.

Upgrade Steps

Follow these steps to perform the upgrade to version 6.0.0:

  1. In Anypoint Studio, create a Mule project.

  2. In the Mule Palette view, click Search in Exchange.

  3. In Add Dependencies to Project, enter amazon s3 in the search field.

  4. In Available modules, select Amazon S3 and click Add.

  5. Click Finish.

  6. Verify that the Amazon S3 dependency version is 6.0 in the pom.xml file in the Mule project.

Studio upgrades the connector automatically.

Post-Upgrade Steps

After you install the latest version of the connector, verify that your error handling is updated to work with the minor changes in error codes in this version of the connector.

Verify the Upgrade

After you install the latest version of the connector, follow these steps to verify the upgrade:

  1. In Studio, verify that there are no errors in the Problems or Console views.

  2. Verify that there are no problems in the project pom.xml file.

  3. Test the connection to verify that the operations work.

Revert the Upgrade

If it is necessary to revert to the previous version of Amazon S3, change the mule-amazon-s3 dependency version in the project’s pom.xml file to the previous version.

You must update the project’s pom.xml file in Anypoint Studio.

View on GitHub