Skip to content

Commit a6ed0fb

Browse files
committed
Update AWS docs to reflect externalId/secretId settings lock
1 parent b5ee7a8 commit a6ed0fb

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

src/connections/destinations/catalog/amazon-kinesis-firehose/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -187,7 +187,7 @@ If you have many sources using Kinesis that it's impractical to attach all of th
187187
To set this value for a Secret ID:
188188
1. Go to the Kinesis Firehose destination settings from each of your Segment sources.
189189
2. Click **Secret ID** and enter your Workspace ID.
190-
* **NOTE:** For security purposes, Segment recommends you to use your Segment Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to: **Settings > Workspace Settings > ID** from the Segment dashboard.
190+
* **NOTE:** For security purposes, Segment sets your Segment Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it to make your account more secure.
191191
3. Once all of your sources are updated to use this value, find the IAM role you created for this destination in the AWS Console in **Services > IAM > Roles**.
192192
4. Select the role and navigate to the **Trust Relationships** tab.
193193
5. Click **Edit trust relationship**. You should see a snippet that looks something like this:

src/connections/destinations/catalog/amazon-kinesis/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ To get started:
4848
4. Create a new Kinesis destination.
4949
1. In the Segment source that you want to connect to your Kinesis destination, click **Add Destination**. Search and select the **Amazon Kinesis** destination.
5050
2. Enter the **Role Address**, **Stream Region**, **Stream Name**, and **Secret ID**.
51-
* **NOTE:** For security purposes, Segment recommends you to use your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to: **Settings > Workspace Settings > ID**.
51+
* **NOTE:** For security purposes, Segment sets your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it to make your account more secure.
5252

5353
## Page
5454
If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like:
@@ -217,7 +217,7 @@ After you update the IAM policy, Segment systems default to use PutRecords for m
217217
If you have many sources using Kinesis that it's impractical to attach all of their IDs to your IAM role, you can instead opt to set a secret ID. To set this value:
218218
1. Go to **Connections > Destinations > Amazon Kinesis** for each of your Segment sources.
219219
2. Click **Secret ID** and enter your Workspace ID.
220-
* **NOTE:** For security purposes, Segment recommends you to use your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to: **Settings > Workspace Settings > ID**.
220+
* **NOTE:** For security purposes, Segment sets your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it and make your account more secure.
221221
3. Once all of your sources have been updated to use this value, find the IAM role you created for this destination in the AWS Console in **Services > IAM > Roles**.
222222
4. Click on the role and navigate to the **Trust Relationships** tab.
223223
5. Click **Edit trust relationship**. You should see a snippet that looks something that looks like this:

src/connections/destinations/catalog/amazon-lambda/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,8 @@ Using CloudFormation minimizes the setup steps needed, and is Segment's recommen
7676
![](images/CloudFormationUploadTemplate.png)
7777

7878
5. Give your stack a name.
79-
6. For the **ExternalId** parameter, enter the "External ID" setting in your Segment Lambda destination settings. This should be your **Workspace ID**.
80-
* **NOTE:** For security purposes, Segment recommends you to use your Workspace ID as your External ID. If you’re currently using an External ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to: **Settings > Workspace Settings > ID**.
79+
6. For the **ExternalId** parameter, enter the "External ID" setting in your Segment Lambda destination settings.
80+
* **NOTE:** For security purposes, Segment will set your Workspace ID as your External ID. If you’re currently using an External ID different from your Workspace ID, reach out to our support team so they can change it and make your account more secure.
8181
7. The **LambdaARN** parameter corresponds to the **Lambda** setting in your Segment Lambda destination settings.
8282

8383
![](images/CloudFormationStackDetails.png)

src/connections/destinations/catalog/amazon-personalize/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ The following examples show how to configure an AWS Glue job to convert Segment
201201
**Create AWS Glue ETL Job**
202202

203203
To create an AWS Glue ETL Job:
204-
1. Navigate to the Glue service in your AWS console.
204+
1. Navigate to the Glue service in your AWS console.
205205
2. Click **Get started** and then click **Jobs** in the left navigation on the Glue console page.
206206

207207
![](images/GlueJobs.png)
@@ -627,7 +627,7 @@ To create a Personlize campaign:
627627
628628
![](images/PersonalizeCreateCampaignDash.png)
629629
630-
2. Enter the name for your campaign.
630+
2. Enter the name for your campaign.
631631
3. Select the solution you created above and click **Create campaign**.
632632
633633
![](images/PersonalizeCreateCampaign.png)
@@ -694,7 +694,7 @@ To create an IAM role:
694694
> note ""
695695
> **NOTE:** Your Source ID can be found by navigating to **Settings > API Keys** from your Segment source homepage.
696696
>
697-
> If you're using an External ID, for security purposes, Segment recommends you to use your Segment Workspace ID as your External ID. If you use an External ID different from your Workspace ID, please change it to make your account more secure. You can find your Workspace ID by going to: **Settings > Workspace Settings > ID** in the Segment dashboard.
697+
> For security purposes, Segment will set your Workspace ID as your External ID. If you are currently using an External ID different from your Workspace ID, reach out to our support team so they can change it and make your account more secure.
698698
699699
```json
700700
{

0 commit comments

Comments
 (0)