Webiny Docs home page

Looks like the deployment failed because Pulumi tried to insert a record into a Amazon DynamoDB table, but the record already exists. We’ve seen this happen from time to time, but we’re not sure what’s the exact cause.

The easiest way to resolve this is to delete the record from the table and try running the deployment again, which will allow Pulumi to insert the record without any issues.

To do this, you can use the AWS Console or the AWS CLI. If you’re using the AWS Console, navigate to the Amazon DynamoDB table in question, find the record, and delete it. If you’re using the AWS CLI, you can run the following command:

Make sure to replace <table-name> and <partition-key-value> with the appropriate values for your table.

To find the Amazon DynamoDB table name, run the yarn webiny output core --env <env> command. The table name will be listed in the output.

Reach out to us in our community Slackexternal link channel if you’d like to further investigate this issue. We might be able to identify the root cause and prevent it from happening in the future.