Where on segment.com/docs did you see this issue?
https://segment.com/docs/unify/profiles-sync/profiles-sync-setup/#connection-settings
What browsers are you seeing the problem on?
No response
Please describe the issue.
The nature of serverless compute got around a need to explicitly allow for Databricks to reach back out to Segment AWS for the undocumented COPY INTO approach.
NB: This may be another thing to log re documentation improvements. I'm not sure how many other customers doing Segment / Databricks integration would hit this challenge but from what I gather having things locked down to only allow Databricks to reach out to known/trusted sources isn't unusual. And if the documentation explicitly mentioned that Databricks will need to reach back out to Segment's AWS location then that would likely help customers avoid the issue.
Reference : [https://segment.zendesk.com/hc/requests/576025]
Where on segment.com/docs did you see this issue?
https://segment.com/docs/unify/profiles-sync/profiles-sync-setup/#connection-settings
What browsers are you seeing the problem on?
No response
Please describe the issue.
The nature of serverless compute got around a need to explicitly allow for Databricks to reach back out to Segment AWS for the undocumented COPY INTO approach.
NB: This may be another thing to log re documentation improvements. I'm not sure how many other customers doing Segment / Databricks integration would hit this challenge but from what I gather having things locked down to only allow Databricks to reach out to known/trusted sources isn't unusual. And if the documentation explicitly mentioned that Databricks will need to reach back out to Segment's AWS location then that would likely help customers avoid the issue.
Reference : [https://segment.zendesk.com/hc/requests/576025]