You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/storage/data-lakes/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Data Lakes uses an EMR cluster to run jobs that load events from all sources int
39
39
### AWS IAM Role
40
40
41
41
Data Lakes uses an IAM role to grant Segment secure access to your AWS account. The required inputs are:
42
-
-**external_ids**: External IDs are the part of the IAM role which Segment uses to assume the role providing access to your AWS account. You will define the external ID in the IAM role as the Segment source ID which you want to connect to Data Lakes. The Segment source ID can be retrieved from the [Segment app[(https://app.segment.com/goto-my-workspace/overview)] when navigating to the Source > Settings > API Keys > Source ID.
42
+
-**external_ids**: External IDs are the part of the IAM role which Segment uses to assume the role providing access to your AWS account. You will define the external ID in the IAM role as the Segment source ID which you want to connect to Data Lakes. The Segment source ID can be retrieved from the [Segment app](https://app.segment.com/goto-my-workspace/overview)] when navigating to the Source > Settings > API Keys > Source ID.
43
43
-**s3_bucket**: Name of the S3 bucket used by the Data Lake.
44
44
45
45
@@ -161,4 +161,4 @@ Segment stops creating new tables for the events after you exceed this limit. Ho
161
161
162
162
You should also read the [additional considerations](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hive-metastore-glue.html) when using AWS Glue Data Catalog.
0 commit comments