AWS firehose documentation change
Summary
Changed absolute URLs to relative paths for VPC access documentation and data transformation references
Security assessment
Link formatting changes without substantive security content modifications. Splunk VPC access guidance remains functionally unchanged.
Diff
diff --git a/firehose/latest/dev/data-not-delivered-to-splunk.md b/firehose/latest/dev/data-not-delivered-to-splunk.md index ad95279da..3d9af7036 100644 --- a//firehose/latest/dev/data-not-delivered-to-splunk.md +++ b//firehose/latest/dev/data-not-delivered-to-splunk.md @@ -9 +9 @@ Check the following if data is not delivered to your Splunk endpoint. - * If your Splunk platform is in a VPC, make sure that Firehose can access it. For more information, see [Access to Splunk in VPC](https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html#using-iam-splunk-vpc). + * If your Splunk platform is in a VPC, make sure that Firehose can access it. For more information, see [Accessing Splunk in VPC](./controlling-access.html#using-iam-splunk-vpc). @@ -35 +35 @@ Check the following if data is not delivered to your Splunk endpoint. - * If you're using data transformation, make sure that your Lambda function never returns responses whose payload size exceeds 6 MB. For more information, see [Amazon Data FirehoseData Transformation](https://docs.aws.amazon.com/firehose/latest/dev/data-transformation.html). + * If you're using data transformation, make sure that your Lambda function never returns responses whose payload size exceeds 6 MB. For more information, see [Amazon Data Firehose Data Transformation](./data-transformation.html#data-transformation.title).