Skip to content
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

Removed hardcoded access_keys #3072

Merged
merged 7 commits into from
Oct 18, 2019
Merged

Removed hardcoded access_keys #3072

merged 7 commits into from
Oct 18, 2019

Conversation

benarent
Copy link
Contributor

@benarent benarent commented Oct 9, 2019

Starting to fix #3071

Copy link
Contributor

@webvictim webvictim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm unsure whether the ${} syntax makes it easier to understand. It might be best to use things like example-table-name to make it very clear that people have to replace this themselves.

(certainly until we get some kind of coloured highlighting for examples/things to replace)

@benarent benarent mentioned this pull request Oct 9, 2019
@benarent
Copy link
Contributor Author

benarent commented Oct 9, 2019

^ Thanks Gus, I've updated it and also added a reference for the DynamoDB regions.

secret_key: Oc20333k293SKwzraT3ah3Rv1G3/97POQb3eGziSZ
# table_name is
table_name: Example_TELEPORT_DYNAMO_TABLE_NAME
audit_table_name: Example_TELEPORT_DYNAMO_EVENTS_TABLE_NAME

# This setting configures Teleport to send the audit events to three places:
# To keep a copy on a local filesystem, in DynamoDB and to Stdout.
audit_events_uri: ['file:///var/lib/teleport/audit/events', 'dynamodb://table_name', 'stdout://']
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(this is the 'new' way of storing events to DynamoDB)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @webvictim not sure if this a note / comment. If I should update let me know.

@benarent
Copy link
Contributor Author

benarent commented Oct 9, 2019

K, thanks @webvictim I've made those changes.

@benarent
Copy link
Contributor Author

Sorry for the delay on turning this around. It's ready for a review now.

@benarent benarent requested a review from webvictim October 17, 2019 17:44
@benarent benarent merged commit e30e6a2 into master Oct 18, 2019
@benarent benarent deleted the benarent/docs/aws-creds branch October 18, 2019 01:40
one000mph pushed a commit to andyet/teleport that referenced this pull request Oct 20, 2019
* Removed hardcoded aws access_keys in favour of customers using IAM and aws credentials.
one000mph pushed a commit to andyet/teleport that referenced this pull request Oct 20, 2019
* Removed hardcoded aws access_keys in favour of customers using IAM and aws credentials.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

audit_table_name doesn't appear in the DynamoDB section of the admin guide
3 participants