---
schema_version: "1"
id: a934cc9ea81c293d23df6861e75a405f0a81ad5d960af76f615f1921d7fc88a4
title: Amazon S3 Connector 8.0 Additional Configuration
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/amazon-s3-connector/latest/amazon-s3-connector-config-topics.md
canonical_url: https://docs.mulesoft.com/amazon-s3-connector/latest/amazon-s3-connector-config-topics
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 4e7002157ea5a72a9098b17844ca7392e1fb26bc32a3fa044e59f49b9957fede
description: MuleSoft Documentation Site
release: "8.0"
latest: true
---
---
product: Amazon S3 Connector
version: 8.0
is-latest-version: true
---

# Amazon S3 Connector 8.0 Additional Configuration

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

## Before You Begin for Source Operations

Amazon S3 source operations use Amazon SQS for notifying when a new object is created or deleted in
an S3 bucket.

There are multiple scenarios for the **On New Object** and **On Deleted Object** Amazon S3 sources:

1.  The [queue is already created](#queue-is-created) and specified

2.  The [queue is created](#queue-created-by-source) by the source

3.  The [event notification configuration is created](#configuration-is-created) by the source

## Queue Is Already Created

To correctly use a source for a queue that already exists, the user must have these actions enabled
for the Amazon SQS queue:

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "VisualEditor0",
      "Effect": "Allow",
      "Action": [
        "sqs:DeleteMessage",
        "sqs:GetQueueUrl",
        "sqs:ReceiveMessage",
        "sqs:GetQueueAttributes"
      ],
      "Resource": "arn:aws:sqs:REGION:ACCOUNT_ID:QUEUE_NAME"
    }
  ]
}
```

Additionally, to enable the queue to receive messages when a new object is created or deleted in an
S3 bucket, create a policy for the queue in this format:

```json
{
  "Version": "2012-10-17",
  "Id": "arn:aws:sqs:REGION:ACCOUNT_ID:QUEUE_NAME/SQSDefaultPolicy",
  "Statement": [
    {
      "Sid": "Sid1593770403887",
      "Effect": "Allow",
      "Principal": "*",
      "Action": "SQS:SendMessage",
      "Resource": "arn:aws:sqs:REGION:ACCOUNT_ID:QUEUE_NAME",
      "Condition": {
        "ArnLike": {
          "aws:SourceArn": "arn:aws:s3:::BUCKET_NAME"
        }
      }
    }
  ]
}
```

## Queue Is Created by Source

If the queue is created by the source, the queue name has the prefix `MULE-S3-TRIGGER`.

When the queue is created by the source, the user must have permission to both create a queue and
set the queue attributes:

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "VisualEditor0",
      "Effect": "Allow",
      "Action": [
        "sqs:DeleteMessage",
        "sqs:ReceiveMessage",
        "sqs:GetQueueAttributes",
        "sqs:CreateQueue",
        "sqs:SetQueueAttributes",
        "sqs:GetQueueUrl"
      ],
      "Resource": "arn:aws:sqs:REGION:ACCOUNT_ID:MULE-S3-TRIGGER-*"
    }
  ]
}
```

When the queue is created by the source, an SQS policy is added to the queue in the following format
when the S3 object is created or deleted in the bucket :

```json
{
  "Version": "2012-10-17",
  "Id": "example-ID",
  "Statement": [
    {
      "Sid": "example-statement-ID",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
    },
      "Action": "SQS:SendMessage",
      "Resource":QUEUE_ARN,
      "Condition": {
        "ArnLike": {
          "aws:SourceArn": "BUCKET_ARN"
        }
      }
    }
  ]
}
```

## Notification Configuration for S3 Bucket Events is Already Created

To correctly use a source for a notification configuration that already exists, you must specify the
notification configuration name in the ADVANCED tab of the source:

```xml
   <s3:new-object-trigger doc:name="On New Object" config-ref="${config}" bucketName="example-bucket-name"
                               notificationConfigurationName="on-new-object-configuration">
            <scheduling-strategy>
                <fixed-frequency/>
            </scheduling-strategy>
        </s3:new-object-trigger>
```

## S3 Policy Bucket

For the S3 policy, use this format for all cases:

```json
{
  "Version": "2012-10-17",
  "Id": "Policy1593761427184",
  "Statement": [
    {
      "Sid": "Stmt1593760119344",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::ACCOUNT_ID:user/test"
      },
      "Action": "SPECIFIC_ACTION",
      "Resource": "arn:aws:s3:::BUCKET_NAME/*"
    },
    {
      "Sid": "Stmt1593760259223",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::ACCOUNT_ID:user/test"
      },
      "Action": ["s3:PutBucketNotification", "s3:GetBucketNotification"],
      "Resource": "arn:aws:s3:::BUCKET_NAME"
    }
  ]
}
```

In this example, the **SPECIFIC\_ACTION** is `s3:PutObject` or `s3:DeleteObject`, depending on the
specified source operation.

## Next Step

After you complete configuring the connector, you can try the
[Example](https://docs.mulesoft.com/amazon-s3-connector/latest/amazon-s3-connector-examples).

## See Also

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