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

[FEATURE] Support for custom Path and Permission Boundary for IAM role and custom Path for IAM Policy #272

Open
nileshlathiya opened this issue Dec 9, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@nileshlathiya
Copy link

nileshlathiya commented Dec 9, 2024

Is your feature request related to a problem? Please describe.
I am working with an Enterprise customer on ML use cases and exploring the way to orchestrate deploy using seed-farmer and aws-codeseeder. As a security best practice, enforcing permission boundaries and specifying custom paths for IAM roles and policies during creation is essential. This approach, widely adopted by enterprise customers, enhances security and access control. Providing features to customize IAM role paths, permission boundaries, and policy paths is highly valuable for aligning with these best practices.

Describe the solution you'd like
I am looking for input parameters for IAM role custom path and permission boundary along with IAM policy custom path when using codeseeder.remote_function or any better solution which allow passing these input parameters so they can be used while IAM role and policy are created as part of aws-codeseeder.

Describe alternatives you've considered
I have manually added the

Additional context
This IAM Role and Policy path and permission boundary are used in most of the scenario where security best practice are followed. So this will be very good addition for user of aws_codeseeder

@nileshlathiya nileshlathiya added the enhancement New feature or request label Dec 9, 2024
@dgraeber
Copy link
Contributor

Circling back on this as I know there are internal conversations with @kukushking , but I have not received any detailed info..

@kukushking
Copy link
Contributor

kukushking commented Jan 27, 2025

The team was away on a holiday. We discussed last week and prioritised for current sprint. Looking into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants