finished aws docs

Author: quetzalliwrites

src/content/docs/aws/services/rds.mdx

@@ -329,7 +329,7 @@ The [`aws_s3` extension](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/
 
 In the SQL code snippet below, we are loading the `aws_s3` extension, then use the `table_import_from_s3(..)` function to populate the data in a table `table1` from a CSV file `test.csv` stored in a local S3 bucket `mybucket1`:
 
-```sql
+```sql lineNumbers
 CREATE EXTENSION IF NOT EXISTS aws_s3 CASCADE;
 SELECT aws_s3.table_import_from_s3(
     'table1', 'c1, c2, c3', '(format csv)',
@@ -339,7 +339,7 @@ SELECT aws_s3.table_import_from_s3(
 
 Analogously, we can use the `query_export_to_s3(..)` extension function to export data from a table `table2` into a CSV file `test.csv` in local S3 bucket `mybucket2`:
 
-```sql
+```sql lineNumbers
 CREATE EXTENSION IF NOT EXISTS aws_s3 CASCADE;
 SELECT aws_s3.query_export_to_s3(
     'SELECT * FROM table2',

src/content/docs/aws/services/s3.mdx

@@ -181,7 +181,7 @@ awslocal s3api create-bucket --bucket cors-bucket
 Next, create a JSON file with the CORS configuration.
 The file should have the following format:
 
-```json title="cors-config.json"
+```json title="cors-config.json" lineNumbers
 {
   "CORSRules": [
     {
@@ -217,7 +217,7 @@ Your S3 bucket is configured to allow cross-origin resource sharing, and if you
 However, if you try to access your bucket from [LocalStack Web Application](https://app.localstack.cloud), you'll see errors, and your bucket won't be accessible anymore.
 We can edit the JSON file `cors-config.json` you created earlier with the following configuration and save it:
 
-```json title="cors-config.json"
+```json title="cors-config.json" lineNumbers
 {
   "CORSRules": [
     {
@@ -263,7 +263,7 @@ IMAGE_NAME=localstack/localstack:s3-latest localstack start
 ```
 </TabItem>
 <TabItem label="Docker Compose">
-```yaml
+```yaml lineNumbers
 services:
   localstack:
     container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"

src/content/docs/aws/services/servicediscovery.mdx

@@ -82,7 +82,7 @@ awslocal ecs create-cluster \
 Next, you will register a task definition that's compatible with Fargate.
 Create a file named `fargate-task.json` and add the following content:
 
-```json title="fargate-task.json"
+```json title="fargate-task.json" lineNumbers
 {
     "family": "tutorial-task-def",
         "networkMode": "awsvpc",
@@ -157,7 +157,7 @@ Make a note of the `GroupId` and `SubnetId` values.
 
 Create a new file named `ecs-service-discovery.json` and add the following content to it:
 
-```json title="ecs-service-discovery.json"  
+```json title="ecs-service-discovery.json" lineNumbers
 {
     "cluster": "tutorial",
     "serviceName": "ecs-service-discovery",

src/content/docs/aws/services/sqs.mdx

@@ -408,7 +408,7 @@ curl "http://localhost.localstack.cloud:4566/_aws/sqs/messages?QueueUrl=http://s
 ```
 </TabItem>
 <TabItem label="Python Requests">
-```python
+```python lineNumbers
 import requests
 
 response = requests.get(
@@ -577,7 +577,7 @@ aws --endpoint-url=http://localhost.localstack.cloud:4566/_aws/sqs/messages sqs
 ```
 </TabItem>
 <TabItem label="Boto3">
-```python
+```python lineNumbers
 import boto3
 sqs = boto3.client("sqs", endpoint_url="http://localhost.localstack.cloud:4566/_aws/sqs/messages")
 response = sqs.receive_message(QueueUrl="http://sqs.us-east-1.localhost.localstack.cloud:4566/000000000000/my-queue")
@@ -631,7 +631,7 @@ curl -H "Accept: application/json" \
 ```
 </TabItem>
 <TabItem label="Python Requests">
-```python
+```python lineNumbers
 import requests
 response = requests.get(
     "http://localhost.localstack.cloud:4566/_aws/sqs/messages",

src/content/docs/aws/services/stepfunctions.mdx

@@ -28,7 +28,7 @@ You can create a state machine using the [`CreateStateMachine`](https://docs.aws
 The API requires the name of the state machine, the state machine definition, and the role ARN that the state machine will assume to call AWS services.
 Run the following command to create a state machine:
 
-```bash
+```bash lineNumbers
 awslocal stepfunctions create-state-machine \
     --name "CreateAndListBuckets" \
     --definition '{
@@ -167,7 +167,7 @@ The first step is to select the state machine where mocked responses should be a
 
 In this example, we'll use a state machine named `LambdaSQSIntegration`, defined as follows:
 
-```json title="LambdaSQSIntegration.json"
+```json title="LambdaSQSIntegration.json" lineNumbers
 {
   "Comment": "This state machine is called: LambdaSQSIntegration",
   "QueryLanguage": "JSONata",
@@ -223,7 +223,7 @@ This section specifies the Step Functions state machines to mock, along with the
 
 Each test case maps state names to `ResponseID`s defined in the `MockedResponses` section.
 
-```json
+```json lineNumbers
 "StateMachines": {
   "<StateMachineName>": {
     "TestCases": {
@@ -247,7 +247,7 @@ At runtime, if a test case is selected, the state uses the mocked response (if d
 
 Below is a complete example of the `StateMachines` section:
 
-```json
+```json lineNumbers
 "LambdaSQSIntegration": {
   "TestCases": {
     "LambdaRetryCase": {
@@ -264,7 +264,7 @@ This section defines mocked responses for Task states.
 
 Each `ResponseID` includes one or more step keys and defines either a `Return` value or a `Throw` error.
 
-```json
+```json lineNumbers
 "MockedResponses": {
   "<ResponseID>": {
     "<step-key>": { "Return": ... },
@@ -287,7 +287,7 @@ Each entry must have **either** `Return` or `Throw`, but cannot have both.
 
 Here is a complete example of the `MockedResponses` section:
 
-```json
+```json lineNumbers
 "MockedLambdaStateRetry": {
   "0": {
     "Throw": {
@@ -314,7 +314,7 @@ Here is a complete example of the `MockedResponses` section:
 
 The `MockConfigFile.json` below is used to test the `LambdaSQSIntegration` state machine defined earlier.
 
-```json
+```json lineNumbers
 {
   "StateMachines":{
     "LambdaSQSIntegration":{
@@ -394,7 +394,7 @@ localstack start --volume /path/to/MockConfigFile.json:/tmp/MockConfigFile.json
 ```
 </TabItem>
 <TabItem label="Docker Compose"> 
-```yaml
+```yaml lineNumbers
 services:
   localstack:
     container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"
@@ -452,7 +452,7 @@ awslocal stepfunctions describe-execution \
     --execution-arn "arn:aws:states:us-east-1:000000000000:execution:LambdaSQSIntegration:MockExecutionBaseCase"
 ```
 
-```json
+```json lineNumbers
 {
     "executionArn": "arn:aws:states:us-east-1:000000000000:execution:LambdaSQSIntegration:MockExecutionBaseCase",
     "stateMachineArn": "arn:aws:states:us-east-1:000000000000:stateMachine:LambdaSQSIntegration",

src/content/docs/aws/services/swf.mdx

@@ -82,7 +82,7 @@ awslocal swf list-domains --registration-status DEPRECATED
 You can register a workflow using the [`RegisterWorkflowType`](https://docs.aws.amazon.com/amazonswf/latest/apireference/API_RegisterWorkflowType.html) API.
 Execute the following command to register a workflow named `test-workflow`:
 
-```bash
+```bash lineNumbers
 awslocal swf register-workflow-type \
     --domain test-domain \
     --name test-workflow \
@@ -130,7 +130,7 @@ The following output would be retrieved:
 You can register an activity using the [`RegisterActivityType`](https://docs.aws.amazon.com/amazonswf/latest/apireference/API_RegisterActivityType.html) API.
 Execute the following command to register an activity named `test-activity`:
 
-```bash
+```bash lineNumbers
 awslocal swf register-activity-type \
     --domain test-domain \
     --name test-activity \
@@ -145,7 +145,7 @@ awslocal swf register-activity-type \
 You can use the [`DescribeActivityType`](https://docs.aws.amazon.com/amazonswf/latest/apireference/API_DescribeActivityType.html) API to verify that the activity was registered successfully.
 Run the following command to describe the `test-activity` activity:
 
-```bash
+```bash lineNumbers
 awslocal swf describe-activity-type \
     --domain test-domain \
     --activity-type name=test-activity,version=1.0
@@ -180,7 +180,7 @@ The following output would be retrieved:
 You can start a workflow execution using the [`StartWorkflowExecution`](https://docs.aws.amazon.com/amazonswf/latest/apireference/API_StartWorkflowExecution.html) API.
 Execute the following command to start a workflow execution for the `test-workflow` workflow:
 
-```bash
+```bash lineNumbers
 awslocal swf start-workflow-execution \
     --domain test-domain \
     --workflow-type name=test-workflow,version=1.0 \

src/content/docs/aws/services/transfer.mdx

@@ -17,7 +17,7 @@ Whether you're looking to facilitate file transfers or enhance your data access
 
 This Python code demonstrates a basic workflow for transferring a file between a local machine and AWS S3 using the AWS Transfer Family service and FTP (File Transfer Protocol).
 
-```python
+```python lineNumbers
 import io
 import time
 import uuid

src/content/docs/aws/services/verifiedpermissions.mdx

@@ -55,7 +55,7 @@ To create a Verified Permissions Policy, use the [`CreatePolicy`](https://docs.a
 
 Create a JSON file named `static_policy.json` with the following content:
 
-```json
+```json lineNumbers
 {
     "static": {
         "description":  "Grant the User alice access to view the trip Album",

src/content/docs/aws/services/waf.mdx

@@ -26,7 +26,7 @@ We will walk you through creating, listing, tagging, and viewing tags for Web Ac
 Start by creating a Web Access Control List (WebACL) using the [`CreateWebACL`](https://docs.aws.amazon.com/waf/latest/APIReference/API_CreateWebACL.html) API.
 Run the following command to create a WebACL named `TestWebAcl`:
 
-```bash
+```bash lineNumbers
 awslocal wafv2 create-web-acl \
     --name TestWebAcl \
     --scope REGIONAL \

src/content/docs/aws/services/xray.mdx

@@ -42,7 +42,7 @@ You can generates a unique trace ID and constructs a JSON document with trace in
 It then sends this trace segment to the AWS X-Ray API using the    [PutTraceSegments](https://docs.aws.amazon.com/xray/latest/api/API_PutTraceSegments.html) API.
 Run the following commands in your terminal:
 
-```bash
+```bash lineNumbers
 START_TIME=$(date +%s)
 HEX_TIME=$(printf '%x\n' $START_TIME)
 GUID=$(dd if=/dev/random bs=12 count=1 2>/dev/null | od -An -tx1 | tr -d ' \t\n')
@@ -68,7 +68,7 @@ Sending trace segment to X-Ray API: {"trace_id": "1-6501ee11-056ec85fafff21f648e
 You can now retrieve the trace summaries from the last 10 minutes using the [GetTraceSummaries](https://docs.aws.amazon.com/xray/latest/api/API_GetTraceSummaries.html) API.
 Run the following commands in your terminal:
 
-```bash
+```bash lineNumbers
 EPOCH=$(date +%s)
 awslocal xray get-trace-summaries --start-time $(($EPOCH-600)) --end-time $(($EPOCH))
 {