more aws services done

Author: quetzalliwrites

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

@@ -47,7 +47,7 @@ Let us walk through these files.
 It does nothing more than print a salutation message.
 Create a `MessageUtil.java` file and save it into the `src/main/java` directory.
 
-```java
+```java showLineNumbers
 public class MessageUtil {
   private String message;
 
@@ -71,7 +71,7 @@ public class MessageUtil {
 Every build needs to be tested.
 Therefore, create the `TestMessageUtil.java` file in the `src/test/java` directory.
 
-```java
+```java showLineNumbers
 import org.junit.Test;
 import org.junit.Ignore;
 import static org.junit.Assert.assertEquals;
@@ -101,7 +101,7 @@ This small suite simply verifies that the greeting message is built correctly.
 Finally, we need a `pom.xml` file to instruct Maven about what to build and which artifact needs to be produced.
 Create this file at the root of your directory.
 
-```xml
+```xml showLineNumbers
 <project xmlns="http://maven.apache.org/POM/4.0.0" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
@@ -140,7 +140,7 @@ A `buildspec` file is a collection of settings and commands, specified in YAML f
 
 Create this `buildspec.yml` file in the root directory.
 
-```yaml
+```yaml showLineNumbers
 version: 0.2
 
 phases:
@@ -200,7 +200,7 @@ awslocal s3 cp MessageUtil.zip s3://codebuild-demo-input
 To properly work, AWS CodeBuild needs access to other AWS services, e.g., to retrieve the source code from a S3 bucket.
 Create a `create-role.json` file with following content:
 
-```json
+```json showLineNumbers
 {
   "Version": "2012-10-17",
   "Statement": [
@@ -227,7 +227,7 @@ it will be needed to create the CodeBuild project later on.
 Let us now define a policy for the created role.
 Create a `put-role-policy.json` file with the following content:
 
-```json
+```json showLineNumbers
 {
   "Version": "2012-10-17",
   "Statement": [
@@ -302,7 +302,7 @@ awslocal codebuild create-project --generate-cli-skeleton
 From the generated file, change the source and the artifact location to match the S3 bucket names you just created.
 Similarly, fill in the ARN of the CodeBuild service role.
 
-```json {hl_lines=[5,9,16]}
+```json {hl_lines=[5,9,16]} showLineNumbers
 {
   "name": "codebuild-demo-project",
   "source": {

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

@@ -61,7 +61,7 @@ This requires a properly configured IAM role that our pipeline can assume.
 
 Create the role and make note of the role ARN:
 
-```json
+```json showLineNumbers
 # role.json
 {
     "Version": "2012-10-17",
@@ -85,7 +85,7 @@ awslocal iam create-role --role-name role --assume-role-policy-document file://r
 
 Now add a permissions policy to this role that permits read and write access to S3.
 
-```json
+```json showLineNumbers
 # policy.json
 {
     "Version": "2012-10-17",
@@ -121,7 +121,7 @@ This is a deploy action which uploads the file to the target bucket.
 Pay special attention to `roleArn`, `artifactStore.location` as well as `S3Bucket`, `S3ObjectKey`, and `BucketName`.
 These correspond to the resources we created earlier.
 
-```json {hl_lines=[6,9,26,27,52]}
+```json {hl_lines=[6,9,26,27,52]} showLineNumbers
 # declaration.json
 {
     "name": "pipeline",

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

@@ -237,7 +237,7 @@ Cognito offers a variety of lifecycle hooks called Cognito Lambda triggers, whic
 To illustrate, suppose you wish to define a _user migration_ Lambda trigger in order to migrate users from your existing user directory into Amazon Cognito user pools at sign-in.
 In this case, you can start by creating a Lambda function, let's say named `"migrate_users"`, responsible for performing the migration by creating a new file `index.js` with the following code:
 
-```javascript
+```javascript showLineNumbers
 const validUsers = {
   belladonna: { password: "12345678Aa!", emailAddress: "[email protected]" },
 };
@@ -379,7 +379,7 @@ awslocal cognito-idp create-resource-server \
 
 You can retrieve the token from your application using the specified endpoint: `http://cognito-idp.localhost.localstack.cloud:4566/_aws/cognito-idp/oauth2/token`.
 
-```javascript
+```javascript showLineNumbers
 require('dotenv').config();
 const axios = require('axios');
 
@@ -419,7 +419,7 @@ Furthermore, you have the option to combine Cognito and LocalStack seamlessly wi
 
 For instance, consider this snippet from a `serverless.yml` configuration:
 
-```yaml
+```yaml showLineNumbers
 service: test
 
 plugins:

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

@@ -249,7 +249,7 @@ npm install [email protected]
 
 Next, copy the following code into a new file named `index.js` in the `resources` folder:
 
-```javascript
+```javascript showLineNumbers
 const AWS = require('aws-sdk');
 const RDS = AWS.RDS;
 const { MongoClient } = require('mongodb');
@@ -340,7 +340,7 @@ Secrets follow a [well-defined pattern](https://docs.aws.amazon.com/secretsmanag
 For the lambda function, you can pass the secret arn as `SECRET_NAME`.
 In the lambda, you can then retrieve the secret details like this:
 
-```javascript
+```javascript showLineNumbers
 const AWS = require('aws-sdk');
 const { MongoClient } = require('mongodb');
 

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

@@ -55,7 +55,7 @@ You can notice that in the `LatestStreamArn` field of the response:
 You can now create a Lambda function (`publishNewBark`) to process stream records from `BarkTable`.
 Create a new file named `index.js` with the following code:
 
-```javascript
+```javascript showLineNumbers
 'use strict';
 var AWS = require("aws-sdk");
 
@@ -98,7 +98,7 @@ awslocal lambda create-function \
 To test the Lambda function, you can invoke it using the [`Invoke`](https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html) API.
 Create a new file named `payload.json` with the following content:
 
-```json
+```json showLineNumbers
 {
     "Records": [
         {

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

@@ -61,7 +61,7 @@ awslocal ecs create-cluster --cluster-name mycluster
 Containers within tasks are defined by a task definition that is managed outside of the context of a cluster.
 To create a task definition that runs an `ubuntu` container forever (by running an infinite loop printing "Running" on startup), create the following file as `task_definition.json`:
 
-```json
+```json showLineNumbers
 {
   "containerDefinitions": [
     {
@@ -296,7 +296,7 @@ ecs_client.register_task_definition(
 
 The same functionality can be achieved with the AWS CDK following this (Python) example:
 
-```python
+```python showLineNumbers
 task_definition = ecs.TaskDefinition(
     ...
     volumes=[
@@ -322,7 +322,7 @@ Your file paths might differ, so check Docker's documentation on [Environment Va
 
 Here is a Docker Compose example:
 
-```yaml
+```yaml showLineNumbers
 services:
   localstack:
     container_name: "${LOCALSTACK_DOCKER_NAME:-localstack-main}"

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

@@ -307,7 +307,7 @@ To enable HTTPS for your endpoints, you can configure Kubernetes to use SSL/TLS
 
 The local EKS cluster comes pre-configured with a secret named `ls-secret-tls`, which can be conveniently utilized to define the `tls` section in the ingress configuration:
 
-```yaml
+```yaml showLineNumbers
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
@@ -425,7 +425,7 @@ In such cases, path-based routing may not be ideal if you need the services to b
 
 To address this requirement, we recommend utilizing host-based routing rules, as demonstrated in the example below:
 
-```bash
+```bash showLineNumbers
 cat <<EOF | kubectl apply -f -
 apiVersion: networking.k8s.io/v1
 kind: Ingress
@@ -532,7 +532,7 @@ As a result, the tag name `__k3d_volume_mount__` is considered deprecated and wi
 After creating your cluster with the `_volume_mount_` tag, you can create your path with volume mounts as usual.
 The configuration for the volume mounts can be set up similar to this:
 
-```yaml
+```yaml showLineNumbers
 apiVersion: v1
 kind: Pod
 metadata:

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

@@ -29,7 +29,7 @@ We will demonstrate how to create a MediaConvert job, list jobs, create a queue,
 
 Create a new file named `job.json` on your local directory:
 
-```json
+```json showLineNumbers
 {
   "Role": "arn:aws:iam::000000000000:role/MediaConvert_Default_Role",
   "Settings": {

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

@@ -219,7 +219,7 @@ Note that only a single backend can be configured, meaning that you will get a s
 
 The following shows a sample docker-compose file that contains a single-noded elasticsearch cluster and a basic localstack setp.
 
-```yaml
+```yaml showLineNumbers
 services:
   elasticsearch:
     container_name: elasticsearch

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

@@ -33,7 +33,7 @@ We will demonstrate creating an EventBridge rule to run a Lambda function on a s
 
 To create a new Lambda function, create a new file called `index.js` with the following code:
 
-```js
+```js showLineNumbers
 'use strict';
 
 exports.handler = (event, context, callback) => {