-
Notifications
You must be signed in to change notification settings - Fork 385
Create an IAM role using the AWS CLI #2150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@forstisabella A few small changes. Also, the numbering is broken due to the code samples. You'll need to add two indents to all those. For example:
1. Copy the following code snippet and save it as a file on your local machine titled `trust-relationship-policy.json`. Replace `<YOUR_WORKSPACE_ID>` with your Segment workspace ID.
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::595280932656:role/segment-s3-integration-production-access"
},
"Action": "sts:AssumeRole",
"Condition": {
"StringEquals": {
"sts:ExternalId": "<YOUR_WORKSPACE_ID>"
}
}
}
]
}
```
✔️ Deploy Preview for segment-docs ready! 🔨 Explore the source changes: 2085a66 🔍 Inspect the deploy log: https://app.netlify.com/sites/segment-docs/deploys/619546d858afde00081e32d6 😎 Browse the preview: https://deploy-preview-2150--segment-docs.netlify.app |
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
Added section to the existing AWS S3 with IAM Role Support Destination page that covers creating an IAM role using the AWS CLI.
Merge timing
On or before Thursday, November 18th
Related issues (optional)