do another bunch

Author: HarshCasper

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

@@ -64,9 +64,7 @@ You can run the following command to verify that the image was built successfull
 docker images
 ```
 
-You will see output similar to the following:
-
-```bash
+```bash title="Output"
 REPOSITORY                TAG       IMAGE ID       CREATED          SIZE  
 ..
 localstack-ecr-image      latest    38883941b8fa   1 minute ago     185MB
@@ -84,9 +82,7 @@ awslocal ecr create-repository \
     --image-scanning-configuration scanOnPush=true
 ```
 
-You will see an output similar to the following:
-
-```bash
+```bash title="Output"
 {
     "repository": {
         "repositoryArn": "arn:aws:ecr:us-east-1:000000000000:repository/localstack-ecr-repository",
@@ -129,9 +125,7 @@ You can run the following command to verify that the image was pushed successful
 awslocal ecr list-images --repository-name localstack-ecr-repository
 ```
 
-You will see an output similar to the following:
-
-```bash
+```bash title="Output"
 {
     "imageIds": [
         {

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

@@ -36,9 +36,7 @@ Execute the following command to create an ECS cluster named `mycluster`:
 awslocal ecs create-cluster --cluster-name mycluster
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "cluster": {
         "clusterArn": "arn:aws:ecs:us-east-1:000000000000:cluster/mycluster",
@@ -98,9 +96,7 @@ and then run the following command:
 awslocal ecs register-task-definition --cli-input-json file://task_definition.json
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "taskDefinition": {
         "taskDefinitionArn": "arn:aws:ecs:us-east-1:000000000000:task-definition/myfamily:1",
@@ -160,9 +156,7 @@ To create a service, execute the following command:
 awslocal ecs create-service --service-name myservice --cluster mycluster --task-definition myfamily --desired-count 1
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "service": {
         "serviceArn": "arn:aws:ecs:us-east-1:000000000000:service/mycluster/myservice",
@@ -226,10 +220,7 @@ To access the generated logs from the container, run the following command:
 awslocal logs filter-log-events --log-group-name myloggroup --query 'events[].message'
 ```
 
-The output will be:
-
-```json
-$ awslocal logs filter-log-events --log-group-name myloggroup | head -n 20
+```bash title="Output"
 {
     "events": [
         {

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

@@ -35,9 +35,7 @@ awslocal efs create-file-system \
     --tags Key=Name,Value=my-file-system
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "CreationToken": "53465731-0032-4cef-92f5-8aefe7c7b91e",
     "FileSystemId": "fs-34feac549e66b814",
@@ -98,9 +96,7 @@ awslocal efs put-lifecycle-configuration \
     --lifecycle-policies "{\"TransitionToIA\":\"AFTER_30_DAYS\"}"
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "LifecyclePolicies": [
         {

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

@@ -39,9 +39,7 @@ awslocal eks create-cluster \
   --resources-vpc-config "{}"
 ```
 
-You can see an output similar to the following:
-
-```bash
+```bash title="Output"
 {
     "cluster": {
         "name": "cluster1",
@@ -71,9 +69,7 @@ You can use the `docker` CLI to check that some containers have been created:
 docker ps
 ```
 
-The output will be:
-
-```bash
+```bash title="Output"
 CONTAINER ID   IMAGE                          COMMAND                  CREATED          STATUS          PORTS                                           NAMES
 ...
 b335f7f089e4   rancher/k3d-proxy:5.0.1-rc.1   "/bin/sh -c nginx-pr…"   1 minute ago   Up 1 minute   0.0.0.0:8081->80/tcp, 0.0.0.0:44959->6443/tcp   k3d-cluster1-serverlb
@@ -88,9 +84,7 @@ Run the following command:
 awslocal eks describe-cluster --name cluster1
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "cluster": {
         "name": "cluster1",
@@ -145,9 +139,7 @@ Run the following command:
 awslocal ecr create-repository --repository-name "fancier-nginx"
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "repository": {
         "repositoryArn": "arn:aws:ecr:us-east-1:000000000000:repository/fancier-nginx",
@@ -194,9 +186,7 @@ awslocal eks update-kubeconfig --name cluster1 && \
     kubectl config use-context arn:aws:eks:us-east-1:000000000000:cluster/cluster1
 ```
 
-The output will be:
-
-```bash
+```bash title="Output"
 ...
 Added new context arn:aws:eks:us-east-1:000000000000:cluster/cluster1 to /home/localstack/.kube/config
 Switched to context "arn:aws:eks:us-east-1:000000000000:cluster/cluster1".
@@ -239,7 +229,7 @@ kubectl describe pod fancier-nginx
 
 In the events, we can see that the pull from ECR was successful:
 
-```bash
+```bash title="Output"
   Normal  Pulled     10s   kubelet            Successfully pulled image "000000000000.dkr.ecr.us-east-1.localhost.localstack.cloud:4566/fancier-nginx:latest" in 2.412775896s
 ```
 
@@ -300,9 +290,7 @@ You will be able to send a request to `nginx` via the load balancer port `8081`
 curl http://localhost:8081/test123
 ```
 
-The output will be:
-
-```bash
+```bash title="Output"
 <html>
 ...
 <hr><center>nginx/1.21.6</center>
@@ -379,9 +367,7 @@ You can create an EKS Cluster configuration using the following command:
 awslocal eks create-cluster --name cluster1 --role-arn arn:aws:iam::000000000000:role/eks-role --resources-vpc-config '{}'
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "cluster": {
         "name": "cluster1",
@@ -400,9 +386,7 @@ And check that it was created with:
 awslocal eks list-clusters
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "clusters": [
         "cluster1"
@@ -487,19 +471,15 @@ This host-based routing mechanism ensures that each service is uniquely identifi
 curl http://eks-service-1.localhost.localstack.cloud:8081/v1
 ```
 
-The output will be:
-
-```bash
+```bash title="Output"
 ... [output of service 1]
 ```
 
 ```bash
 curl http://eks-service-2.localhost.localstack.cloud:8081/v1
 ```
 
-The output will be:
-
-```bash
+```bash title="Output"
 ... [output of service 2]
 ```
 
@@ -528,9 +508,7 @@ awslocal eks create-cluster \
   --tags '{"_volume_mount_":"/path/on/host:/path/on/node"}'
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
     "cluster": {
         "name": "cluster1",

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

@@ -41,9 +41,7 @@ Wait for it to be available, then you can use the cluster endpoint for Redis ope
 awslocal elasticache describe-cache-clusters --show-cache-node-info --query "CacheClusters[0].CacheNodes[0].Endpoint"
 ```
 
-The output will be:
-
-```json
+```bash title="Output"
 {
   "Address": "localhost.localstack.cloud",
   "Port": 4510

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

@@ -32,9 +32,7 @@ awslocal elasticbeanstalk create-application \
     --application-name my-app
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "Application": {
         "ApplicationArn": "arn:aws:elasticbeanstalk:us-east-1:000000000000:application/my-app",
@@ -63,9 +61,7 @@ awslocal elasticbeanstalk create-environment \
     --environment-name my-environment
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "EnvironmentName": "my-environment",
     "EnvironmentId": "4fcae3fb",
@@ -94,9 +90,7 @@ awslocal elasticbeanstalk create-application-version \
     --version-label v1
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "ApplicationVersion": {
         "ApplicationVersionArn": "arn:aws:elasticbeanstalk:us-east-1:000000000000:applicationversion/my-app/v1",

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

@@ -45,9 +45,7 @@ awslocal elastictranscoder create-pipeline \
     --role arn:aws:iam::000000000000:role/Elastic_Transcoder_Default_Role
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "Pipeline": {
         "Id": "0998507242379-vltecz",
@@ -85,9 +83,7 @@ Execute the following command to list all pipelines:
 awslocal elastictranscoder list-pipelines
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "Pipelines": [
         {
@@ -126,9 +122,7 @@ Execute the following command to read the pipeline with the ID `0998507242379-vl
 awslocal elastictranscoder read-pipeline --id 0998507242379-vltecz
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "Pipeline": {
         "Id": "0998507242379-vltecz",

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

@@ -111,9 +111,7 @@ Finally, you can issue an HTTP request to the `DNSName` parameter of `CreateLoad
 curl example-lb.elb.localhost.localstack.cloud:4566
 ```
 
-The following output will be retrieved:
-
-```bash
+```bash title="Output"
 {
   "host": {
     "hostname": "example-lb.elb.localhost.localstack.cloud",

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

@@ -103,9 +103,7 @@ Execute the following command to create a job using a `job.json` file:
 awslocal mediaconvert create-job --cli-input-json file://job.json
 ```
 
-The following output would be retrieved:
-
-```json
+```bash title="Output"
 {
     "Job": {
         "AccelerationSettings": {
@@ -164,9 +162,7 @@ awslocal mediaconvert create-queue
     --description "High priority queue for video encoding"
 ```
 
-The following output would be retrieved:
-
-```bash
+```bash title="Output"
 {
     "Queue": {
         "Arn": "arn:aws:mediaconvert:us-east-1:000000000000:queues/MyQueue",

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

@@ -40,7 +40,7 @@ awslocal emr create-cluster \
 
 You will see a response similar to the following:
 
-```bash
+```bash title="Output"
 {
     "ClusterId": "j-A2KF3EKLAOWRI"
 }