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.

Sign up for GitHub

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

Jump to bottom

Document best practice for naming resources so as to restrict IAM roles #42

Closed
lindydonna opened this issue Dec 13, 2017 · 1 comment
Closed

Document best practice for naming resources so as to restrict IAM roles #42

lindydonna opened this issue Dec 13, 2017 · 1 comment
Assignees
@lindydonna
Labels
area/docs Improvements or additions to documentation
Milestone
0.16

Comments

@lindydonna
Copy link
Contributor

lindydonna commented Dec 13, 2017 •
edited
Loading

(Assuming bugs around naming are fixed)

In docs, suggest that customers prefix their resources with a short name. Then, they can create access keys that are limited to that name prefix.
@lindydonna lindydonna self-assigned this Dec 13, 2017
@lindydonna lindydonna added the area/docs Improvements or additions to documentation label Dec 13, 2017
@lindydonna lindydonna added this to the 0.14 milestone Feb 6, 2018
@lukehoban lukehoban modified the milestones: 0.14, 0.16 Apr 22, 2018
@lindydonna
Copy link
Contributor Author

IAM roles can be restricted based on resource names, but this is pretty complex guidance. Closing until we get some more customer requirements here. Customers who have used similar tools seem to already have good practices in place.

@infin8x infin8x added the p2 label Jul 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lindydonna lindydonna

Labels
area/docs Improvements or additions to documentation
Projects
None yet
Milestone
0.16
Development

No branches or pull requests
3 participants
@lukehoban @infin8x @lindydonna