---
title: "Amazon S3"
slug: "s3-integration"
tags: ["Enterprise"]
updated: 2026-04-27T16:16:12Z
published: 2026-04-27T16:16:12Z
canonical: "support.perimeter81.com/s3-integration"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.perimeter81.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon S3

<meta charset="utf-8">

## Understanding Data Exporting to S3 bucket

Important Update - 

- The Amazon S3 integration in Check Point SASE is planned for deprecation.
- The integration stops working on December 1, 2026.
- Customers without an existing configuration no longer see this integration as an available option in the portal.

**Recommended action****-** Migrate to the export option available in the Check Point Infinity Portal before December 1, 2026. This action prevents disruption to log forwarding.

The configuration steps remain available for reference while the integration stays active for existing customers.

This article describes the Amazon S3 service and how to configure it. Amazon Simple Storage Service (Amazon S3) is an object storage service that offers industry-leading scalability, data availability, security, and performance. You can configure your Check Point SASE data stream to an S3 bucket to have full visibility of your Check Point SASE activity.

## Create a new Bucket

1. Open the AWS Management Console and select **S3**.  
![360010931659ScreenShot2020-04-12at151541.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360010931659ScreenShot2020-04-12at151541.png)
2. Select **Create Bucket**.  
![360010927040ScreenShot2020-04-12at151107.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360010927040ScreenShot2020-04-12at151107.png)
3. Fill in the following information:  
![360010928060ScreenShot2020-04-12at151827.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360010928060ScreenShot2020-04-12at151827.png)

- **Bucket name****:** Enter a name of your choice  
Please note that Check Point SASE doesn't support "-" or "." (dots), please use letters only.
- **Region****:** Amazon S3 creates buckets in a Region you specify. To optimize latency, minimize costs, or address regulatory requirements, choose any AWS Region that is geographically close to you.

![360010928140ScreenShot2020-04-12at171713.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360010928140ScreenShot2020-04-12at171713.png)

- Block all public access is checked by default. You may choose to customize it according to your company policy.

![360010932239ScreenShot2020-04-12at171815.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360010932239ScreenShot2020-04-12at171815.png)

- Disable object lock, then select **Create bucket**.

## Create a new IAM Policy

**Important**: At this point, you can choose to grant the user full access to your S3 buckets (by attaching the appropriate AWS managed policy) or create a new policy that applies only to the Check Point SASE bucket. If you choose the first option, you may skip this section.

1. Open the AWS Identity and Access Management (**IAM**) dashboard.
2. Go to the **Policies** tab and select **Create policy**.
3. Paste the following snippet as a JSON file. Replace test with the bucket name, then select **Review policy**.  
![360010947520ScreenShot2020-04-14at100750.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360010947520ScreenShot2020-04-14at100750.png)

```shell
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "s3:*",
            "Resource": "arn:aws:s3:::test"
        },
        {
            "Effect": "Allow",
            "Action": "s3:*",
            "Resource": "arn:aws:s3:::test/*"
        }
    ]
}
```

ImportantThe template presented above, while scoped to a single bucket associated with Check Point SASE's logs only, will grant a [wide variety of permissions](https://docs.aws.amazon.com/AmazonS3/latest/API/API_Operations_Amazon_Simple_Storage_Service.html). If for any reason you choose to limit the list of permissions, make sure that at the very least it includes parts highlighted below: <meta charset="utf-8">

```
{
"Version" : "2012-10-17",
"Statement" : [
{
"Effect" : "Allow" ,
"Action" : [
"s3:ListBucket",
"s3:GetBucketLocation"
],
"Resource" : ["${aws_s3_bucket.pm81-logs.arn}"]
},
{
"Effect" : "Allow" ,
"Action" : [
"s3:PutObject" ,
"s3:GetObject" ,
"s3:DeleteObject" ],
"Resource" : ["${aws_s3_bucket.pm81-logs.arn}/*" ]
}
]}
```

![360010949399ScreenShot2020-04-14at101304.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360010949399ScreenShot2020-04-14at101304.png)

4. Fill in the following information, and then select **Create** **policy**.

- **Name****:** Enter a name of your choice.
- **Description** (optional)**:** Let other users in your account know what this policy aims for.

## Create an AWS user

1. Open the AWS Identity and Access Management (**IAM** ) dashboard.
2. Go to the **Users** tab and select **Add user**.
  - **Username:** Enter a name of your choice. <wt-ignore source="wt-feature-result" uuid="7c97a6c3-3df4-40e6-80b6-b57a7e3d66e9">And</wt-ignore> select next.![](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/image-1679229508741.png)
3. Select **Attach existing policies directly** and choose the policy you created earlier (if you skipped the previous section, select the S3 full access AWS managed policy). Select **Next**.![](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/image-1679229556154.png)

## Create an AWS access key

1. Open the AWS Identity and Access Management (**IAM** ) dashboard.
2. <wt-ignore source="wt-feature-result" uuid="1e5fbfa8-f16c-42ce-82d6-af7deda2f623">Navigate</wt-ignore> to the **Users** tab and select **the user you have created**.
3. <wt-ignore data-pm-slice="0 0 []" source="wt-feature-result" uuid="71f4ab5f-48bd-4b3a-851f-53d4b62dbe3f">Navigate</wt-ignore> to the **Security credentials** tab![](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/image-1679229764345.png)
4. Scroll down to **Access keys** and select******Create access****key****![](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/image-1679229837542.png)**
5. <wt-ignore source="wt-feature-result" uuid="6baf7f68-2f8b-4ac7-9105-36bcca33913b">Choose</wt-ignore> **Application running outside <wt-ignore source="wt-feature-result" uuid="27a4455a-aae5-40c2-af81-e304c32ceb12">AWS</wt-ignore>**<wt-ignore source="wt-feature-result" uuid="27a4455a-aae5-40c2-af81-e304c32ceb12">&nbsp;and</wt-ignore> click next![](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/image-1679229902016.png)
6. <wt-ignore data-pm-slice="0 0 []" source="wt-feature-result" uuid="349a383b-c0f4-4d8b-b012-c74c10f0b295">Choose</wt-ignore> **Create access****key**(you can add **Description tag value if you like)**
7. **<wt-ignore data-pm-slice="0 0 []" source="wt-feature-result" uuid="d42447c6-0bae-4998-982d-087e2081a323">Copy</wt-ignore> <wt-ignore source="wt-feature-result" uuid="9532e02b-b95e-4df7-8d8c-118e0296cb8e">the&nbsp;</wt-ignore><wt-ignore source="wt-feature-result" uuid="9532e02b-b95e-4df7-8d8c-118e0296cb8e">Secret</wt-ignore> access <wt-ignore source="wt-feature-result" uuid="2de72eb8-4c8a-4153-ae77-405372330e87">key</wt-ignore><wt-ignore source="wt-feature-result" uuid="2de72eb8-4c8a-4153-ae77-405372330e87">&nbsp;and</wt-ignore> the Access key****![](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/image-1679230035502.png)**

## Connect the S3 bucket to Check Point SASE

1. Log in to your Check Point SASE Management Platform, and navigate to **Settings/Integrations,** and select Add at the Amazon S3 row.  
![360011062679ScreenShot2020-04-16at105728.png](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/360011062679ScreenShot2020-04-16at105728.png)
2. Fill in according to the values copied in the previous steps (the primary key will be used as your workspace key)  
![](https://cdn.document360.io/44667c0c-50d7-412a-acbd-20d4a41c952e/Images/Documentation/image-1727893053914.png)
  - <wt-ignore source="wt-feature-result" uuid="6fb6efa5-9c64-4377-bf7b-c4f531bf3626">Access</wt-ignore> key ID = **Access key**(copied from AWS)****
  - <wt-ignore source="wt-feature-result" uuid="badea767-b0a2-40f1-95c4-ecfce12c72f8">Secret</wt-ignore> access key = **Secret access key** (copied from AWS)
  - <wt-ignore source="wt-feature-result" uuid="db3b248c-0a8d-436b-939f-9278eadeed75">Bucket</wt-ignore> = Your S3 Bucket Identifier <wt-ignore source="wt-feature-result" uuid="ad973ecc-3c6f-4c69-92d7-a95e4101efc6">(for</wt-ignore> example- if your bucket name is "arn:aws:s3:::tests3bucket", you will only need to input "tests3bucket")
  - <wt-ignore source="wt-feature-result" uuid="8d1359ba-e5bf-4e49-8015-f480a5758ea7">Bucket</wt-ignore> region = The region you <wt-ignore source="wt-feature-result" uuid="4d9d2f6c-9989-4071-a80b-e8fc10caf17a">chose</wt-ignore> in the first step
3. Select ***Validate***.

## Recommendations

- Ensure that the IAM user has the necessary permissions to access the S3 bucket.
- Regularly review and update your S3 bucket settings to align with your organization's security policies.
- When setting up the integration, double-check the provided AWS credentials to avoid connectivity issues

Check Point SASE uses these IP addresses to deliver SIEM logs

- US tenant:
  - 44.199.0.186
  - 44.198.227.127
  - 50.19.134.176
  - 23.20.83.77
  - 54.85.165.134
- EU tenant:
  - 52.50.186.78
  - 79.125.50.175
  - 34.246.127.40

## Troubleshooting

| **Status message<meta charset="utf-8">** | **Action required** |
| --- | --- |
| Success | None |
| S3_INVALID_ACCESS_KEY_ID | Make sure you copied correctly the access key ID |
| S3_INVALID_SECRET_ACCESS_KEY | Make sure you copied correctly the secret access key. |
| S3_INVALID_BUCKET | Make sure the Bucket name in Check Point SASE matched the Bucket name in S3 (case sensitive). |
| S3_ACCESS_DENIED_BUCKET | The IAM user doesn't have the required access permissions to the bucket. Make sure to attach the appropriate policy. |

<meta charset="utf-8">

## Support Contacts

If you have any difficulties or questions, don't hesitate to contact Check Point SASE's support team. We offer 24/7 chat support on our website at [sase.checkpoint.com](https://www.sase.checkpoint.com/), or you can email us at sase-support@checkpoint.com. We're here to assist you and ensure your VPN tunnel setup is a success.
