Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CREATE_FAILED when running "cdk deploy"

See original GitHub issue

Hi, I am new to CDK and considering using it. I am trying to get the AppSyncGraphQLDynamoDB example working. When I run cdk deploy I get the following error:

  0/12 | 08:47:22 | CREATE_IN_PROGRESS   | AWS::IAM::Role              | ItemsDynamoDBRole (ItemsDynamoDBRole7D2E3F6D) 
  0/12 | 08:47:22 | CREATE_IN_PROGRESS   | AWS::IAM::Role              | ItemsDynamoDBRole (ItemsDynamoDBRole7D2E3F6D) Resource creation Initiated
  0/12 | 08:47:22 | CREATE_IN_PROGRESS   | AWS::DynamoDB::Table        | ItemsTable (ItemsTable5AAC2C46) Resource creation Initiated
  1/12 | 08:47:22 | CREATE_FAILED        | AWS::IAM::Role              | ItemsDynamoDBRole (ItemsDynamoDBRole7D2E3F6D) ARN arn:aws:iam::aws:policy/arn:aws:iam::aws:policy/AmazonDynamoDBFullAccess is not valid. (Service: AmazonIdentityManagement; Status Code: 400; Error Code: InvalidInput; Request ID: fda7a95a-aaca-11e9-8b34-71c203c1eb46)
        new Role (/home/ec2-user/environment/kloudkrypt/node_modules/@aws-cdk/aws-iam/lib/role.js:30:22)
        \_ new AppSyncCdkStack (/home/ec2-user/environment/kloudkrypt/index.js:50:32)
        \_ Object.<anonymous> (/home/ec2-user/environment/kloudkrypt/index.js:130:1)
        \_ Module._compile (module.js:653:30)
        \_ Object.Module._extensions..js (module.js:664:10)
        \_ Module.load (module.js:566:32)
        \_ tryModuleLoad (module.js:506:12)
        \_ Function.Module._load (module.js:498:3)
        \_ Function.Module.runMain (module.js:694:10)
        \_ startup (bootstrap_node.js:204:16)
        \_ bootstrap_node.js:625:3

Any suggestions?

Thanks, -Derek

Issue Analytics

State:
Created 4 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

derektumulakcommented, Jul 24, 2019

Thanks Joseph. I’ll take a look at your suggestion.

Best, Derek

On Jul 24, 2019, at 2:14 PM, Joseph Chiocchi notifications@github.com wrote:

@derektumulak I get the same error as you. see #78 if you want a workaround for that example until @rhboyd comments in that PR are addressed

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

0reactions

NGL321commented, Nov 14, 2019

It looks like the initial bug discovered here was resolved in #86, and the second bug is encapsulated under #78.

I am going to close this issue for now as resolved. Feel free to re-open if I am incorrect.

😸