Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter honorconsulting

    (@honorconsulting)

    Leon,

    I really appreciate the assist.

    For anyone reading this, once you have a user that has the proper access levels to S3 and Cloudfront, which can be an IAM user or your root user, this just means that you need to check your settings in S3 > bucketname.com > Permissions > Block Public Access. Once there, you need to make sure that both of the options that control ACLs are both switched off.

    All is working well now. Thank you!

    Thread Starter honorconsulting

    (@honorconsulting)

    Hi Mark. Thanks for the response. Yes, I’ve seen that documentation and am following those instructions. Also, I’ve checked the logs to make sure that the S3 endpoint and protocols all match up. I have also primed the S3 bucket with the directory folder in case that was the issue, which it appears not to be.

    Please let me know if you have any other suggestions. Thank you!

    Thread Starter honorconsulting

    (@honorconsulting)

    Yes, I’m realizing that it would not be feasible to separate these two. Instead, I am going to exclude anything but foundational CSS (theme and child), so that it will be minified, but not aggregated, and intercept plugin styles through functions to load a “plugin child stylesheet”, so that small changes to plugin specific classes etc. won’t end up changing autoptimize hashes across the entire site when it really only affects a few individual pages. Static is Cloudfront running on HTTP/2 so this should keep things dynamic, but with little impact on performance. The only reason I’m fussing with this is to reduce the amount of time it takes to deploy. Less changes to HTML means I can take advantage of the iterative features of WP2Static and deploy faster for small changes.

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