You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
I use spot instances for runners.
However, after setting GitLabRunnerSpotInstance to "Yes", the manager could not create the new machines and the logs stated that:
Error creating machine: Error in driver during machine creation: Error request spot instance: AuthFailure.ServiceLinkedRoleCreationNotPermitted: The provided
credentials do not have permission to create the service-linked role for EC2 Spot Instances.
I had to add "iam:CreateServiceLinkedRole" for resource "*" to the manager's inline policy "Runners".
I got the information from a related issue: LeanerCloud/AutoSpotting#187
The text was updated successfully, but these errors were encountered:
Hi @fquffio, unfortunately I do not know which service linked role has to be created there. 😆
I just wanted to make it work as quickly as possible and adding the permission above works well.
If you come up with a proper solution, I might test it on our infrastructure.
Looks like AWS creates the AWSServiceRoleForEC2Spot role automatically on the first ever spot instance request.
So, if you make a spot request via aws (web), it will probably solve your problem
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I use spot instances for runners.
However, after setting GitLabRunnerSpotInstance to "Yes", the manager could not create the new machines and the logs stated that:
I had to add "iam:CreateServiceLinkedRole" for resource "*" to the manager's inline policy "Runners".
I got the information from a related issue: LeanerCloud/AutoSpotting#187
The text was updated successfully, but these errors were encountered: