#10144 AWS: cannot read an error when provisioning an instance
Closed: Fixed 2 years ago by guyinger. Opened 2 years ago by guyinger.

While provisioning an instance on EC2 from a costume AMI, it fails and I get the following error:
"You are not authorized to perform this operation. Encoded authorization failure message: nvc4oX5JgUCGOG2Nyu9jRaw8ejIGxjxETOZ8QgSW1mDwSV65OqvSI8uI-J7FEI2_uPXYYOUow8APK8KNyteAMXCyAe2v7qaDXwJyl6_o8_dfpdaHUTb2bZ8JcVOuD6kcgvSd19symDMwF2tvsnIb5l7IKSkjz0Sq5gsyCcdLBPpll-6XAL5qC049K0zqs13xuM9_WYmSytzIItYfBewxbNsLP1KDLS7_AhSzNxOS7vyYXKzQKZDelD3Z9CSQZrVobYZNxed5_dowL994KRy32E3APIA5segTkGiZEAjq5374amWrOKA0rX7EDN05swaBdImaaEoAFBF2NrOvD9032Vx-vgeOCW9NE16Ch7lV-510J96Br-lQgo3ojR-XCr6-CzS_m_f0ejuLpkMJEywON3PM_xnwgcNYrlJjR4y_CwqDL9ou1R3Uf-3jw3HYCwS1szljzRE_pUjIafbL5exmBnI9Juxq3RuHOQ0oFTBa85e0d7EEUU4d9Dw60ToRS4So0hvpJWm87pcfLcJf2bGXbIEjUm5WKAXnVCr9LEiK8YU2x4lMsexb3YL0DXs-_aBe4beswSu75MFFW-vdmsHhy5VUWIrqlhmb3BWn-fwFumDo0SYuYnFxpTFR9ulrfJd3UPwPqwV8qHzWkKD_CW4yfK9iD1WEhg"

I am not able to know if it's a problem in the AMI, permissions..etc. so it's impossible to sort it out.

CC @mvadkert


It was a permission error: "action": "ec2:RunInstances"

I have added that permission, hopefully that will be enough but often you will need a couple of permissions in one go. What are you running to get the error?

Metadata Update from @mobrien:
- Issue assigned to mobrien

2 years ago

@guyinger can you pls recheck

@mobrien nothing special, just boot an ARM VM from our private image.

@mobrien nothing special, just boot an ARM VM from our private image.

That should be fine so. RunInstance is the permission to create instances from a non standard AMI

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

@mobrien thanks for the info, need to check what is non standard AMI ...

@guyinger can you confirm it now works so we can close this pls?

I confirm, it seems to be working now. Thanks.

@mobrien @mvadkert

Metadata Update from @guyinger:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Done