get msaf done

Author: HarshCasper

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

@@ -1,30 +1,29 @@
 ---
 title: "Managed Service for Apache Flink"
-linkTitle: "Managed Service for Apache Flink"
 description: >
   Get started with Managed Service for Apache Flink on LocalStack
 tags: ["Ultimate"]
 ---
 
-{{< callout >}}
+:::note
 This service was formerly known as 'Kinesis Data Analytics for Apache Flink'.
-{{< /callout >}}
+:::
 
 ## Introduction
 
 [Apache Flink](https://flink.apache.org/) is a framework for building applications that process and analyze streaming data.
 [Managed Service for Apache Flink (MSF)](https://docs.aws.amazon.com/managed-flink/latest/java/what-is.html) is an AWS service that provides the underlying infrastructure and a hosted Apache Flink cluster that can run Apache Flink applications.
 
-LocalStack lets you to run Flink applications locally and implements several [AWS-compatible API operations]({{< ref "coverage_kinesisanalyticsv2" >}}).
+LocalStack lets you to run Flink applications locally and implements several [AWS-compatible API operations]().
 
 A separate Apache Flink cluster is started in [application mode](https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/deployment/overview/#application-mode) for every Managed Flink application created.
 Flink cluster deployment on LocalStack consists of two separate containers for [JobManager](https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/concepts/flink-architecture/#jobmanager) and [TaskManager](https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/concepts/flink-architecture/#taskmanagers).
 
-{{< callout "note" >}}
+:::note
 The emulated MSF provider was introduced and made the default in LocalStack v4.1.
 
 If you wish to use the older mock provider, you can set `PROVIDER_OVERRIDE_KINESISANALYTICSV2=legacy`.
-{{< /callout >}}
+:::
 
 ## Getting Started
 
@@ -38,16 +37,16 @@ Start the LocalStack container using your preferred method.
 Begin by cloning the AWS sample repository.
 We will use the [S3 Sink](https://github.com/localstack-samples/amazon-managed-service-for-apache-flink-examples/tree/main/java/S3Sink) application in this example.
 
-{{< command >}}
-$ git clone https://github.com/localstack-samples/amazon-managed-service-for-apache-flink-examples.git
-$ cd java/S3Sink
-{{< /command >}}
+```bash
+git clone https://github.com/localstack-samples/amazon-managed-service-for-apache-flink-examples.git
+cd java/S3Sink
+```
 
 Next, use [Maven](https://maven.apache.org/) to compile and package the Flink application into a jar.
 
-{{< command >}}
-$ mvn package
-{{< /command >}}
+```bash
+mvn package
+```
 
 The Flink application jar file will be placed in the `./target/flink-kds-s3.jar` directory.
 
@@ -57,20 +56,20 @@ MSF requires that all application code resides in S3.
 
 Create an S3 bucket and upload the compiled Flink application jar.
 
-{{< command >}}
-$ awslocal s3api create-bucket --bucket flink-bucket
-$ awslocal s3api put-object --bucket flink-bucket --key job.jar --body ./target/flink-kds-s3.jar
-{{< /command >}}
+```bash
+awslocal s3api create-bucket --bucket flink-bucket
+awslocal s3api put-object --bucket flink-bucket --key job.jar --body ./target/flink-kds-s3.jar
+```
 
 ### Output Sink
 
 As mentioned earlier, this Flink application writes the output to an S3 bucket.
 
 Create the S3 bucket that will serve as the sink.
 
-{{< command >}}
-$ awslocal s3api create-bucket --bucket sink-bucket
-{{< /command >}}
+```bash
+awslocal s3api create-bucket --bucket sink-bucket
+```
 
 ### Permissions
 
@@ -93,9 +92,9 @@ Create an IAM role for the running MSF application to assume.
 }
 ```
 
-{{< command >}}
-$ awslocal iam create-role --role-name msaf-role --assume-role-policy-document file://role.json
-{{< /command >}}
+```bash
+awslocal iam create-role --role-name msaf-role --assume-role-policy-document file://role.json
+```
 
 Next create add a permissions policy to this role that permits read and write access to S3.
 
@@ -113,18 +112,18 @@ Next create add a permissions policy to this role that permits read and write ac
 }
 ```
 
-{{< command >}}
-$ awslocal iam put-role-policy --role-name msaf-role --policy-name msaf-policy --policy-document file://policy.json
-{{< /command >}}
+```bash
+awslocal iam put-role-policy --role-name msaf-role --policy-name msaf-policy --policy-document file://policy.json
+```
 
 Now, when the running MSF application assumes this role, it will have the necessary permissions to write to the S3 sink.
 
 ### Deploy Application
 
 With all prerequisite resources in place, the Flink application can now be created and started.
 
-{{< command >}}
-$ awslocal kinesisanalyticsv2 create-application \
+```bash
+awslocal kinesisanalyticsv2 create-application \
     --application-name msaf-app \
     --runtime-environment FLINK-1_20 \
     --application-mode STREAMING \
@@ -146,15 +145,15 @@ $ awslocal kinesisanalyticsv2 create-application \
         }
     }'
 
-$ awslocal kinesisanalyticsv2 start-application --application-name msaf-app
-{{< /command >}}
+awslocal kinesisanalyticsv2 start-application --application-name msaf-app
+```
 
 Once the Flink cluster is up and running, the application will stream the results to the sink S3 bucket.
 You can verify this with:
 
-{{< command >}}
-$ awslocal s3api list-objects --bucket sink-bucket
-{{< /command >}}
+```bash
+awslocal s3api list-objects --bucket sink-bucket
+```
 
 ## CloudWatch Logging
 
@@ -170,10 +169,15 @@ There are following prerequisites for CloudWatch Logs integration:
 
 To add a logging option:
 
-{{< command >}}
-$ awslocal kinesisanalyticsv2 add-application-cloud-watch-logging-option \
+```bash
+awslocal kinesisanalyticsv2 add-application-cloud-watch-logging-option \
     --application-name msaf-app \
     --cloud-watch-logging-option '{"LogStreamARN": "arn:aws:logs:us-east-1:000000000000:log-group:msaf-log-group:log-stream:msaf-log-stream"}'
+```
+
+The response will be similar to:
+
+```json
 {
     "ApplicationARN": "arn:aws:kinesisanalytics:us-east-1:000000000000:application/msaf-app",
     "ApplicationVersionId": 2,
@@ -184,34 +188,39 @@ $ awslocal kinesisanalyticsv2 add-application-cloud-watch-logging-option \
         }
     ]
 }
-{{< /command >}}
+```
 
-{{< callout >}}
+:::note
 Enabling CloudWatch Logs integration has a significant performance hit.
-{{< /callout >}}
+:::
 
 Configured logging options can be retrieved using [DescribeApplication](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_DescribeApplication.html):
 
-{{< command >}}
-$ awslocal kinesisanalyticsv2 describe-application --application-name msaf-app | jq .ApplicationDetail.CloudWatchLoggingOptionDescriptions
+```bash
+awslocal kinesisanalyticsv2 describe-application --application-name msaf-app | jq .ApplicationDetail.CloudWatchLoggingOptionDescriptions
+```
+
+The response will be similar to:
+
+```json
 [
   {
     "CloudWatchLoggingOptionId": "1.1",
     "LogStreamARN": "arn:aws:logs:us-east-1:000000000000:log-group:msaf-log-group:log-stream:msaf-log-stream"
   }
 ]
-{{< /command >}}
+```
 
 Log events can be retrieved from CloudWatch Logs using the appropriate operation.
 To retrieve all events:
 
-{{< command >}}
-$ awslocal logs get-log-events --log-group-name msaf-log-group --log-stream-name msaf-log-stream
-{{< /command >}}
+```bash
+awslocal logs get-log-events --log-group-name msaf-log-group --log-stream-name msaf-log-stream
+```
 
-{{< callout >}}
+:::note
 Logs events are reported to CloudWatch every 10 seconds.
-{{< /callout >}}
+:::
 
 LocalStack reports both Flink application and Flink framework logs to CloudWatch.
 However, certain extended information such as stack traces may be missing.
@@ -222,13 +231,18 @@ You may obtain this information by execing into the Flink Docker container creat
 You can manage [resource tags](https://docs.aws.amazon.com/managed-flink/latest/java/how-tagging.html) using [TagResource](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_TagResource.html), [UntagResource](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_UntagResource.html) and [ListTagsForResource](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_ListTagsForResource.html).
 Tags can also be specified when creating the Flink application using the [CreateApplication](https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_CreateApplication.html) operation.
 
-{{< command >}}
-$ awslocal kinesisanalyticsv2 tag-resource \
+```bash
+awslocal kinesisanalyticsv2 tag-resource \
     --resource-arn arn:aws:kinesisanalytics:us-east-1:000000000000:application/msaf-app \
     --tags Key=country,Value=SE
 
-$ awslocal kinesisanalyticsv2 list-tags-for-resource \
+awslocal kinesisanalyticsv2 list-tags-for-resource \
     --resource-arn arn:aws:kinesisanalytics:us-east-1:000000000000:application/msaf-app
+```
+
+The response will be similar to:
+
+```json
 {
     "Tags": [
         {
@@ -237,11 +251,15 @@ $ awslocal kinesisanalyticsv2 list-tags-for-resource \
         }
     ]
 }
+```
+
+You can also untag the resource:
 
+```bash
 $ awslocal kinesisanalyticsv2 untag-resource \
     --resource-arn arn:aws:kinesisanalytics:us-east-1:000000000000:application/msaf-app \
     --tag-keys country
-{{< /command >}}
+```
 
 ## Supported Flink Versions