last pieces

Author: HarshCasper

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

@@ -1,22 +1,20 @@
 ---
 title: "Data Firehose"
-linkTitle: "Data Firehose"
-description: >
-  Get started with Data Firehose on LocalStack
+description: Get started with Data Firehose on LocalStack
 tags: ["Free"]
 ---
 
-{{< callout >}}
+:::note
 This service was formerly called as 'Kinesis Data Firehose'.
-{{< /callout >}}
+:::
 
 ## Introduction
 
 Data Firehose is a service provided by AWS that allows you to extract, transform and load streaming data into various destinations, such as Amazon S3, Amazon Redshift, and Elasticsearch.
 With Data Firehose, you can ingest and deliver real-time data from different sources as it automates data delivery, handles buffering and compression, and scales according to the data volume.
 
 LocalStack allows you to use the Data Firehose APIs in your local environment to load and transform real-time data.
-The supported APIs are available on our [API coverage page]({{< ref "coverage_firehose" >}}), which provides information on the extent of Data Firehose's integration with LocalStack.
+The supported APIs are available on our [API coverage page](), which provides information on the extent of Data Firehose's integration with LocalStack.
 
 ## Getting started
 
@@ -30,9 +28,9 @@ We will demonstrate how to use Firehose to load Kinesis data into Elasticsearch
 You can create an Elasticsearch domain using the [`create-elasticsearch-domain`](https://docs.aws.amazon.com/cli/latest/reference/es/create-elasticsearch-domain.html) command.
 Execute the following command to create a domain named `es-local`:
 
-{{< command >}}
-$ awslocal es create-elasticsearch-domain --domain-name es-local
-{{< / command >}}
+```bash
+awslocal es create-elasticsearch-domain --domain-name es-local
+```
 
 Save the value of the `Endpoint` field from the response, as it will be required further down to confirm the setup.
 
@@ -43,17 +41,17 @@ Now let us create our target S3 bucket and our source Kinesis stream:
 Before creating the stream, we need to create an S3 bucket to store our backup data.
 You can do this using the [`mb`](https://docs.aws.amazon.com/cli/latest/reference/s3/mb.html) command:
 
-{{< command >}}
-$ awslocal s3 mb s3://kinesis-activity-backup-local
-{{< / command >}}
+```bash
+awslocal s3 mb s3://kinesis-activity-backup-local
+```
 
 You can now use the [`CreateStream`](https://docs.aws.amazon.com/kinesis/latest/APIReference/API_CreateStream.html) API to create a Kinesis stream named `kinesis-es-local-stream` with two shards:
 
-{{< command >}}
-$ awslocal kinesis create-stream \
+```bash
+awslocal kinesis create-stream \
   --stream-name kinesis-es-local-stream \
   --shard-count 2
-{{< / command >}}
+```
 
 ### Create a Firehouse delivery stream
 
@@ -64,20 +62,20 @@ Within the `kinesis-stream-source-configuration`, it is required to specify the
 The `elasticsearch-destination-configuration` sets vital parameters, which includes the access role, `DomainARN` of the Elasticsearch domain where you wish to publish, and the settings including the `IndexName` and `TypeName` for the Elasticsearch setup.
 Additionally to backup all documents to S3, the `S3BackupMode` parameter is set to `AllDocuments`, which is accompanied by `S3Configuration`.
 
-{{< callout >}}
+:::note
 Within LocalStack's default configuration, IAM roles remain unverified and no strict validation is applied on ARNs.
 However, when operating within the AWS environment, you need to check the access rights of the specified role for the task.
-{{< /callout >}}
+:::
 
 You can use the [`CreateDeliveryStream`](https://docs.aws.amazon.com/firehose/latest/APIReference/API_CreateDeliveryStream.html) API to create a Firehose delivery stream named `activity-to-elasticsearch-local`:
 
-{{< command >}}
-$ awslocal firehose create-delivery-stream \
+```bash
+awslocal firehose create-delivery-stream \
   --delivery-stream-name activity-to-elasticsearch-local \
   --delivery-stream-type KinesisStreamAsSource \
   --kinesis-stream-source-configuration "KinesisStreamARN=arn:aws:kinesis:us-east-1:000000000000:stream/kinesis-es-local-stream,RoleARN=arn:aws:iam::000000000000:role/Firehose-Reader-Role" \
   --elasticsearch-destination-configuration "RoleARN=arn:aws:iam::000000000000:role/Firehose-Reader-Role,DomainARN=arn:aws:es:us-east-1:000000000000:domain/es-local,IndexName=activity,TypeName=activity,S3BackupMode=AllDocuments,S3Configuration={RoleARN=arn:aws:iam::000000000000:role/Firehose-Reader-Role,BucketARN=arn:aws:s3:::kinesis-activity-backup-local}"
-{{< / command >}}
+```
 
 On successful execution, the command will return the `DeliveryStreamARN` of the created delivery stream:
 
@@ -93,43 +91,43 @@ Before testing the integration, it's necessary to confirm if the local Elasticse
 You can use the [`describe-elasticsearch-domain`](https://docs.aws.amazon.com/cli/latest/reference/es/describe-elasticsearch-domain.html) command to check the status of the Elasticsearch cluster.
 Run the following command:
 
-{{< command >}}
-$ awslocal es describe-elasticsearch-domain \
+```bash
+awslocal es describe-elasticsearch-domain \
   --domain-name es-local | jq ".DomainStatus.Processing"
-{{< / command >}}
+```
 
 Once the command returns `false`, you can move forward with data ingestion.
 The data can be added to the source Kinesis stream or directly to the Firehose delivery stream.
 
 You can add data to the Kinesis stream using the [`PutRecord`](https://docs.aws.amazon.com/kinesis/latest/APIReference/API_PutRecord.html) API.
 The following command adds a record to the stream:
 
-{{< command >}}
-$ awslocal kinesis put-record \
+```bash
+awslocal kinesis put-record \
   --stream-name kinesis-es-local-stream \
   --data '{ "target": "barry" }' \
   --partition-key partition
-{{< / command >}}
+```
 
-{{< callout "tip" >}}
+:::note
 For users using AWS CLI v2, consider adding `--cli-binary-format raw-in-base64-out` to the command mentioned above.
-{{< /callout >}}
+:::
 
 You can use the [`PutRecord`](https://docs.aws.amazon.com/firehose/latest/APIReference/API_PutRecord.html) API to add data to the Firehose delivery stream.
 The following command adds a record to the stream:
 
-{{< command >}}
-$ awslocal firehose put-record \
+```bash
+awslocal firehose put-record \
   --delivery-stream-name activity-to-elasticsearch-local \
   --record '{ "Data": "eyJ0YXJnZXQiOiAiSGVsbG8gd29ybGQifQ==" }'
-{{< / command >}}
+```
 
 To review the entries in Elasticsearch, you can employ [curl](https://curl.se/) for simplicity.
 Remember to replace the URL with the `Endpoint` field from the initial `create-elasticsearch-domain` operation.
 
-{{< command >}}
-$ curl -s http://es-local.us-east-1.es.localhost.localstack.cloud:443/activity/_search | jq '.hits.hits'
-{{< / command >}}
+```bash
+curl -s http://es-local.us-east-1.es.localhost.localstack.cloud:443/activity/_search | jq '.hits.hits'
+```
 
 You will get an output similar to the following:
 

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

@@ -142,7 +142,7 @@ if __name__ == '__main__':
 
 Amazon Neptune resources with IAM DB authentication enabled require all requests to use AWS Signature Version 4.  
 
-When LocalStack starts with [IAM enforcement enabled]({{< ref "/user-guide/security-testing" >}}), the Neptune database checks user permissions before granting access.
+When LocalStack starts with [IAM enforcement enabled](/aws/capabilities/security-testing/iam-policy-enforcement), the Neptune database checks user permissions before granting access.
  The following Gremlin query actions are available for database engine versions `1.3.2.0` and higher:
 
 ```json
@@ -237,9 +237,7 @@ rm -rf <LocalStack Volume>/lib/tinkerpop
 The LocalStack Web Application provides a Resource Browser for managing Neptune databases and 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 **Neptune** under the **Database** section.
 
-<img src="neptune-resource-browser.png" alt="Neptune Resource Browser" title="Neptune Resource Browser" width="900" />
-<br>
-<br>
+![Neptune Resource Browser](/images/aws/neptune-resource-browser.png)
 
 The Resource Browser allows you to perform the following actions: