AWS firehose documentation change
Summary
Formatting improvements and link updates for MSK troubleshooting guide. Added punctuation and converted some absolute links to relative paths.
Security assessment
Changes involve punctuation corrections and link formatting without introducing new security content or addressing vulnerabilities. Security-related statements about permissions and VPC settings were already present.
Diff
diff --git a/firehose/latest/dev/msk_troubleshooting.md b/firehose/latest/dev/msk_troubleshooting.md index 6ba1214a6..4f42e4b22 100644 --- a//firehose/latest/dev/msk_troubleshooting.md +++ b//firehose/latest/dev/msk_troubleshooting.md @@ -17 +17 @@ For troubleshooting processing, transformation or S3 delivery issues, please ref -Check the following if your hose with MSK As Source is failing creation +Check the following if your hose with MSK As Source is failing creation: @@ -21 +21 @@ Check the following if your hose with MSK As Source is failing creation - * If you are using Private connectivity, ensure that [ Private Link on the cluster is turned on](https://docs.aws.amazon.com/msk/latest/developerguide/aws-access-mult-vpc.html) + * If you are using Private connectivity, ensure that [ Private Link on the cluster is turned on](https://docs.aws.amazon.com/msk/latest/developerguide/aws-access-mult-vpc.html). @@ -23 +23 @@ Check the following if your hose with MSK As Source is failing creation -If you are using Public connectivity, ensure that [ Public access on the cluster is turned on](https://docs.aws.amazon.com/msk/latest/developerguide/public-access.html) +If you are using Public connectivity, ensure that [ Public access on the cluster is turned on](https://docs.aws.amazon.com/msk/latest/developerguide/public-access.html). @@ -25 +25 @@ If you are using Public connectivity, ensure that [ Public access on the cluster - * If you are using Private connectivity, make sure that you add a [ resource based policy that allows Firehose to create Private Link](https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html#access-to-msk). Also refer: [ MSK cross account permissions](https://docs.aws.amazon.com/msk/latest/developerguide/mvpc-cross-account-permissions.html) + * If you are using Private connectivity, make sure that you add a [resource based policy that allows Firehose to create Private Link](./controlling-access.html#access-to-msk). Also refer: [ MSK cross account permissions](https://docs.aws.amazon.com/msk/latest/developerguide/mvpc-cross-account-permissions.html). @@ -27 +27 @@ If you are using Public connectivity, ensure that [ Public access on the cluster - * Ensure that the role in source configuration has [ permission to ingest data from cluster's Topic](https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html#firehose-assume-role) + * Ensure that the role in source configuration has [permission to ingest data from cluster's Topic](./controlling-access.html#firehose-assume-role). @@ -29 +29 @@ If you are using Public connectivity, ensure that [ Public access on the cluster - * Ensure that your VPC security groups allow incoming traffic on [ ports used by the cluster's bootstrap servers](https://docs.aws.amazon.com/msk/latest/developerguide/port-info.html) + * Ensure that your VPC security groups allow incoming traffic on [ ports used by the cluster's bootstrap servers](https://docs.aws.amazon.com/msk/latest/developerguide/port-info.html).