finish the rest

Author: HarshCasper

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

@@ -55,9 +55,7 @@ Execute the following command to list the resources:
 awslocal lakeformation list-resources
 ```
 
-The following output is displayed:
-
-```bash
+```bash title="Output"
 {
     "ResourceInfoList": [
         {

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

@@ -123,9 +123,7 @@ awslocal lambda create-function-url-config \
     --auth-type NONE
 ```
 
-The following output would be retrieved:
-
-```json
+```bash title="Output"
 {
     "FunctionUrl": "http://my-custom-subdomain.lambda-url.<region>...",
     ....
@@ -141,9 +139,7 @@ awslocal lambda create-function-url-config \
     --qualifier test-alias
 ```
 
-The following output would be retrieved:
-
-```json
+```bash title="Output"
 {
     "FunctionUrl": "http://my-custom-subdomain-test-alias.lambda-url.<region>...",
     ....
@@ -162,9 +158,7 @@ curl -X POST \
     -d '{"num1": "10", "num2": "10"}'
 ```
 
-The following output would be retrieved:
-
-```sh
+```bash title="Output"
 The product of 10 and 10 is 100% 
 ```
 
@@ -479,7 +473,7 @@ We then used the [`CreateFunction` API](https://docs.aws.amazon.com/lambda/lates
 To test our Lambda function and see the output from the Lambda Layer, we can invoke the function and check the logs (with `DEBUG=1` enabled).
 Here's an example:
 
-```shell
+```bash title="Output"
 > START RequestId: a8bc4ce6-e2e8-189e-cf58-c2eb72827c23 Version: $LATEST
 > Output from Lambda layer util function
 > Debug output from Lambda function
@@ -673,9 +667,7 @@ If you receive a `ResourceConflictException` when trying to invoke a function, i
 awslocal lambda get-function --function-name my-function
 ```
 
-The output will be similar to the following:
-
-```bash
+```bash title="Output"
 An error occurred (ResourceConflictException) when calling the Invoke operation (reached max retries: 0):
 The operation cannot be performed at this time.
 The function is currently in the following state: Pending
@@ -693,9 +685,7 @@ Alternatively, you can check the function state using the [`GetFunction` API](ht
 awslocal lambda get-function --function-name my-function
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
   "Configuration": {
     ...
@@ -714,9 +704,7 @@ When the function is active, the output will be similar to the following:
 awslocal lambda get-function --function-name my-function
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
   "Configuration": {
     ...

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

@@ -67,9 +67,7 @@ awslocal managedblockchain create-network \
         }'
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
     "NetworkId": "n-X24AF1AK2GC6MDW11HYW5I5DQC",
     "MemberId": "m-6VWBWHP2Y15F7TQ2DS093RTCW2"
@@ -107,9 +105,7 @@ awslocal managedblockchain create-node \
     --member-id m-6VWBWHP2Y15F7TQ2DS093RTCW2
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
     "NodeId": "nd-77K8AI0O5BEQD1IW4L8OGKMXV7"
 }
@@ -129,9 +125,7 @@ awslocal managedblockchain create-proposal \
     --member-id m-6VWBWHP2Y15F7TQ2DS093RTCW2
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
     "ProposalId": "p-NK0PSLDPETJQX01Q4OLBRHP8CZ"
 }

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

@@ -31,9 +31,7 @@ Run the following command to create a container and retrieve the the `Endpoint`
 awslocal mediastore create-container --container-name mycontainer
 ```
 
-You should see the following output:
-
-```bash
+```bash title="Output"
 {
     "Container": {
         "Endpoint": "http://mediastore-mycontainer.mediastore.localhost.localstack.cloud:4566",
@@ -59,9 +57,7 @@ awslocal mediastore-data put-object \
     --content-type binary/octet-stream
 ```
 
-You should see the following output:
-
-```bash
+```bash title="Output"
 {
     "ContentSHA256": "",
     "ETag": "\"111d787cdcfcc358fd15684131f586d8\""
@@ -82,9 +78,7 @@ awslocal mediastore-data get-object \
     /tmp/out.txt
 ```
 
-You should see the following output:
-
-```bash
+```bash title="Output"
 {
     "ContentLength": "716",
     "ContentType": "binary/octet-stream",

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

@@ -40,9 +40,7 @@ Run the following command to retrieve the cluster endpoint using the [`DescribeC
 awslocal memorydb describe-clusters --query "Clusters[0].ClusterEndpoint"
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
   "Address": "127.0.0.1",
   "Port": 36739

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

@@ -39,9 +39,7 @@ awslocal mq create-broker \
     --users='{"ConsoleAccess": true, "Groups": ["testgroup"],"Password": "QXwV*$iUM9USHnVv&!^7s3c@", "Username": "admin"}'
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
     "BrokerArn": "arn:aws:mq:us-east-1:000000000000:broker:test-broker:b-f503abb7-66bc-47fb-b1a9-8d8c51ef6545",
     "BrokerId": "b-f503abb7-66bc-47fb-b1a9-8d8c51ef6545"
@@ -54,13 +52,10 @@ You can use the [`DescribeBroker`](https://docs.aws.amazon.com/amazon-mq/latest/
 Run the following command to get information about the broker we created above:
 
 ```bash
-awslocal mq describe-broker --broker-id
+awslocal mq describe-broker --broker-id b-f503abb7-66bc-47fb-b1a9-8d8c51ef6545
 ```
 
-The output will be similar to the following:
-
-```json
-b-f503abb7-66bc-47fb-b1a9-8d8c51ef6545
+```bash title="Output"
 {
     "BrokerArn": "arn:aws:mq:us-east-1:000000000000:broker:test-broker:b-f503abb7-66bc-47fb-b1a9-8d8c51ef6545",
     "BrokerId": "b-f503abb7-66bc-47fb-b1a9-8d8c51ef6545",

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

@@ -30,7 +30,7 @@ To set up a local MSK (Managed Streaming for Apache Kafka) cluster, you can use
 In this process, you'll need a JSON file named `brokernodegroupinfo.json` which specifies the three subnets where you want your local Amazon MSK to distribute the broker nodes.
 Create the file and add the following content to it:
 
-```json
+```bash title="Output"
 {
     "InstanceType": "kafka.m5.xlarge",
     "BrokerAZDistribution": "DEFAULT",
@@ -52,9 +52,7 @@ awslocal kafka create-cluster \
     --number-of-broker-nodes 3
 ```
 
-The output of the command looks similar to this:
-
-```bash
+```bash title="Output"
 {
     "ClusterArn": "arn:aws:kafka:us-east-1:000000000000:cluster/EventsCluster/b154d18a-8ecb-4691-96b2-50348357fc2f-25",
     "ClusterName": "EventsCluster",
@@ -71,9 +69,7 @@ awslocal kafka describe-cluster \
     --cluster-arn "arn:aws:kafka:us-east-1:000000000000:cluster/EventsCluster/b154d18a-8ecb-4691-96b2-50348357fc2f-25"
 ```
 
-The output of the command looks similar to this:
-
-```bash
+```bash title="Output"
 {
     "ClusterInfo": {
         "BrokerNodeGroupInfo": {
@@ -122,9 +118,7 @@ bin/kafka-topics.sh \
     --topic LocalMSKTopic
 ```
 
-After executing the command, your output should resemble the following:
-
-```bash
+```bash title="Output"
 Created topic LocalMSKTopic.
 ```
 
@@ -212,7 +206,7 @@ awslocal lambda create-event-source-mapping \
 
 Upon successful completion of the operation to create the Lambda Event Source Mapping, you can expect the following response:
 
-```bash
+```bash title="Output"
 {
     "UUID": "9c353a2b-bc1a-48b5-95a6-04baf67f01e4",
     "StartingPosition": "LATEST",

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

@@ -51,13 +51,15 @@ The Airflow UI can be accessed via the URL in the `WebserverUrl` attribute of th
 The username and password are always set to `localstack`.
 
 ```bash
-awslocal mwaa get-environment --name my-mwaa-env --query Environment.WebserverUrl
-"http://localhost.localstack.cloud:4510"
+awslocal mwaa get-environment \
+        --name my-mwaa-env \
+        --query Environment.WebserverUrl \
+        "http://localhost.localstack.cloud:4510"
 ```
 
 LocalStack also prints this information in the logs:
 
-```bash
+```bash title="Output" 
 2024-03-06T14:54:47.070  INFO --- [functhread10] l.services.mwaa.provider   : Airflow environment 'my-mwaa-env' available at http://localhost.localstack.cloud:4510 with username 'localstack' and password 'localstack'
 ```
 

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

@@ -58,9 +58,7 @@ awslocal neptune create-db-cluster \
     --db-cluster-identifier my-neptune-db
 ```
 
-You should see the following output:
-
-```json
+```bash title="Output"
 {
     "DBCluster": {
         ...
@@ -194,9 +192,7 @@ Use the Python package [awscurl](https://pypi.org/project/awscurl/) to make your
 awscurl "https://localhost.localstack.cloud:4510/gremlin?gremlin=g.V().count()" -H "Accept: application/json" | jq .
 ```
 
-The output will be similar to the following:
-
-```json
+```bash title="Output"
 {
   "requestId": "729c3e7b-50b3-4df7-b0b6-d1123c4e81df",
   "status": {

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

@@ -76,9 +76,7 @@ You can verify that the cluster is up and running by checking the cluster health
 curl -s http://my-domain.us-east-1.opensearch.localhost.localstack.cloud:4566/_cluster/health | jq .
 ```
 
-The following output will be visible on your terminal:
-
-```json
+```bash title="Output"
 {
   "cluster_name": "opensearch",
   "status": "green",
@@ -173,7 +171,7 @@ IAM support is also not yet available.
 A secure OpenSearch domain can be spawned with this example CLI input.
 Save it in a file named `opensearch_domain.json`.
 
-```json
+```json title="opensearch_domain.json"
 {
     "DomainName": "secure-domain",
     "ClusterConfig": {
@@ -220,9 +218,7 @@ Once the domain setup is complete (`Processing: false`), the cluster can only be
 curl -u 'admin:really-secure-passwordAa!1' http://secure-domain.us-east-1.opensearch.localhost.localstack.cloud:4566/_cluster/health
 ```
 
-The following output will be visible on your terminal:
-
-```json
+```bash title="Output"
 {"cluster_name":"opensearch","status":"green",...}
 ```