-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
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.
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)
^ 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://'] |
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.
(this is the 'new' way of storing events to DynamoDB)
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.
Sorry @webvictim not sure if this a note / comment. If I should update let me know.
K, thanks @webvictim I've made those changes. |
Sorry for the delay on turning this around. It's ready for a review now. |
* Removed hardcoded aws access_keys in favour of customers using IAM and aws credentials.
* Removed hardcoded aws access_keys in favour of customers using IAM and aws credentials.
Starting to fix #3071