diff --git a/src/content/docs/r2/buckets/event-notifications.mdx b/src/content/docs/r2/buckets/event-notifications.mdx index 5325ecef5ea07e..8243543adafad9 100644 --- a/src/content/docs/r2/buckets/event-notifications.mdx +++ b/src/content/docs/r2/buckets/event-notifications.mdx @@ -12,7 +12,7 @@ Event notifications send messages to your [queue](/queues/) when data in your R2 Before getting started, you will need: - An existing R2 bucket. If you do not already have an existing R2 bucket, refer to [Create buckets](/r2/buckets/create-buckets/). -- An existing queue. If you do not already have a queue, refer to [Create a queue](/queues/get-started/#3-create-a-queue). +- An existing queue. If you do not already have a queue, refer to [Create a queue](/queues/get-started/#2-create-a-queue). - A [consumer Worker](/queues/reference/how-queues-works/#create-a-consumer-worker) or [HTTP pull](/queues/configuration/pull-consumers/) enabled on your Queue. ### Enable event notifications via Dashboard diff --git a/src/content/docs/r2/tutorials/cloudflare-access.mdx b/src/content/docs/r2/tutorials/cloudflare-access.mdx index 381033166a3d6c..597c2a93bea690 100644 --- a/src/content/docs/r2/tutorials/cloudflare-access.mdx +++ b/src/content/docs/r2/tutorials/cloudflare-access.mdx @@ -35,7 +35,7 @@ Within the **Zero Trust** section of the Cloudflare Dashboard, you will need to If you have not configured Cloudflare Access before, we recommend: * Configuring an [identity provider](/cloudflare-one/identity/) first to enable Access to use your organization's single-sign on (SSO) provider as an authentication method. -* Creating an [Access group](/cloudflare-one/identity/users/groups/#access-groups) that defines which users or groups within your organization can access specific resources. +* Creating an [Access group](/cloudflare-one/identity/users/groups/) that defines which users or groups within your organization can access specific resources. To create an Access application for your R2 bucket: @@ -47,7 +47,7 @@ To create an Access application for your R2 bucket: 6. Configure the **Identity providers** that will be used to protect this domain using Access. 7. Click **Next** 8. Enter a **Policy name** and an **Action**. This should be **Allow**, and will enable the group(s) you select to access objects within the bucket behind this Access application. -9. To **Assign a group** (or groups) and allow access to your bucket, select one or more groups. If you have not created any groups, you will [need to do this first](/cloudflare-one/identity/users/groups/#access-groups). You should **ensure that this group only contains the users within your organization that need access to this R2 bucket**. +9. To **Assign a group** (or groups) and allow access to your bucket, select one or more groups. If you have not created any groups, you will [need to do this first](/cloudflare-one/identity/users/groups/). You should **ensure that this group only contains the users within your organization that need access to this R2 bucket**. 10. Click **Next** and then **Add an application**. Review the [Cloudflare Access documentation](/cloudflare-one/applications/configure-apps/self-hosted-apps/) to understand how to configure additional Access application options. @@ -70,7 +70,7 @@ You will need to [connect a custom domain](/r2/buckets/public-buckets/#connect-a Visit the custom domain you connected to your R2 bucket, which should present a Cloudflare Access authentication page with your selected identity provider(s) and/or authentication methods. -For example, if you connected Google and/or GitHub identity providers, you can log in with those providers. If the login is successful and your account is a member of the [Access group](/cloudflare-one/identity/users/groups/#access-groups) you associated with the Access application you created in this guide, you will be able to access (read/download) objects within the R2 bucket. +For example, if you connected Google and/or GitHub identity providers, you can log in with those providers. If the login is successful and your account is a member of the [Access group](/cloudflare-one/identity/users/groups/) you associated with the Access application you created in this guide, you will be able to access (read/download) objects within the R2 bucket. If you cannot authenticate or receive a block page after authenticating, check that you have an [Access policy](/cloudflare-one/applications/configure-apps/self-hosted-apps/#2-add-an-access-policy) configured within your Access application that explicitly allows the group your user account is associated with. diff --git a/src/content/docs/r2/tutorials/upload-logs-event-notifications.mdx b/src/content/docs/r2/tutorials/upload-logs-event-notifications.mdx index 56ddc86bd10f23..b537755019a9c0 100644 --- a/src/content/docs/r2/tutorials/upload-logs-event-notifications.mdx +++ b/src/content/docs/r2/tutorials/upload-logs-event-notifications.mdx @@ -31,7 +31,7 @@ To begin, refer to [Install/Update Wrangler](/workers/wrangler/install-and-updat You will need to create two R2 buckets: -- `example-upload-bucket`: When new objects are uploaded to this bucket, your [consumer Worker](/queues/get-started/#5-create-your-consumer-worker) will write logs. +- `example-upload-bucket`: When new objects are uploaded to this bucket, your [consumer Worker](/queues/get-started/#4-create-your-consumer-worker) will write logs. - `example-log-sink-bucket`: Upload logs from `example-upload-bucket` will be written to this bucket. To create the buckets, run the following Wrangler commands: