exasol / cloudformation-aws-exasol

MIT License
1 stars 0 forks source link

Template fails with strange error if stack name is too long #3

Open jakobbraun opened 3 years ago

jakobbraun commented 3 years ago

In case the stack name is quite long the stack creation fails with:

INFO    Error run Instances: UnauthorizedOperation: You are not authorized to perform this operation. 
Encoded authorization failure message: 10QnXCrTA5hRImFyyLQio...

Decoded message:

{\"allowed\":false,\"explicitDeny\":false,\"matchedStatements\":{\"items\":[]},\"failures\":{\"items\":[]},\"context\":{\"principal\":{\"id\":\"AROASNN2LAKNXFGVOL57M:exasol-test-setup-abstract-CreateEC2InstanceLambda-d1kdTkFS8Jrf\",\"arn\":\"arn:aws:sts::XXXXXXXX:assumed-role/exasol-test-setup-abstrac-CreateEC2InstanceLambdaR-LGWS28ZCQCJ8/exasol-test-setup-abstract-CreateEC2InstanceLambda-d1kdTkFS8Jrf\"},\"action\":\"iam:PassRole\",\"resource\":\"arn:aws:iam::XXXXXXXX:role/exasol-test-setup-abstraction-ci-exa-EC2RoleDBNode-WGDM0C34NAZ3\",\"conditions\":{\"items\":[{\"key\":\"aws:Region\",\"values\":{\"items\":[{\"value\":\"eu-central-1\"}]}},{\"key\":\"aws:Service\",\"values\":{\"items\":[{\"value\":\"ec2\"}]}},{\"key\":\"aws:Resource\",\"values\":{\"items\":[{\"value\":\"role/exasol-test-setup-abstraction-ci-exa-EC2RoleDBNode-WGDM0C34NAZ3\"}]}},{\"key\":\"iam:RoleName\",\"values\":{\"items\":[{\"value\":\"exasol-test-setup-abstraction-ci-exa-EC2RoleDBNode-WGDM0C34NAZ3\"}]}},{\"key\":\"aws:Account\",\"values\":{\"items\":[{\"value\":\"XXXXXXXX\"}]}},{\"key\":\"aws:Type\",\"values\":{\"items\":[{\"value\":\"role\"}]}},{\"key\":\"aws:ARN\",\"values\":{\"items\":[{\"value\":\"arn:aws:iam::XXXXXXXX:role/exasol-test-setup-abstraction-ci-exa-EC2RoleDBNode-WGDM0C34NAZ3\"}]}}]}}}

The error message is distracting since it sounds like the user had insufficient privileges. However, with a shorter stack name everything works fine.

pj-spoelders commented 3 years ago

I ran into this issue when using taskcat. With a shorter stack name it also worked fine. I'll try to find the root cause of this issue.