---
schema_version: "1"
id: 2958e787ac4eaa5abd1878cf7fb18386bd0757595045dc6c6ea9c7399843c387
title: Troubleshooting Amazon S3 Connector 7.1
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/amazon-s3-connector/7.1/amazon-s3-connector-troubleshooting.md
canonical_url: https://docs.mulesoft.com/amazon-s3-connector/7.1/amazon-s3-connector-troubleshooting
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d30da1048949700261f7c01f1623b8d3cda9c70ded2639a6b131ec997a00638e
description: MuleSoft Documentation Site
release: "7.1"
latest: false
---
---
product: Amazon S3 Connector
version: 7.1
---

# Troubleshooting Amazon S3 Connector 7.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To troubleshoot Anypoint Connector for Amazon S3 (Amazon S3 Connector), become familiar with the
information about interpreting commonly thrown exception messages.

## Enable SSL Logging

Enable SSL logs to investigate an issue related to TLS communications.

Set your SSL log level depending on your required level of detail:

1.  Enable only SSL log details:

    `javax.net.debug=ssl`

2.  Enable only handshaking details. (The handshake protocol is a series of messages exchanged over
    the record protocol.)

    `javax.net.debug=ssl:handshake`

3.  Enable handshaking details and SSL details at the same time:

    `javax.net.debug=ssl, handshake`

4.  Enable the dumping of all details and traffic data:

    `javax.net.debug=all`

    > [!NOTE] This option is very verbose and under normal circumstances is not necessary.

> [!WARNING] SSL logging results in a performance impact for HTTPS or other TLS connections. Enable
> SSL logging only to troubleshoot a specific issue and do not enable it for extended periods. SSL
> logging produces a significant amount of log messages and can inundate your log file if it is left
> enabled and unattended.

To enable SSL logs:

Set the debug parameter as an argument in the runtime configuration for the application.

1.  In Studio, right-click on the project and select **Run > Run Configurations**.

2.  Go to the **Arguments** tab and add `-M-Djavax.net.debug=ssl` in the **VM arguments** section.

## Enable Verbose Exception Logging

Enable verbose exception logs to show a complete stack trace of the error instead of the default
truncated output:

1.  In Studio, right-click on the project and select **Run > Run Configurations**.

2.  Go to the **Arguments** tab and append the arguments in the **VM arguments** section to add the
    `mule.verbose.exceptions` property. For example:

    `-XX:PermSize=128M -XX:MaxPermSize=256M -Dmule.verbose.exceptions=true`

## Enable Verbose Logging

To get a better understanding of why an application’s interaction with Amazon S3 Connector is
failing, temporarily enable verbose logging for the connector.

Remember to always disable enhanced verbosity after troubleshooting, because it can affect your Mule
application’s performance.

To enable verbose logging in the configuration file:

1.  Access Anypoint Studio and navigate to the **Package Explorer** view.

2.  Open your application’s project name.

3.  Open the `src/main/resources` folder.

4.  Open the `log4j2.xml` file inside the folder.

5.  Add an `<AsyncLogger>` tag inside the `<Loggers>` tag:

    ```xml
    			<Loggers>
    				...
    				<AsyncLogger name="org.mule.extension.s3" level="DEBUG"/>
    				...
    			</Loggers>
    ```

6.  Save your application changes.

7.  Click the project name in **Package Explorer** and then click **Run** > **Run As** > **Mule
    Application**.

## Understand Commonly Thrown Exceptions

Here is a list of commonly thrown exception messages and how to interpret them:

- S3:BAD\_REQUEST

  The input or payload is invalid.

- S3:BUCKET\_ALREADY\_EXISTS

  The bucket name you specify already exists.

- S3:BUCKET\_ALREADY\_OWNED\_BY\_YOU

  The bucket you create already exists and is owned by you.

- S3:CONNECTIVITY

  A connection cannot be established.

- S3:FORBIDDEN

  There is a \`403\` forbidden error, for example, there are missing permissions.

- S3:GLACIER\_EXPEDITED\_RETRIEVAL\_NOT\_AVAILABLE

  Expedited retrieval is not available.

- S3:INTERNAL\_ERROR

  There is an internal error, such as a server issue or a temporary glitch.

- S3:INVALID\_OBJECT\_STATE

  The object state is invalid with the action.

- S3:MALFORMED\_XML

  The XML you send is malformed.

- S3:NO\_SUCH\_KEY

  The key you specify does not exist.

- S3:NO\_SUCH\_LIFECYCLE\_CONFIGURATION

  The lifecycle configuration you specify does not exist.

- S3:NO\_SUCH\_TAG\_SET

  The tag set you specify does not exist.

- S3:NO\_SUCH\_UPLOAD

  The upload you specify does not exist.

- S3:OBJECT\_ALREADY\_IN\_ACTIVE\_TIER

  The object is already in the active tier.

- S3:OPERATION\_ABORTED

  The operation is aborted because there is another in-progress action against the same resource.

- S3:RESTORE\_ALREADY\_IN\_PROGRESS

  The restore is already in progress.

- S3:RETRY\_EXHAUSTED

  The maximum number of retries for the operation is reached.

- S3:S3\_ERROR

  An error occurs in Amazon S3.

- S3:SERVER\_BUSY

  The server is busy.

- S3:SERVICE\_ERROR

  There is a service error.

- S3:REQUEST\_TIMEOUT

  The Put Object operation had a request timeout.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Amazon S3 Connector Reference](https://docs.mulesoft.com/amazon-s3-connector/7.1/amazon-s3-connector-reference)

- [Salesforce Help](https://help.salesforce.com)

- [Known Issues](https://help.salesforce.com/s/issues)