revamp s3 docs

Author: HarshCasper

src/content/docs/aws/services/s3.md src/content/docs/aws/services/s3.mdxsrc/content/docs/aws/services/s3.md renamed to src/content/docs/aws/services/s3.mdx

@@ -1,6 +1,5 @@
 ---
 title: "Simple Storage Service (S3)"
-linkTitle: "Simple Storage Service (S3)"
 description: Get started with Amazon S3 on LocalStack
 persistence: supported
 tags: ["Free"]
@@ -14,30 +13,30 @@ Each object or file within S3 encompasses essential attributes such as a unique
 S3 can store unlimited objects, allowing you to store, retrieve, and manage your data in a highly adaptable and reliable manner.
 
 LocalStack allows you to use the S3 APIs in your local environment to create new buckets, manage your S3 objects, and test your S3 configurations locally.
-The supported APIs are available on our [API coverage page]({{< ref "coverage_s3" >}}), which provides information on the extent of S3's integration with LocalStack.
+The supported APIs are available on our [API coverage page](), which provides information on the extent of S3's integration with LocalStack.
 
 ## Getting started
 
 This guide is designed for users new to S3 and assumes basic knowledge of the AWS CLI and our [`awslocal`](https://github.com/localstack/awscli-local) wrapper script.
 
-Start your LocalStack container using your [preferred method]({{< ref "getting-started/installation" >}}).
+Start your LocalStack container using your preferred method.
 We will demonstrate how you can create an S3 bucket, manage S3 objects, and generate pre-signed URLs for S3 objects.
 
 ### Create an S3 bucket
 
 You can create an S3 bucket using the [`CreateBucket`](https://docs.aws.amazon.com/cli/latest/reference/s3api/create-bucket.html) API.
 Run the following command to create an S3 bucket named `sample-bucket`:
 
-{{< command >}}
-$ awslocal s3api create-bucket --bucket sample-bucket
-{{< / command >}}
+```bash
+awslocal s3api create-bucket --bucket sample-bucket
+```
 
 You can list your S3 buckets using the [`ListBuckets`](https://docs.aws.amazon.com/cli/latest/reference/s3api/list-buckets.html) API.
 Run the following command to list your S3 buckets:
 
-{{< command >}}
-$ awslocal s3api list-buckets
-{{< / command >}}
+```bash
+awslocal s3api list-buckets
+```
 
 On successful creation of the S3 bucket, you will see the following output:
 
@@ -62,20 +61,20 @@ To upload a file to your S3 bucket, you can use the [`PutObject`](https://docs.a
 Download a random image from the internet and save it as `image.jpg`.
 Run the following command to upload the file to your S3 bucket:
 
-{{< command >}}
-$ awslocal s3api put-object \
+```bash
+awslocal s3api put-object \
   --bucket sample-bucket \
   --key image.jpg \
   --body image.jpg
-{{< / command >}}
+```
 
 You can list the objects in your S3 bucket using the [`ListObjects`](https://docs.aws.amazon.com/cli/latest/reference/s3api/list-objects.html) API.
 Run the following command to list the objects in your S3 bucket:
 
-{{< command >}}
-$ awslocal s3api list-objects \
+```bash
+awslocal s3api list-objects \
   --bucket sample-bucket
-{{< / command >}}
+```
 
 If your image has been uploaded successfully, you will see the following output:
 
@@ -99,14 +98,17 @@ If your image has been uploaded successfully, you will see the following output:
 
 Run the following command to upload a file named `index.html` to your S3 bucket:
 
-{{< command >}}
+```bash
+awslocal s3api put-object --bucket sample-bucket --key index.html --body index.html
+```
 
-$ awslocal s3api put-object --bucket sample-bucket --key index.html --body index.html
+The following output would be retrieved:
 
+```bash
 {
     "ETag": "\"d41d8cd98f00b204e9800998ecf8427e\""
 }
-{{< / command >}}
+```
 
 ### Generate a pre-signed URL for S3 object
 
@@ -115,9 +117,9 @@ Pre-signed URL allows anyone to retrieve the S3 object with an HTTP GET request.
 
 Run the following command to generate a pre-signed URL for your S3 object:
 
-{{< command >}}
-$ awslocal s3 presign s3://sample-bucket/image.jpg
-{{< / command >}}
+```bash
+awslocal s3 presign s3://sample-bucket/image.jpg
+```
 
 You will see a generated pre-signed URL for your S3 object.
 You can use [curl](https://curl.se/) or [`wget`](https://www.gnu.org/software/wget/) to retrieve the S3 object using the pre-signed URL.
@@ -143,13 +145,13 @@ By default, most SDKs will try to use **Virtual-Hosted style** requests and prep
 However, if the endpoint is not prefixed by `s3.`, LocalStack will not be able to understand the request and it will most likely result in an error.
 
 You can either change the endpoint to an S3-specific one, or configure your SDK to use **Path style** requests instead.
-Check out our [SDK documentation]({{< ref "sdks" >}}) to learn how you can configure AWS SDKs to access LocalStack and S3.
+Check out our [SDK documentation](/aws/integrations/aws-sdks) to learn how you can configure AWS SDKs to access LocalStack and S3.
 
-{{< callout "tip" >}}
+:::note
 While using [AWS SDKs](https://aws.amazon.com/developer/tools/#SDKs), you would need to configure the `ForcePathStyle` parameter to `true` in the S3 client configuration to use **Path style** requests.
 If you want to use virtual host addressing of buckets, you can remove `ForcePathStyle` from the configuration.
-The `ForcePathStyle` parameter name can vary between SDK and languages, please check our [SDK documentation]({{< ref "sdks" >}})
-{{< /callout >}}
+The `ForcePathStyle` parameter name can vary between SDK and languages, please check our [SDK documentation](/aws/integrations/aws-sdks)
+:::
 
 If your endpoint is not prefixed with `s3.`, all requests are treated as **Path style** requests.
 Using the `s3.localhost.localstack.cloud` endpoint URL is recommended for all requests aimed at S3.
@@ -168,12 +170,17 @@ Follow this step-by-step guide to configure CORS rules on your S3 bucket.
 
 Run the following command on your terminal to create your S3 bucket:
 
-{{< command >}}
-$ awslocal s3api create-bucket --bucket cors-bucket
+```bash
+awslocal s3api create-bucket --bucket cors-bucket
+```
+
+The following output would be retrieved:
+
+```bash
 {
     "Location": "/cors-bucket"
 }
-{{< / command >}}
+```
 
 Next, create a JSON file with the CORS configuration.
 The file should have the following format:
@@ -191,22 +198,22 @@ The file should have the following format:
 }
 ```
 
-{{< callout >}}
+:::note
 Note that this configuration is a sample, and you can tailor it to fit your needs better, for example, restricting the **AllowedHeaders** to specific ones.
-{{< /callout >}}
+:::
 
 Save the file locally with a name of your choice, for example, `cors-config.json`.
 Run the following command to apply the CORS configuration to your S3 bucket:
 
-{{< command >}}
-$ awslocal s3api put-bucket-cors --bucket cors-bucket --cors-configuration file://cors-config.json
-{{< / command >}}
+```bash
+awslocal s3api put-bucket-cors --bucket cors-bucket --cors-configuration file://cors-config.json
+```
 
 You can further verify that the CORS configuration was applied successfully by running the following command:
 
-{{< command >}}
-$ awslocal s3api get-bucket-cors --bucket cors-bucket
-{{< / command >}}
+```bash
+awslocal s3api get-bucket-cors --bucket cors-bucket
+```
 
 On applying the configuration successfully, you should see the same JSON configuration file you created earlier.
 Your S3 bucket is configured to allow cross-origin resource sharing, and if you try to send requests from your local application running on [localhost:3000](http://localhost:3000), they should be successful.
@@ -233,10 +240,10 @@ We can edit the JSON file `cors-config.json` you created earlier with the follow
 
 You can now run the same steps as before to update the CORS configuration and verify if it is applied correctly:
 
-{{< command >}}
-$ awslocal s3api put-bucket-cors --bucket cors-bucket --cors-configuration file://cors-config.json
-$ awslocal s3api get-bucket-cors --bucket cors-bucket
-{{< / command >}}
+```bash
+awslocal s3api put-bucket-cors --bucket cors-bucket --cors-configuration file://cors-config.json
+awslocal s3api get-bucket-cors --bucket cors-bucket
+```
 
 You can try again to upload files in your bucket from the [LocalStack Web Application](https://app.localstack.cloud) and it should work.
 
@@ -245,17 +252,22 @@ You can try again to upload files in your bucket from the [LocalStack Web Applic
 LocalStack provides a Docker image for S3, which you can use to run S3 in a Docker container.
 The image is available on [Docker Hub](https://hub.docker.com/r/localstack/localstack) and can be pulled using the following command:
 
-{{< command >}}
-$ docker pull localstack/localstack:s3-latest
-{{< / command >}}
+```bash
+docker pull localstack/localstack:s3-latest
+```
 
 The S3 Docker image only supports the S3 APIs and does not include other services like Lambda, DynamoDB, etc. You can run the S3 Docker image using any of the following commands:
 
-{{< tabpane lang="shell" >}}
-{{< tab header="LocalStack CLI" lang="shell" >}}
+import { Tabs, TabItem } from '@astrojs/starlight/components';
+
+<Tabs>
+<TabItem label="LocalStack CLI">
+```bash
 IMAGE_NAME=localstack/localstack:s3-latest localstack start
-{{< /tab >}}
-{{< tab header="Docker Compose" lang="yml" >}}
+```
+</TabItem>
+<TabItem label="Docker Compose">
+```yaml
 services:
   localstack:
     container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"
@@ -267,22 +279,25 @@ services:
     volumes:
       - "${LOCALSTACK_VOLUME_DIR:-./volume}:/var/lib/localstack"
       - "/var/run/docker.sock:/var/run/docker.sock"
-{{< /tab >}}
-{{< tab header="Docker" lang="shell" >}}
+```
+</TabItem>
+<TabItem label="Docker">
+```bash
 docker run \
   --rm \
   -p 4566:4566 \
   localstack/localstack:s3-latest
-{{< /tab >}}
-{{< /tabpane >}}
+```
+</TabItem>
+</Tabs>
 
 The S3 Docker image has similar parity with the S3 APIs supported by LocalStack Docker image.
-You can use similar [configuration options]({{< ref "configuration/#s3" >}}) to alter the behaviour of the S3 Docker image, such as `DEBUG` or `S3_SKIP_SIGNATURE_VALIDATION`.
+You can use similar [configuration options](/aws/capabilities/config/configuration/#s3) to alter the behaviour of the S3 Docker image, such as `DEBUG` or `S3_SKIP_SIGNATURE_VALIDATION`.
 
-{{< callout >}}
+:::note
 The S3 Docker image does not support persistence, and all data is lost when the container is stopped.
 To use persistence or save the container state as a Cloud Pod, you need to use the [`localstack/localstack-pro`](https://hub.docker.com/r/localstack/localstack-pro) image.
-{{< /callout >}}
+:::
 
 ## SSE-C Encryption
 
@@ -303,10 +318,10 @@ However, LocalStack does not support the actual encryption and decryption of obj
 
 ## Resource Browser
 
-The LocalStack Web Application provides a [Resource Browser]({{< ref "resource-browser" >}}) for managing S3 buckets & configurations.
+The LocalStack Web Application provides a [Resource Browser](/aws/capabilities/web-app/resource-browser) for managing S3 buckets & configurations.
 You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the **Resources** section, and then clicking on **S3** under the **Storage** section.
 
-<img src="s3-resource-browser.png" alt="S3 Resource Browser" title="S3 Resource Browser" width="900" />
+![S3 Resource Browser](/images/aws/s3-resource-browser.png)
 
 The Resource Browser allows you to perform the following actions:
 
@@ -324,4 +339,4 @@ The following code snippets and sample applications provide practical examples o
 - [Serverless Transcription application using Transcribe, S3, Lambda, SQS, and SES](https://github.com/localstack/sample-transcribe-app)
 - [Query data in S3 Bucket with Amazon Athena, Glue Catalog & CloudFormation](https://github.com/localstack/query-data-s3-athena-glue-sample)
 - [Serverless Image Resizer with Lambda, S3, SNS, and SES](https://github.com/localstack/serverless-image-resizer)
-- [Host a static website locally using Simple Storage Service (S3) and Terraform with LocalStack]({{< ref "s3-static-website-terraform" >}})
+- [Host a static website locally using Simple Storage Service (S3) and Terraform with LocalStack]()