docs: Add detailed explication of IAM policies #15
Conversation
|
These look great to me. I don't have write permissions on the repo, but looks good to merge. |
|
This looks awesome, @gavinelder! Can we use it in the public documentation? |
|
@justinegeffen I would love for us to merge this into public docs |
Absolutely no problem doing that! I'll open a PR shortly. :) |
gavinelder
changed the title
bebosudo
left a comment
bebosudo
left a comment
There was a problem hiding this comment.
Great start! I left some comments to improve the meaning. Happy to give this a second pass
Co-authored-by: Alberto Chiusole <[email protected]>
bebosudo
left a comment
bebosudo
left a comment
There was a problem hiding this comment.
here are some more possible improvements
|
Some feedback from a prospect getting set up on Seqera Platform for the first time on this PR:
|
|
@bebosudo, @gavinelder: would be great if we could merge this PR. Let me know how I can help push it over the line. :) |
bebosudo
left a comment
bebosudo
left a comment
There was a problem hiding this comment.
More comments that I'll commit in the next step
…mention from forge readme
…and adding more context
The IAM user shouldn't be the one sending emails out
|
This is great, thanks all! I did an editorial pass to tidy up formatting and some minor language changes. Other than that, it's good to go on my side! |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Co-authored-by: Ken Brewer <[email protected]>
kenibrewer
left a comment
kenibrewer
left a comment
There was a problem hiding this comment.
Taking a second look, a lot of these changes are big steps in the right direction. So let's merge this and improve in follow-on PRs if needed.
The following updated the existing tower IAM policy by segmenting it into resource classes so end users can customize this to suit their own specific needs.
There are no additional permissions / added or removed only changes to the logical grouping along within additional explanations as to how an end user can craft these policies themselves.
Please note that further to this an end user can define a custom IAM policy for CE environments manually giving them a finer level of control under the CE environment advanced options.