Skip to content

Commit 202ed17

Browse files
committed
DOC-469 Last editing pass
1 parent c1fbd6d commit 202ed17

File tree

1 file changed

+9
-9
lines changed
  • src/connections/storage/catalog/aws-s3

1 file changed

+9
-9
lines changed

src/connections/storage/catalog/aws-s3/index.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -242,8 +242,8 @@ For example:
242242

243243
For each source in the scenario, complete the steps described in [Migrate an existing destination](#migrate-an-existing-destination), and ensure that you have separate IAM Roles and Permissions set for staging and production use.
244244

245-
## Migrate an existing destination using Public API
246-
This procedure uses Segment's Public API to migrate your existing Amazon S3 destination to the new AWS S3 destination. For more information about the Public API, see the [Public API Getting Started Guide](https://api.segmentapis.com/docs/guides/#getting-started).
245+
## Migrate an existing destination using the Public API
246+
This procedure uses Segment's Public API to migrate an existing Amazon S3 destination to the new AWS S3 destination. For more information about the Public API, see the [Public API documentation](https://api.segmentapis.com/docs/guides/#introduction).
247247

248248
> warning "Avoid overwriting data"
249249
> Sending data to the same S3 location from both the existing Amazon S3 destination and the AWS S3 destinations will overwrite data in your instance of S3. To avoid this, disable your Amazon S3 destination after you create your AWS S3 destination.
@@ -254,17 +254,17 @@ To migrate to the AWS S3 destination using the Public API:
254254
2. From the Catalog, select the Storage Destinations tab, and select the **AWS S3** destination.
255255
3. On the AWS S3 destination page, click the **Configure AWS S3** button.
256256
4. Configure your AWS S3 destination. When asked for the bucket name, enter `<YOUR_BUCKET_NAME>/segment-logs/test`.
257-
5. Enable the destination, and verify data is received at `<YOUR_BUCKET_NAME>/segment-logs/test/segment-logs`. <br/>**Note:** If the folder receives data, continue to the next step. If you don't see log entries, check the trust relationship document and IAM policy attached to the role.
258-
6. Create the new AWS S3 destination using the [`create destination`](https://api.segmentapis.com/docs/connections/destinations/#create-destination) call. The `sourceId`, `metadataId`, and `settings` parameters are required. An example of the parameters is below: <br/>
257+
5. Enable the destination, and verify data is received at `<YOUR_BUCKET_NAME>/segment-logs/test/segment-logs`. <br/>**Note:** If the folder receives data, continue to the next step. If you don't see log entries, check the trust relationship document and IAM policy attached to your IAM role.
258+
6. Create your new AWS S3 destination using the [`create destination`](https://api.segmentapis.com/docs/connections/destinations/#create-destination) Public API call. The `sourceId`, `metadataId`, and `settings` parameters are required. An example of the parameters is below: <br/>
259259
```json
260260
{
261-
"sourceId": "rh5BDZp6QDHvXFCkibm1pR",
261+
"sourceId": "$SOURCE_ID",
262262
"metadataId": "60be92c8dabdd561bf6c9130",
263263
"name": "AWS S3",
264264
"settings": {
265265
"region": "XYZ",
266266
"s3Bucket": "test",
267-
"iamRoleArn": "arn:aws:iam::355207333203:role/organization-s3-copy-secure"
267+
"iamRoleArn": "$IAM_ROLE_ARN"
268268
}
269269
}
270270
```
@@ -282,23 +282,23 @@ curl -vvv --location --request PATCH https://api.segmentapis.com/destinations/$D
282282
' | jq
283283
```
284284
<br/>
285-
8. Identify the source IDs for your old Amazon S3 destination(s). You can use the public-api to return information about a list of your Amazon S3 destinations or an individual destination. <br/>
285+
8. Identify the source IDs for your old Amazon S3 destination(s). You can use the Public API to return information about a list of your Amazon S3 destinations or an individual destination. <br/><br/>
286286
To return a list of all of your Amazon S3 destinations, use the [`list destinations`](https://api.segmentapis.com/docs/connections/destinations/#list-destinations) call and filter the results using metadata id `54f418c3db31d978f14aa925` or slug `amazon-s3`: <br/>
287287
```shell
288288
curl -vvv --location --request GET https://api.segmentapis.com/destinations?pagination.count=1 \
289289
--header 'Content-Type: application/json' \
290290
--header 'Authorization: Bearer ...' \
291291
--data-raw '
292292
```
293-
<br/> To return the information for an individual Amazon S3 destination, use the [`get destination`](https://api.segmentapis.com/docs/connections/destinations/#get-destination) call, using the destination ID for your individual Amazon S3 destination (**Note:** The destination ID for your Amazon S3 source is visible in the Segment app, on the destination's settings page) <br/>
293+
To return the information for an individual Amazon S3 destination, use the [`get destination`](https://api.segmentapis.com/docs/connections/destinations/#get-destination) call, using the destination ID for your individual Amazon S3 destination (**Note:** The destination ID for your Amazon S3 source is visible in the Segment app, on the destination's settings page.) <br/>
294294
```shell
295295
curl -vvv --location --request GET https://api.segmentapis.com/destinations/$DESTINATION_ID \
296296
--header 'Content-Type: application/json' \
297297
--header 'Authorization: Bearer ...' \
298298
--data-raw '
299299
```
300300
301-
9. Disable the Amazon S3 destinations using the following command (replacing `$DESTINATION_ID` with the ID of your Amazon S3 destination you found in step 8):
301+
9. Disable the Amazon S3 destinations using the following command, replacing `$DESTINATION_ID` with the ID of your Amazon S3 destination you found in previous step:
302302
303303
```shell
304304
curl -vvv --location --request PATCH https://api.segmentapis.com/destinations/$DESTINATION_ID \

0 commit comments

Comments
 (0)