[Logs] Adds one click logpush instructions (#20550)

* Adds one click logpsuh instructions

* Apply suggestions from code review

Co-authored-by: marciocloudflare <[email protected]>

* Changes after review.

---------

Co-authored-by: marciocloudflare <[email protected]>

Author: angelampcosta

src/assets/images/logs/logs-r2.png

@@ -8,13 +8,37 @@ sidebar:
 
 import { Render } from "~/components"
 
-Cloudflare Logpush supports pushing logs directly to R2 via the Cloudflare dashboard or via API.
+Cloudflare Logpush supports pushing logs directly to R2. You can do so via the automatic setup (Cloudflare creates an R2 bucket for you), or you can create your own R2 bucket with the custom setup. The automatic setup is ideal for quickly setting up a bucket or for testing purposes. Instead, use the custom setup if you need full control over the configuration.
 
 For more information about R2, refer to the [Cloudflare R2](/r2/) documentation.
 
+## Automatic setup
+
+If you want to use the automatic setup for your logpush job:
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
+
+2. Select the Enterprise account or domain (also known as zone) you want to use with Logpush. Depending on your choice, you have access to [account-scoped datasets](/logs/reference/log-fields/account/) and [zone-scoped datasets](/logs/reference/log-fields/zone/), respectively.
+
+3. Go to **Analytics & Logs** > **Logpush**.
+
+4. Select **Create a Logpush job**.
+
+5. Select **R2 Object Storage - automatic** as destination.
+
+6. Next, select the dataset and the storage region you want to use.
+
+7. To finalize, select **Create Logpush job**.
+
+Your setup should now be complete. If you require full control over the configuration, consider using the custom setup instead.
+
+## Custom setup
+
+Cloudflare Logpush supports pushing logs directly to R2 via the Cloudflare dashboard or via API.
+
 Before getting started:
 
-* Create an R2 bucket and set up R2 API tokens.
+- Create an R2 bucket and set up R2 API tokens.
 
   1. Go to the R2 UI > **Create bucket**.
 
@@ -26,11 +50,11 @@ Before getting started:
 
   5. Copy the Secret Access Key and Access Key ID. You will need these when setting up your Logpush job.
 
-* Ensure that you have the following permissions:
+- Ensure that you have the following permissions:
 
-  * R2 write, Logshare Edit.
+  - R2 write, Logshare Edit.
 
-## Manage via the Cloudflare dashboard
+### Manage via the Cloudflare dashboard
 
 <Render file="enable-logpush-job" />
 
@@ -58,7 +82,7 @@ When you are done entering the destination details, select **Continue**.
 
 10. Select **Submit** once you are done configuring your logpush job.
 
-## Manage via API
+### Manage via API
 
 To create a job, make a `POST` request to the Logpush jobs endpoint with the following fields:
 
@@ -95,3 +119,33 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/jobs \
   "enabled": true
 }'
 ```
+
+## Download logs from R2
+
+Once your logs are stored in R2, you can download them using various methods:
+
+### Dashboard
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
+
+2. Navigate to R2 and select your bucket.
+
+3. From your bucket's page, locate the desired log file.
+
+4. Select on the **...** icon next to the file to download it.
+
+![Log files list](~/assets/images/logs/logs-r2.png)
+
+### AWS CLI
+
+Cloudflare R2 is S3-compatible, so you can use the AWS CLI to interact with it.
+  - Configure the AWS CLI with your R2 credentials.
+  - Use the `aws s3 cp` command to download the log file:
+
+```bash
+aws s3 cp s3://<BUCKET-NAME>/<PATH-TO-LOG-FILE><LOCAL-DESTINATION>`
+```
+
+Replace `<bucket-name>`, `<path-to-log-file>`, and `<local-destination>` with your specific details.
+
+Downloaded files are gzipped so they must be decompressed before you can open them in a text editor.