You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/data-localization/how-to/r2.mdx
+15-18Lines changed: 15 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,9 @@ title: R2 Object Storage
3
3
pcx_content_type: how-to
4
4
sidebar:
5
5
order: 6
6
-
7
6
---
8
7
9
-
import { Details } from"~/components"
8
+
import { Details } from"~/components";
10
9
11
10
In the following sections, we will give you some details about how to configure R2 with Regional Services and Customer Metadata Boundary.
12
11
@@ -32,7 +31,7 @@ The following instructions will show you how to set up a Logpush job using an S3
32
31
33
32
<Detailsheader="Generate a token for a specific bucket (recommended)">
34
33
35
-
Go to the R2 section of your Cloudflare dashboard and select **Manage R2 API Tokens** to generate a token directly tied to your specific bucket. You can follow the instructions in the [Authentication](/r2/api/s3/tokens/) section.
34
+
Go to the R2 section of your Cloudflare dashboard and select **Manage R2 API Tokens** to generate a token directly tied to your specific bucket. You can follow the instructions in the [Authentication](/r2/api/tokens/) section.
36
35
37
36
</Details>
38
37
@@ -54,19 +53,19 @@ The result:
54
53
55
54
```json
56
55
{
57
-
"result": {
58
-
"id": "325xxxxcd",
59
-
"status": "active"
60
-
},
61
-
"success": true,
62
-
"errors": [],
63
-
"messages": [
64
-
{
65
-
"code": 10000,
66
-
"message": "This API Token is valid and active",
67
-
"type": null
68
-
}
69
-
]
56
+
"result": {
57
+
"id": "325xxxxcd",
58
+
"status": "active"
59
+
},
60
+
"success": true,
61
+
"errors": [],
62
+
"messages": [
63
+
{
64
+
"code": 10000,
65
+
"message": "This API Token is valid and active",
66
+
"type": null
67
+
}
68
+
]
70
69
}
71
70
```
72
71
@@ -97,10 +96,8 @@ With Customer Metadata Boundary set to `EU`, **R2** > **Bucket** > [**Metrics**]
97
96
98
97
:::note
99
98
100
-
101
99
Additionally, customers can create R2 buckets with [jurisdictional restrictions set to EU](/r2/reference/data-location/#jurisdictional-restrictions). In this case, we recommend [using jurisdictions with the S3 API](/r2/reference/data-location/#using-jurisdictions-with-the-s3-api).
102
100
103
-
104
101
:::
105
102
106
103
Refer to the [R2 documentation](/r2/) for more information.
<Detailsheader="I am getting an error when accessing the API">
138
136
139
-
***Error**: Time range returned too many results. Try reducing the time range and try again.
137
+
-**Error**: Time range returned too many results. Try reducing the time range and try again.
140
138
141
139
HTTP status code `422` will be returned if the time range between the start and end parameters is too wide. Try querying a shorter time range if you are running into this limit.
142
140
143
-
***Error**: Provided token does not have the required features enabled.
141
+
-**Error**: Provided token does not have the required features enabled.
144
142
145
143
Contact your account representative to have the beta Logpull RayID Lookup subscription added to your account.
146
144
147
-
***Error**: Time range returned too many results. Try reducing the time range and try again.
145
+
-**Error**: Time range returned too many results. Try reducing the time range and try again.
148
146
149
147
High volume zones can produce many log files in R2. Try reducing your start and end time range until you find a duration that works best for your log volume.
150
148
151
-
152
149
</Details>
153
150
154
-
155
151
<Detailsheader="How do I know what time range to index?">
156
152
157
153
Currently, there is no process to index logs as they arrive. If you have the RayID and know the time the request was made, try indexing the next 5-10 minutes of logs after the request was completed.
158
154
159
-
160
155
</Details>
161
156
162
-
163
157
<Detailsheader="What is the time delay between when an event happens and when I can query for it?">
164
158
165
159
Logpush delivers logs in batches as soon as possible, generally in less than one minute. After this, logs can be accessed using Logs Engine.
166
160
167
-
168
161
</Details>
169
162
170
-
171
163
<Detailsheader="Does R2 have retention controls?">
172
164
173
165
R2 does not currently have retention controls in place. You can query back as far as when you created the Logpush job.
174
166
175
-
176
167
</Details>
177
168
178
-
179
169
<Detailsheader="Which datasets is Logs Engine compatible with?">
180
170
181
171
The retrieval API is compatible with all the datasets we support. The full list is available on the [Log fields](/logs/reference/log-fields/) section.
0 commit comments