[Content]: Amazon Kinesis Firehose Destination Configuration Guide

[joeynmq]

What article on segment.com/docs is affected?

https://segment.com/docs/connections/destinations/catalog/amazon-kinesis-firehose/#attach-multiple-sources-to-your-iam-role

What part(s) of the article would you like to see updated?

The steps 3 & 4 under the Attach multiple sources to your IAM role section has flagged that the "sts:ExternalId": "YOUR_SEGMENT_SOURCE_ID".

However, we received some tickets from customers who were having problems connecting to Firehose destinations if they enter the Source ID to sts:ExternalId. We have then solved the issue by adding the Secret ID (as in the destination settings) to sts:ExternalId.

I would recommend updating our our docs here to avoid confusion.
E.g., from "sts:ExternalId": "YOUR_SEGMENT_SOURCE_ID" to "sts:ExternalId": "YOUR_SECRET_ID"

Thanks :)

Additional information

No response

[markzegarelli]

Hi @joeynmq. Apologies for the delay on this one.

Would you recommend replacing the same value in this snippet as well?

 {
   "Version": "2012-10-17",
   "Statement": [
     {
       "Effect": "Allow",
       "Principal": {
         "AWS": "arn:aws:iam::595280932656:root"
       },
       "Action": "sts:AssumeRole",
       "Condition": {
         "StringEquals": {
           "sts:ExternalId": ["YOUR_SEGMENT_SOURCE_ID", "ANOTHER_SOURCE_ID", "A_THIRD_SOURCE_ID"]
         }
       }
     }
   ]
 }

[joeynmq]

Hi @markzegarelli, yes that would be great! I would recommend changing it from
["YOUR_SEGMENT_SOURCE_ID", "ANOTHER_SOURCE_ID", "A_THIRD_SOURCE_ID"]
to
["YOUR_SEGMENT_SECRET_ID", "ANOTHER_SECRET_ID", "A_THIRD_SECRET_ID"]

Much appreciated :)

[forstisabella]

Closing, as this was addressed in PR #4182.