2 Answers
- Newest
- Most votes
- Most comments
1
One suggestion from me, ensure you have PartiQL permissions for the User which is logged into the console.
{
"Version":"2012-10-17",
"Statement":[
{
"Effect":"Allow",
"Action":[
"dynamodb:PartiQLInsert",
"dynamodb:PartiQLUpdate",
"dynamodb:PartiQLDelete",
"dynamodb:PartiQLSelect"
],
"Resource":[
"arn:aws:dynamodb:us-west-2:123456789012:table/Music"
]
}
]
}
0
I just asked the person responsible to the aws account to reattach the permissions for the Dynamo. The guy attach the administrator permission for testing purpose and I can confirm the problem was related to permissions. A good feedback to AWS team would be a better error handling for the PartiQL. I know this is a new service and it is very handy but as a recommendation I highly suggest this improvement as nothing was coming up.
answered a year ago
Thanks, I will update the PartiQL team with your feedback.
Relevant content
- asked a day ago
- Accepted Answerasked 7 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 2 years ago
One suggestion from me, ensure you have PartiQL permissions for the User which is logged into the console. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ql-iam.html#access-policy-ql-iam-example1
Can you please check your permission to execute SQL