Impossible add IAM role to Amazon CodeCatalyst space
Hi dear support. Could you help to add normal IAM role to Amazon CodeCatalyst space?
When I try to do it, I can see messages
- The IAM role could not be added to your space, roleArn can not be empty
I tried to use 'Create CodeCatalyst development administrator role in IAM' - doesn't work then tried add by 'Add an existing role you have created in IAM' - doesn't work.
I removed and created roles by this page, but it doesn't work https://docs.aws.amazon.com/codecatalyst/latest/userguide/ipa-iam-roles.html#ipa-iam-roles-service-role
Could you help me please with these roles?
- Newest
- Most votes
- Most comments
We're sorry to hear about the issue you've encountered. Our team is actively looking into it. In the meantime, could you please confirm if you were able to add IAM roles to other spaces or if you are facing this issue consistently?
Your input is greatly appreciated.
Relevant content
- asked 3 months ago
- asked 2 years ago
- Accepted Answerasked 10 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 9 months ago
Can you please add some screenshots of your problem?
Did you check if you have any SCPs that probihit you using your CodeCtalyst region?
I have the same problem here. When trying "Create CodeCatalyst development administrator role in IAM" in "Add IAM role to Amazon CodeCatalyst space" screen in AWS Management Console, I got the following error message : The IAM role could not be added to your space roleArn can not be empty It seems there's something wrong with AWS backend API. I could find the 400 status code returned from the following API which was called from AWS management console when I see the developer tool of my web browser: POST https://codecatalyst.us-west-2.amazonaws.com/v1/connections/abc/iam-roles {"roleArn":"arn:aws:iam::abc:role/service-role/CodeCatalystWorkflowDevelopmentRole-abc","authorizationTypes":["SERVICE","RUNNER"],"clientToken":"abc"}
400 Bad Request {"message":"roleArn can not be empty","reason":"CANNOT_PARSE","fieldList":[{"name":"roleArn","message":"roleArn can not be empty"}],"status":400}
Same problem here, even create the policy for role myself didn't work.
"roleArn can not be empty"
I saw the post request actually did send the roleArn(and it's not empty), but get 400 error.