From e160a94d48d47715c11f625c06b0942816f61e4b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A1szl=C3=B3=20G=C3=96R=C3=96G?= Date: Wed, 27 Mar 2024 19:25:51 +0100 Subject: [PATCH 1/2] Modify endpoints in own server section of AWS S3 --- docs/uploader/aws-s3-multipart.mdx | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/uploader/aws-s3-multipart.mdx b/docs/uploader/aws-s3-multipart.mdx index 8c9f9f28b..62a79e355 100644 --- a/docs/uploader/aws-s3-multipart.mdx +++ b/docs/uploader/aws-s3-multipart.mdx @@ -141,14 +141,16 @@ You will need to do the following things: as AWS Lambdas), inside Next.js as an API route, or wherever your server runs. - `GET` > `/uppy/sts`: get the temporary security credentials (optional). - - `POST` > `/uppy/s3`: get parameters and pre-signed URL for non-multipart + - `POST` > `/uppy/s3/params`: get parameters and pre-signed URL for non-multipart upload. - - `POST` > `/uppy/s3-multipart`: create the multipart upload. - - `GET` > `/uppy/s3-multipart/:id`: get the uploaded parts. - - `GET` > `/uppy/s3-multipart/:id/:partNumber`: sign the part and return a + - `POST` > `/uppy/s3/multipart`: create the multipart upload. + - `GET` > `/uppy/s3/multipart/:id`: get the uploaded parts. + - `GET` > `/uppy/s3/multipart/:id/batch`: sign a batch of parts and return a pre-signed URL. - - `POST` > `/uppy/s3-multipart/:id/complete`: complete the multipart upload. - - `DELETE` > `/uppy/s3-multipart/:id`: abort the multipart upload. + - `GET` > `/uppy/s3/multipart/:id/:partNumber`: sign the part and return a + pre-signed URL. + - `POST` > `/uppy/s3/multipart/:id/complete`: complete the multipart upload. + - `DELETE` > `/uppy/s3/multipart/:id`: abort the multipart upload. 3. [Setup Uppy](https://github.com/transloadit/uppy/blob/main/examples/aws-nodejs/public/index.html). ### Use with Companion From 584bbf3ec94445aad7907132bbd7054b7a60a360 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?L=C3=A1szl=C3=B3=20G=C3=96R=C3=96G?= Date: Fri, 29 Mar 2024 18:34:49 +0100 Subject: [PATCH 2/2] Modify steps in own server section of AWS S3 --- docs/uploader/aws-s3-multipart.mdx | 19 +++---------------- 1 file changed, 3 insertions(+), 16 deletions(-) diff --git a/docs/uploader/aws-s3-multipart.mdx b/docs/uploader/aws-s3-multipart.mdx index 62a79e355..0185e8595 100644 --- a/docs/uploader/aws-s3-multipart.mdx +++ b/docs/uploader/aws-s3-multipart.mdx @@ -136,22 +136,9 @@ bucket in question. In-depth documentation about CORS rules is available on the The recommended approach is to integrate `@uppy/aws-s3` with your own server. You will need to do the following things: -1. [Setup up a S3 bucket](#setting-up-your-s3-bucket). -2. Create endpoints in your server. You can create them as edge functions (such - as AWS Lambdas), inside Next.js as an API route, or wherever your server - runs. - - `GET` > `/uppy/sts`: get the temporary security credentials (optional). - - `POST` > `/uppy/s3/params`: get parameters and pre-signed URL for non-multipart - upload. - - `POST` > `/uppy/s3/multipart`: create the multipart upload. - - `GET` > `/uppy/s3/multipart/:id`: get the uploaded parts. - - `GET` > `/uppy/s3/multipart/:id/batch`: sign a batch of parts and return a - pre-signed URL. - - `GET` > `/uppy/s3/multipart/:id/:partNumber`: sign the part and return a - pre-signed URL. - - `POST` > `/uppy/s3/multipart/:id/complete`: complete the multipart upload. - - `DELETE` > `/uppy/s3/multipart/:id`: abort the multipart upload. -3. [Setup Uppy](https://github.com/transloadit/uppy/blob/main/examples/aws-nodejs/public/index.html). +1. [Setup a S3 bucket](#setting-up-your-s3-bucket). +2. [Setup your server](https://github.com/transloadit/uppy/blob/main/examples/aws-nodejs/index.js) +3. [Setup Uppy client](https://github.com/transloadit/uppy/blob/main/examples/aws-nodejs/public/index.html). ### Use with Companion