AWS managed-flink documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in multiple instances and updated phrasing.
Security assessment
Consistency update for service naming. No impact on security controls as Lambda execution logic and IAM permissions remain unaltered.
Diff
diff --git a/managed-flink/latest/java/lambda-cfn-flink.md b/managed-flink/latest/java/lambda-cfn-flink.md index f193bc29a..5399d2890 100644 --- a//managed-flink/latest/java/lambda-cfn-flink.md +++ b//managed-flink/latest/java/lambda-cfn-flink.md @@ -11 +11 @@ Amazon Managed Service for Apache Flink (Amazon MSF) was previously known as Ama -The following exercise shows how to start a Flink application created with AWS CloudFormation using a Lambda function in the same stack. +The following exercise shows how to start a Flink application created with CloudFormation using a Lambda function in the same stack. @@ -15 +15 @@ The following exercise shows how to start a Flink application created with AWS C -Before you begin this exercise, follow the steps on creating a Flink application using AWS CloudFormation at [AWS::KinesisAnalytics::Application](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kinesis-analyticsapplication.html). +Before you begin this exercise, follow the steps on creating a Flink application using CloudFormation at [AWS::KinesisAnalytics::Application](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kinesis-analyticsapplication.html). @@ -19 +19 @@ Before you begin this exercise, follow the steps on creating a Flink application -To start a Flink application after creation or update, we use the kinesisanalyticsv2 [start-application](https://docs.aws.amazon.com/cli/latest/reference/kinesisanalyticsv2/start-application.html) API. The call will be triggered by an AWS CloudFormation event after Flink application creation. We’ll discuss how to set up the stack to trigger the Lambda function later in this exercise, but first we focus on the Lambda function declaration and its code. We use `Python3.8` runtime in this example. +To start a Flink application after creation or update, we use the kinesisanalyticsv2 [start-application](https://docs.aws.amazon.com/cli/latest/reference/kinesisanalyticsv2/start-application.html) API. The call will be triggered by an CloudFormation event after Flink application creation. We’ll discuss how to set up the stack to trigger the Lambda function later in this exercise, but first we focus on the Lambda function declaration and its code. We use `Python3.8` runtime in this example. @@ -86 +86 @@ To start a Flink application after creation or update, we use the kinesisanalyti -In the preceding code, Lambda processes incoming AWS CloudFormation events, filters out everything besides `Create` and `Update`, gets the application state and start it if the state is `READY`. To get the application state, you must create the Lambda role, as shown following. +In the preceding code, Lambda processes incoming CloudFormation events, filters out everything besides `Create` and `Update`, gets the application state and start it if the state is `READY`. To get the application state, you must create the Lambda role, as shown following.