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

Do not create AWS policy, role, and instance profile when launching instances #1211

Closed
r4victor opened this issue May 13, 2024 · 0 comments · Fixed by #1212
Closed

Do not create AWS policy, role, and instance profile when launching instances #1211

r4victor opened this issue May 13, 2024 · 0 comments · Fixed by #1212
Assignees
@r4victor
Labels
ux

Comments

@r4victor
Copy link
Collaborator

dstack used to stop instances from within the VM. Because of this, AWS backend still has a legacy code for creating policy, role, and instance profile when launching instances. This code should be removed and minimum AWS permissions should be updated accordingly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@r4victor r4victor

Labels
ux
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not create AWS instance profile when launching instances dstackai/dstack
1 participant
@r4victor