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 Dec 9, 2024. It is now read-only.
Hi Daniel. First off, thanks for trying out Desktop -- your feedback is greatly appreciated.
Secondly, I'm sorry about the error! I believe I see what is happening. Here's some more context: Desktop asks to create a brand new IAM role, with limited permissions. On our side, we create this role as a Provider. This is the new credential mechanism that our framework uses. It appears that this Provider was incorrectly marked as default, which means that if not specified otherwise, this credential will get used for all deployments.
I went ahead and unset the Desktop Provider as default. So, you should be good to go now.
For the record, we had this happen to us too. Our serverless deployments via GitHub Actions stopped working. Debugging found the new IAM role had insufficient permissions.
Very surprised to see that beta Serverless Desktop role being used by our Production deployments!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While installing Desktop it had me approve a new cloudstack thingy and now my CircleCI jobs fail when deploying functions:
An error occurred: CustomDashresourceDashapigwDashcwDashroleLambdaFunction - AccessDenied. User doesn't have permission to call iam:GetRole.
This seems not good :(
The text was updated successfully, but these errors were encountered: