Skip to content

Commit c5468c0

Browse files
[Email Security] Adding prereq
1 parent cb758e5 commit c5468c0

File tree

1 file changed

+31
-20
lines changed

1 file changed

+31
-20
lines changed

src/content/docs/cloudflare-one/insights/email-monitoring/email-security-logs.mdx

Lines changed: 31 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -5,45 +5,56 @@ sidebar:
55
order: 5
66
---
77

8-
Email Security allows you to configure logs to send detection data to an endpoint of your choosing.
8+
Email Security allows you to configure Logpush to send detection data to an endpoint of your choice.
9+
10+
## Prerequisites
11+
12+
Before you can enable Logpush for Email Security, you will have to:
13+
14+
1. Create an [R2 bucket](/r2/get-started/#2-create-a-bucket).
15+
2. Once you have created your R2 bucket, [create an API token](/r2/api/s3/tokens/). Under **Permissions**, ensure you select **Admin Read & Write**.
16+
3. Once you have created your R2 API Token, the dashboard will display an **Access Key ID**, and **Secret Access Key**. Save these two, as you will need them to set up Logpush later.
17+
18+
## Enable Logpush jobs
919

1020
To enable Logpush for Email Security:
1121

1222
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
1323
2. Select **Analytics & Logs** > **Logpush**.
1424
2. Select **Create a Logpush job**, then select **S3-Compatible**.
1525
3. Enter the **destination details**:
16-
- **Bucket**: Enter the bucket name.
26+
- **Bucket (required)**: Enter the bucket name.
1727
- **Endpoint URL**: Enter your endpoint URL. To find your endpoint URL:
1828
- On the Cloudflare dashboard, go to **R2 Object Storage** > **Overview** > Select your bucket.
1929
- Go to Settings, and copy and paste the **S3 API** URL.
20-
- **Bucket region**: Enter the Bucket region: Enter the region of your bucket: To find the bucket region:
30+
- **Bucket region**: Enter the region of your bucket. To find the bucket region:
2131
- On the dashboard, go to **R2 Object Storage** > **Overview** > Select your bucket.
22-
- Go to Settings, and find your region in **Location**.
23-
- Enter the **Access Key ID**.
24-
- Enter the **Secret Access Key**.
25-
4. Select **Continue**. Your destination has now been configured.
32+
- Go to **Settings**, and find your region in **Location**.
33+
- **Access Key ID**: Enter the Access Key ID you created as a [prerequisite](/cloudflare-one/insights/email-monitoring/email-security-logs/#prerequisites).
34+
- **Secret Access Key**: Enter the Secret Access Key you created as a [prerequisite](/cloudflare-one/insights/email-monitoring/email-security-logs/#prerequisites).
35+
4. Select **Continue**.
36+
37+
Your destination has now been configured.
38+
39+
To view the job you created:
40+
41+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
42+
2. Go to **R2 Object Storage**, select your bucket.
43+
3. Select **Objects**.
2644

2745
## Audit logs
2846

29-
Once you have configured your destination, you can audit your logs.
47+
Once you have configured your destination, you can audit logs:
3048

3149
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
3250
2. Select **Analytics & Logs** > **Logpush**.
3351
3. Select **Audit logs**.
34-
4. **Configure logpush job**:
52+
4. Under **Configure logpush job**:
3553
- **Job name**: Enter the job name.
3654
- **If logs match**: Select **Filtered logs**:
37-
- Field: Choose ResourceType
38-
- Operator: starts with
39-
- Value: Enter `email_security`
40-
- **Send the following field**: Ensure **General** is selected.
55+
- **Field**: Choose `ResourceType`.
56+
- **Operator**: Choose `starts with`.
57+
- **Value**: Enter `email_security`.
4158
5. Select **Submit**.
4259

43-
Your job has now been created successfully.
44-
45-
To view the job you created:
46-
47-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
48-
2. Go to **R2 Object Storage**, select your bucket.
49-
3. Select **Objects**.
60+
Your job has now been created successfully.

0 commit comments

Comments
 (0)