do a bunch

Author: HarshCasper

src/content/docs/aws/services/redshift.md

@@ -1,6 +1,5 @@
 ---
 title: "Redshift"
-linkTitle: "Redshift"
 description: Get started with Redshift on LocalStack
 tags: ["Free", "Ultimate"]
 ---
@@ -12,12 +11,12 @@ RedShift is fully managed by AWS and serves as a petabyte-scale service which al
 The query results can be saved to an S3 Data Lake while additional analytics can be provided by Athena or SageMaker.
 
 LocalStack allows you to use the RedShift APIs in your local environment to analyze structured and semi-structured data across local data warehouses and data lakes.
-The supported APIs are available on our [API coverage page]({{< ref "coverage_redshift" >}}), which provides information on the extent of RedShift's integration with LocalStack.
+The supported APIs are available on our [API coverage page](), which provides information on the extent of RedShift's integration with LocalStack.
 
-{{< callout "Note" >}}
+:::note
 Users on Free plan can use RedShift APIs in LocalStack for basic mocking and testing.
 For advanced features like Redshift Data API and other emulation capabilities, please refer to the Ultimate plan.
-{{< /callout >}}
+:::
 
 ## Getting started
 
@@ -51,108 +50,106 @@ You will also create a Glue database, connection, and crawler to populate the Gl
 You can create a RedShift cluster using the [`CreateCluster`](https://docs.aws.amazon.com/redshift/latest/APIReference/API_CreateCluster.html) API.
 The following command will create a RedShift cluster with the variables defined above:
 
-{{< command >}}
-$ awslocal redshift create-cluster \
+```bash
+awslocal redshift create-cluster \
       --cluster-identifier $REDSHIFT_CLUSTER_IDENTIFIER \
       --db-name $REDSHIFT_DATABASE_NAME \
       --master-username $REDSHIFT_USERNAME \
       --master-user-password $REDSHIFT_PASSWORD \
       --node-type n1
-{{< / command >}}
+```
 
 You can fetch the status of the cluster using the [`DescribeClusters`](https://docs.aws.amazon.com/redshift/latest/APIReference/API_DescribeClusters.html) API.
 Run the following command to extract the URL of the cluster:
 
-{{< command >}}
-$ REDSHIFT_URL=$(awslocal redshift describe-clusters \
+```bash
+REDSHIFT_URL=$(awslocal redshift describe-clusters \
       --cluster-identifier $REDSHIFT_CLUSTER_IDENTIFIER | jq -r '(.Clusters[0].Endpoint.Address) + ":" + (.Clusters[0].Endpoint.Port|tostring)')
-{{< / command >}}
+```
 
 ### Create a Glue database, connection, and crawler
 
 You can create a Glue database using the [`CreateDatabase`](https://docs.aws.amazon.com/glue/latest/webapi/API_CreateDatabase.html) API.
 The following command will create a Glue database:
 
-{{< command >}}
-$ awslocal glue create-database \
+```bash
+awslocal glue create-database \
       --database-input "{\"Name\": \"$GLUE_DATABASE_NAME\"}"
-{{< / command >}}
+```
 
 You can create a connection to the RedShift cluster using the [`CreateConnection`](https://docs.aws.amazon.com/glue/latest/webapi/API_CreateConnection.html) API.
 The following command will create a Glue connection with the RedShift cluster:
 
-{{< command >}}
-$ awslocal glue create-connection \
+```bash
+awslocal glue create-connection \
       --connection-input "{\"Name\":\"$GLUE_CONNECTION_NAME\", \"ConnectionType\": \"JDBC\", \"ConnectionProperties\": {\"USERNAME\": \"$REDSHIFT_USERNAME\", \"PASSWORD\": \"$REDSHIFT_PASSWORD\", \"JDBC_CONNECTION_URL\": \"jdbc:redshift://$REDSHIFT_URL/$REDSHIFT_DATABASE_NAME\"}}"
-{{< / command >}}
+```
 
 Finally, you can create a Glue crawler using the [`CreateCrawler`](https://docs.aws.amazon.com/glue/latest/webapi/API_CreateCrawler.html) API.
 The following command will create a Glue crawler:
 
-{{< command >}}
-$ awslocal glue create-crawler \
+```bash
+awslocal glue create-crawler \
       --name $GLUE_CRAWLER_NAME \
       --database-name $GLUE_DATABASE_NAME \
       --targets "{\"JdbcTargets\": [{\"ConnectionName\": \"$GLUE_CONNECTION_NAME\", \"Path\": \"$REDSHIFT_DATABASE_NAME/%/$REDSHIFT_TABLE_NAME\"}]}" \
       --role r1
-{{< / command >}}
+```
 
 ### Create table in RedShift
 
 You can create a table in RedShift using the [`CreateTable`](https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_TABLE_NEW.html) API.
 The following command will create a table in RedShift:
 
-{{< command >}}
-$ REDSHIFT_STATEMENT_ID=$(awslocal redshift-data execute-statement \
+```bash
+REDSHIFT_STATEMENT_ID=$(awslocal redshift-data execute-statement \
       --cluster-identifier $REDSHIFT_CLUSTER_IDENTIFIER \
       --database $REDSHIFT_DATABASE_NAME \
       --sql \
   "create table $REDSHIFT_TABLE_NAME(salesid integer not null, listid integer not null, sellerid integer not null, buyerid integer not null, eventid integer not null, dateid smallint not null, qtysold smallint not null, pricepaid decimal(8,2), commission decimal(8,2), saletime timestamp)" | jq -r .Id)
-{{< / command >}}
+```
 
 You can check the status of the statement using the [`DescribeStatement`](https://docs.aws.amazon.com/redshift-data/latest/APIReference/API_DescribeStatement.html) API.
 The following command will check the status of the statement:
 
-{{< command >}}
-$ wait "awslocal redshift-data describe-statement \
+```bash
+wait "awslocal redshift-data describe-statement \
       --id $REDSHIFT_STATEMENT_ID" ".Status" "FINISHED"
-{{< / command >}}
+```
 
 ### Run the crawler
 
 You can run the crawler using the [`StartCrawler`](https://docs.aws.amazon.com/glue/latest/webapi/API_StartCrawler.html) API.
 The following command will run the crawler:
 
-{{< command >}}
-$ awslocal glue start-crawler \
+```bash
+awslocal glue start-crawler \
       --name $GLUE_CRAWLER_NAME
-{{< / command >}}
+```
 
 You can wait for the crawler to finish using the [`GetCrawler`](https://docs.aws.amazon.com/glue/latest/webapi/API_GetCrawler.html) API.
 The following command will wait for the crawler to finish:
 
-{{< command >}}
-$ wait "awslocal glue get-crawler \
+```bash
+wait "awslocal glue get-crawler \
       --name $GLUE_CRAWLER_NAME" ".Crawler.State" "READY"
-{{< / command >}}
+```
 
 You can finally retrieve the schema of the table using the [`GetTable`](https://docs.aws.amazon.com/glue/latest/webapi/API_GetTable.html) API.
 The following command will retrieve the schema of the table:
 
-{{< command >}}
-$ awslocal glue get-table \
+```bash
+awslocal glue get-table \
       --database-name $GLUE_DATABASE_NAME \
       --name "${REDSHIFT_DATABASE_NAME}_${REDSHIFT_SCHEMA_NAME}_${REDSHIFT_TABLE_NAME}"
-{{< / command >}}
+```
 
 ## Resource Browser
 
 The LocalStack Web Application provides a Resource Browser for managing RedShift clusters.
 You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the **Resources** section, and then clicking on **RedShift** under the **Analytics** section.
 
-<img src="redshift-resource-browser.png" alt="RedShift Resource Browser" title="RedShift Resource Browser" width="900" />
-<br>
-<br>
+![RedShift Resource Browser](/images/aws/redshift-resource-browser.png)
 
 The Resource Browser allows you to perform the following actions:
 

src/content/docs/aws/services/resourcegroups.md

@@ -1,6 +1,5 @@
 ---
 title: "Resource Groups"
-linkTitle: "Resource Groups"
 tags: ["Free"]
 description: >
   Get started with Resource Groups on LocalStack
@@ -14,7 +13,7 @@ Resource Groups in AWS provide two types of queries that developers can use to b
 With Tag-based queries, developers can organize resources based on common attributes or characteristics, while CloudFormation stack-based queries allow developers to group resources that are deployed together as part of a CloudFormation stack.
 
 LocalStack allows you to use the Resource Groups APIs in your local environment to group and categorize resources based on criteria such as tags, resource types, regions, or custom attributes.
-The supported APIs are available on our [API coverage page]({{< ref "coverage_resource-groups" >}}), which provides information on the extent of Resource Group's integration with LocalStack.
+The supported APIs are available on our [API coverage page](), which provides information on the extent of Resource Group's integration with LocalStack.
 
 ## Getting Started
 
@@ -34,11 +33,11 @@ A tag-based group is created based on a query of type `TAG_FILTERS_1_0`.
 Use the [`CreateGroup`](https://docs.aws.amazon.com/resource-groups/latest/APIReference/API_CreateGroup.html) API to create a Resource Group.
 Run the following command to create a Resource Group named `my-resource-group`:
 
-{{< command >}}
-$ awslocal resource-groups create-group \
+```bash
+awslocal resource-groups create-group \
     --name my-resource-group \
     --resource-query '{"Type":"TAG_FILTERS_1_0","Query":"{\"ResourceTypeFilters\":[\"AWS::EC2::Instance\"],\"TagFilters\":[{\"Key\":\"Stage\",\"Values\":[\"Test\"]}]}"}'
-{{< /command >}}
+```
 
 You can also specify `AWS::AllSupported` as the `ResourceTypeFilters` value to include all supported resource types in the group.
 
@@ -47,27 +46,27 @@ You can also specify `AWS::AllSupported` as the `ResourceTypeFilters` value to i
 To update a Resource Group, use the [`UpdateGroup`](https://docs.aws.amazon.com/resource-groups/latest/APIReference/API_UpdateGroup.html) API.
 Execute the following command to update the Resource Group `my-resource-group`:
 
-{{< command >}}
+```bash
 awslocal resource-groups update-group \
     --group-name my-resource-group \
     --description "EC2 S3 buckets and RDS DBs that we are using for the test stage"
-{{< /command >}}
+```
 
 Furthermore, you can also update the query and tags associated with a Resource Group using the [`UpdateGroup`](https://docs.aws.amazon.com/resource-groups/latest/APIReference/API_UpdateGroup.html) API.
 Run the following command to update the query and tags of the Resource Group `my-resource-group`:
 
-{{< command >}}
+```bash
 awslocal resource-groups update-group-query \
     --group-name my-resource-group \
     --resource-query '{"Type":"TAG_FILTERS_1_0","Query":"{\"ResourceTypeFilters\":[\"AWS::EC2::Instance\",\"AWS::S3::Bucket\",\"AWS::RDS::DBInstance\"],\"TagFilters\":[{\"Key\":\"Stage\",\"Values\":[\"Test\"]}]}"}'
-{{< /command >}}
+```
 
 ### Delete a Resource Group
 
 To delete a Resource Group, use the [`DeleteGroup`](https://docs.aws.amazon.com/resource-groups/latest/APIReference/API_DeleteGroup.html) API.
 Run the following command to delete the Resource Group `my-resource-group`:
 
-{{< command >}}
-$ awslocal resource-groups delete-group \
+```bash
+awslocal resource-groups delete-group \
     --group-name my-resource-group
-{{< /command >}}
+```

src/content/docs/aws/services/route53.md

@@ -1,6 +1,5 @@
 ---
 title: "Route 53"
-linkTitle: "Route 53"
 description: Get started with Route 53 on LocalStack
 persistence: supported
 tags: ["Free"]
@@ -14,14 +13,14 @@ In addition to basic DNS functionality, Route 53 offers advanced features like h
 Route 53 integrates seamlessly with other AWS services, such as route traffic to CloudFront distributions, S3 buckets configured for static website hosting, EC2 instances, and more.
 
 LocalStack allows you to use the Route53 APIs in your local environment to create hosted zones and to manage DNS entries.
-The supported APIs are available on our [API coverage page]({{< ref "coverage_route53" >}}), which provides information on the extent of Route53's integration with LocalStack.
+The supported APIs are available on our [API coverage page](), which provides information on the extent of Route53's integration with LocalStack.
 LocalStack also integrates with its DNS server to respond to DNS queries with these domains.
 
-{{< callout "note">}}
+:::note
 LocalStack CLI does not publish port `53` anymore by default.
 Use the CLI flag `--host-dns` to expose the port on the host.
 This would be required if you want to reach out to Route53 domain names from your host machine, using the LocalStack DNS server.
-{{< /callout >}}
+:::
 
 ## Getting started
 
@@ -35,12 +34,12 @@ We will demonstrate how to create a hosted zone and query the DNS record with th
 You can created a hosted zone for `example.com` using the [`CreateHostedZone`](https://docs.aws.amazon.com/Route53/latest/APIReference/API_CreateHostedZone.html) API.
 Run the following command:
 
-{{< command >}}
-$ zone_id=$(awslocal route53 create-hosted-zone \
+```bash
+zone_id=$(awslocal route53 create-hosted-zone \
     --name example.com \
     --caller-reference r1 | jq -r '.HostedZone.Id')
-$ echo $zone_id
-{{< / command >}}
+echo $zone_id
+```
 
 The following output would be retrieved:
 
@@ -53,11 +52,11 @@ The following output would be retrieved:
 You can now change the resource record sets for the hosted zone `example.com` using the [`ChangeResourceRecordSets`](https://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html) API.
 Run the following command:
 
-{{< command >}}
-$ awslocal route53 change-resource-record-sets \
+```bash
+awslocal route53 change-resource-record-sets \
     --hosted-zone-id $zone_id \
     --change-batch 'Changes=[{Action=CREATE,ResourceRecordSet={Name=test.example.com,Type=A,ResourceRecords=[{Value=1.2.3.4}]}}]'
-{{< / command >}}
+```
 
 The following output would be retrieved:
 
@@ -73,19 +72,19 @@ The following output would be retrieved:
 
 ## DNS resolution
 
-LocalStack Pro supports the ability to respond to DNS queries for your Route53 domain names, with our [integrated DNS server]({{< ref "user-guide/tools/dns-server" >}}).
+LocalStack Pro supports the ability to respond to DNS queries for your Route53 domain names, with our [integrated DNS server](/aws/tooling/dns-server).
 
-{{< callout >}}
-To follow the example below you must [configure your system DNS to use the LocalStack DNS server]({{< ref "user-guide/tools/dns-server#system-dns-configuration" >}}).
-{{< /callout >}}
+:::note
+To follow the example below you must [configure your system DNS to use the LocalStack DNS server](/aws/tooling/dns-server#system-dns-configuration).
+:::
 
 ### Query a DNS record
 
 You can query the DNS record using `dig` via the built-in DNS server by running the following command:
 
-{{< command >}}
-$ dig @localhost test.example.com
-{{< / command >}}
+```bash
+dig @localhost test.example.com
+```
 
 The following output would be retrieved:
 
@@ -101,7 +100,7 @@ test.example.com.       300     IN      A       1.2.3.4
 
 The DNS name `localhost.localstack.cloud`, along with its subdomains like `mybucket.s3.localhost.localstack.cloud`, serves an internal routing purpose within LocalStack.
 It facilitates communication between a LocalStack compute environment (such as a Lambda function) and the LocalStack APIs, as well as your containerised applications with the LocalStack APIs.
-For example configurations, see the [Network Troubleshooting guide]({{< ref "references/network-troubleshooting/endpoint-url/#from-your-container" >}}).
+For example configurations, see the [Network Troubleshooting guide]().
 
 For most use-cases, the default configuration of the internal LocalStack DNS name requires no modification.
 It functions seamlessly in typical scenarios.
@@ -115,12 +114,12 @@ This can be accomplished using Route53.
 Create a hosted zone for the domain `localhost.localstack.cloud` using the [`CreateHostedZone` API](https://docs.aws.amazon.com/Route53/latest/APIReference/API_CreateHostedZone.html) API.
 Run the following command:
 
-{{< command >}}
-$ zone_id=$(awslocal route53 create-hosted-zone \
+```bash
+zone_id=$(awslocal route53 create-hosted-zone \
     --name localhost.localstack.cloud \
     --caller-reference r1 | jq -r .HostedZone.Id)
-$ echo $zone_id
-{{< / command >}}
+echo $zone_id
+```
 
 The following output would be retrieved:
 
@@ -131,11 +130,11 @@ The following output would be retrieved:
 You can now use the [`ChangeResourceRecordSets`](https://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html) API to create a record set for the domain `localhost.localstack.cloud` using the `zone_id` retrieved in the previous step.
 Run the following command to accomplish this:
 
-{{< command >}}
-$ awslocal route53 change-resource-record-sets \
+```bash
+awslocal route53 change-resource-record-sets \
     --hosted-zone-id $zone_id \
     --change-batch '{"Changes":[{"Action":"CREATE","ResourceRecordSet":{"Name":"localhost.localstack.cloud","Type":"A","ResourceRecords":[{"Value":"5.6.7.8"}]}},{"Action":"CREATE","ResourceRecordSet":{"Name":"*.localhost.localstack.cloud","Type":"A","ResourceRecords":[{"Value":"5.6.7.8"}]}}]}'
-{{< / command >}}
+```
 
 The following output would be retrieved:
 
@@ -151,10 +150,10 @@ The following output would be retrieved:
 
 You can now verify that the DNS name `localhost.localstack.cloud` and its subdomains resolve to the IP address:
 
-{{< command >}}
-$ dig @127.0.0.1 bucket1.s3.localhost.localstack.cloud
-$ dig @127.0.0.1 localhost.localstack.cloud
-{{< / command >}}
+```bash
+dig @127.0.0.1 bucket1.s3.localhost.localstack.cloud
+dig @127.0.0.1 localhost.localstack.cloud
+```
 
 The following output would be retrieved:
 
@@ -176,7 +175,7 @@ localhost.localstack.cloud. 300 IN      A       5.6.7.8
 The LocalStack Web Application provides a Route53 for creating hosted zones and to manage DNS entries.
 You can access the Resource Browser by opening the LocalStack Web Application in your browser, navigating to the **Resources** section, and then clicking on **Route53** under the **Analytics** section.
 
-<img src="route53-resource-browser.png" alt="Route53 Resource Browser" title="Route53 Resource Browser" width="900" />
+![Route53 Resource Browser](/images/aws/route53-resource-browser.png)
 
 The Resource Browser allows you to perform the following actions: