Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter jbuscema

    (@jbuscema)

    @streetfight_888 I needed to use a slightly different policy to resolve the issue. The other issues I was having where resolved in one of the latest updates. Here is the policy I am using that works:

    {
    “Version”: “2012-10-17”,
    “Statement”: [
    {
    “Sid”: “Permissions1”,
    “Effect”: “Allow”,
    “Action”: [
    “s3:HeadBucket”,
    “polly:DescribeVoices”,
    “polly:GetLexicon”,
    “polly:PutLexicon”,
    “polly:SynthesizeSpeech”,
    “polly:ListLexicons”
    ],
    “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*”
    }
    ]
    }

    Thread Starter jbuscema

    (@jbuscema)

    @tstachlewski I was able to get it working by changing the policy a bit. The policy I used is different from the one in the doc. Below is the policy I am using now that solved the issue. Additionally, a few of the other issues that were preventing me from using the plugin were resolved in the latest update.

    {
    “Version”: “2012-10-17”,
    “Statement”: [
    {
    “Sid”: “Permissions1”,
    “Effect”: “Allow”,
    “Action”: [
    “s3:HeadBucket”,
    “polly:DescribeVoices”,
    “polly:GetLexicon”,
    “polly:PutLexicon”,
    “polly:SynthesizeSpeech”,
    “polly:ListLexicons”
    ],
    “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*”
    }
    ]
    }

    Thread Starter jbuscema

    (@jbuscema)

    @smb-dev @tstachlewski @awslabs Wondering if you have any update on my issue. I was able to log into the AWS console using my IAM user I setup per the guide. I cleared cache on my server and even restarted apache, but I still have the “Please verify your AWS Credentials are accurate” message in WordPress. Again, I followed the setup guide and policy creation exactly. Not sure what else I can do.

    Thread Starter jbuscema

    (@jbuscema)

    @smb-dev I followed the guide to the T and checked my policy. It’s correct and I am using the correct secret/access but still have the same problem. I also restarted apache, cleared cache, etc. Still getting the same error message.

    Thread Starter jbuscema

    (@jbuscema)

    Tomasz,

    I am using programmatic. I don’t see an email from you but I am happy to discuss offline.

    Jason

    Thread Starter jbuscema

    (@jbuscema)

    The policy that is in the documentation doesn’t seem to be accurate. I quickly changed the policy to full admin and I was able to log into S3, but the plugin still did not work with the updated full admin policy. Obviously I would not keep it that way but I just want to test it out. Not sure what I am doing wrong.

    Policy I attached to the wordpress user:

    {
    “Version”: “2012-10-17”,
    “Statement”: [
    {
    “Sid”: “Permissions1”,
    “Effect”: “Allow”,
    “Action”: [
    “s3:HeadBucket”,
    “polly:SynthesizeSpeech”,
    “polly:DescribeVoices”
    ],
    “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*”
    }
    ]
    }

Viewing 6 replies - 1 through 6 (of 6 total)