Invalid principal in policy - "CANONICAL_USER"

This appears to be bug with AWS(https://forums.aws.amazon.com/thread.jspa?threadID=235615) right now. They are working to fix within the next few weeks, but there is a workaround.

The workaround suggested by AWS would be to replace

"Principal": {"CanonicalUser":"dd81f2e5f9fd34f0fca01d29c62e6ae6cafd33079d99d14ad22fbbea41f36d9a"}

to
 
"Principal": { "AWS":"613648124410" }


Please notify us if this doesn't work.

(Additionally we offer the option to use your own IAM user, http://docs.blitline.com/articles/iam_perms.html, if you are interested in that)

Feedback and Knowledge Base