Closed armenr closed 3 years ago
Update:
If you are using amplify admin UI as your means of authentication, THAT creates this unexpected behavior. That is to say, maybe the docs should reflect the fact that using this plugin/successfully pushing the resources it creates is ONLY achievable when you are using a named AWS profile OR access key/secret key...Amplify Admin UI won't allow it because the admin UI creates that stupid role with the missing permissions, and will throw errors every bloody time.
Yeah this is a common occurrence. I will try to see what the console team can do to make this process smoother. We have seen this issue crop up before:
Going to keep this ticket open and work with @renebrandel to see what we can do to help users with this!
Also updated wiki with this answer for future reference answer can be found here: https://github.com/awslabs/amplify-video/wiki/Troubleshooting
@wizage - YOU, sir, are a scholar and a gentleman. I thank you for swift response and help :)
I will look into the issues you referenced. This is great stuff to know, and I am most grateful!
Describe the bug Amplify push fails when adding
amplify video
category.To Reproduce Steps to reproduce the behavior:
npm i amplify-category-video -g
amplify add video
amplify push
ERROR
Expected behavior Expected behavior would be: "Resources built/deployed successfully"
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
amplify --version ---> 4.48.0
Additional context
Each of these backends has Admin UI enabled on them...don't know if that's relevant or not.
Service role configured for the Amplify App: "AmplifyBackendDeployment" -->![Screen Shot 2021-04-16 at 5 53 15 PM](https://user-images.githubusercontent.com/7662191/115097035-c0d35080-9edc-11eb-9893-3e4eb96b52e0.png)
Here's what's really confusing me:
Looks like something, somewhere, is attempting to assume a role that's got insufficient privileges! So, I went into IAM and looked for that role, and found it:
As you can see, this role does not have sufficient privileges to access secretsmanager OR mediaconvert (as described in the amplify-video repo Wiki page for "IAM").
Problems:
Any help would be much appreciated. Thank you! :)