8000 Associate production-specific IAM policy to runners with environment=production · Issue #302 · runs-on/runs-on · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Associate production-specific IAM policy to runners with environment=production #302

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
Open
jesseduffield opened this issue May 18, 2025 · 1 comment
Open

Associate production-specific IAM policy to runners with environment=production #302

jesseduffield opened this issue May 18, 2025 · 1 comment

Comments

@jesseduffield
Copy link

I'd like to be able to give my production runners (i.e. the ones that deploy to prod) more IAM permissions than my non-production runners (i.e. the ones that run tests). Github supports different environments for runners but it's not clear to me how I can then associate those environments to different IAM roles. Currently runs-on provides EC2InstanceCustomPolicy as a stack parameter but that's globally defined.
@crohr
Copy link
Contributor
crohr commented May 18, 2025

@jesseduffield did you know RunsOn supports environments? This feature can be used to actually map GitHub environments to RunsOn environments. Downside is that you need to get one RunsOn stack per environment, but it helps maintaining strong isolation so maybe it's worth it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@crohr @jesseduffield
0