AI Text-to-Speech using AWS Polly

Yes. You need AWS credentials with access to the AWS Polly APIs that the plugin uses.

Yes. The plugin supports storing generated audio in Amazon S3 and serving it through Amazon CloudFront.

Yes. You can enable audio generation for individual posts and the plugin will keep track of queued, running, and ready states.

Yes. This is optional; a single WordPress site does not need any of the changes described below. A site copy is another WordPress installation, for example a test or staging copy. Each installation can use a separate S3 bucket while sharing AWS access with other installations. Enter only that installation's bucket name in its plugin settings. For the simplest shared setup, reuse the same IAM user and access key in each installation. Edit the existing WordPressPollyPlugin customer managed policy instead of creating another policy. Add every bucket to CheckAudioBucket by replacing its single Resource value with an array of bucket ARNs: "Resource": [ "arn:aws:s3:::FIRST-BUCKET-NAME", "arn:aws:s3:::SECOND-BUCKET-NAME" ] In ManageGeneratedAudio, use a matching array of object ARNs, each ending in /*: "Resource": [ "arn:aws:s3:::FIRST-BUCKET-NAME/*", "arn:aws:s3:::SECOND-BUCKET-NAME/*" ] Add both ARN forms for every additional bucket. All installations using this IAM user can access every bucket listed in the policy. Changing or rotating the shared access key requires updating every installation that uses it. The same customer managed policy can also be attached to multiple IAM users, so a new policy is not required for every user. However, every attached user receives access to all buckets listed in that policy, and later policy changes affect all attached users. Sharing one IAM user and policy is possible across different websites or projects. For unrelated projects, production sites, or sites managed by different people, separate IAM users, access keys, and policies limit the effect of an exposed credential or an accidental policy change. This separation is optional and is not required for a basic one-site setup. The public-read bucket policy from configuration step 8 is different from the IAM policy. A bucket policy is saved on one specific bucket, so repeat step 8 for each additional bucket and replace YOUR-BUCKET-NAME with that bucket's own name. The same policy template can be copied, but one saved bucket policy cannot be attached to several buckets. If an installation changes buckets, keep its old bucket ARNs in the IAM policy until the previously generated audio has been removed. Cleanup uses the bucket recorded when each audio file was generated. Official IAM managed-policy reference: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html