Viewing 8 replies - 1 through 8 (of 8 total)
  • General advice would be to double check the permission policy. Make sure the user does not have other policies attached or is in a group which would limit its permission scope.

    This is the one I have in the ‘PollyForWordPressPolicy’policy (which works for the S3 part)

    
    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Sid": "Permissions1",
                "Effect": "Allow",
                "Action": [
                    "s3:HeadBucket",
                    "polly:SynthesizeSpeech",
                    "polly:DescribeVoices",
                    "translate:TranslateText"
                ],
                "Resource": "*"
            },
            {
                "Sid": "Permissions2",
                "Effect": "Allow",
                "Action": [
                    "s3:ListBucket",
                    "s3:GetBucketAcl",
                    "s3:GetBucketPolicy",
                    "s3:PutObject",
                    "s3:DeleteObject",
                    "s3:CreateBucket",
                    "s3:PutObjectAcl"
                ],
                "Resource": [
                    "arn:aws:s3:::audio_for_wordpress*",
                    "arn:aws:s3:::audio-for-wordpress*"
                ]
            }
        ]
    }
    

    And also reapply the keys.

    Another issue observed is with other plugins that use the aws sdk as isolation between the plugin is an wp issue. if S3 backup plugins are active this may an option, try disabling these and retry. See other posts about this problem set as well.

    Thread Starter kruler69

    (@kruler69)

    Works perfectly, thank you.

    though, I’m not sure it is set up correctly since AWS Polly says in each post below the text editor “Enable Text-To-Speech (Amazon Polly)”. i thought it loads the s3 file from the bucket each time a user plays the player.

    Please check in the settings of Polly the default behavior for generation on new posts.

    Could be that is the issue.

    I’m also suspicious of the new glutenberg editor which is now default in wp501.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi @kruler69 (and thanks @remong for help).
    The plugin itself needs to have got permissions to S3 – it creates the bucket and it saves mp3 files there. When the user ‘play’ the audio it will be delivered from S3 – yes.

    Please let me know if you will have got any other questions.

    Thanks Remong!
    This slightly updated Policy vs the linked Tutorial fixed it for me too. Now the S3 bucket was created.

    • This reply was modified 5 years, 10 months ago by DavidFB.

    I had the same issue which was fixed with the new policy json code. For what it is worth, the policy specified on the WordPress Amazon Polly plugin site is different that what you posted here.
    The policy in these instructions are also different: AWS: Add Voice to WordPress Polly.

    Best Regards,

    Argus

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi, yes. I’m trying to update the tutorial. Sorry for that. The policy is here: https://www.ads-software.com/plugins/amazon-polly/ is proper.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Closing based on above.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Could not create S3 bucket’ is closed to new replies.