johnrharris

Thank you, and please accept my apology for the slow reply. Upgrading to WP Offload Media (Lite) 2.4 made no difference–we still received the same error as posted in our original inquiry. After additional evaluation and testing, however, we discovered that the error appears to be related to our attempted use of IAM Roles to tell WP Offload Media not to ask for or require the access keys. The user guide advises as follows:

…if you host your WordPress site on an EC2 instance you won’t necessarily want to distribute your access credentials onto the instance, and will want to make use of IAM Roles.

It then suggests “After creating an IAM role you can use the ‘AS3CF_AWS_USE_EC2_IAM_ROLE’ constant to tell WP Offload Media not to ask for or require the access keys…preferable with:”

define( 'AS3CF_SETTINGS', serialize( array(
    'provider' => 'aws',
    'use-server-roles' => true,
) ) );

By dispensing with this recommended approach and instead defining access keys within wp-config.php uisng the directive below, the plugin began behaving as expected:

define( 'AS3CF_SETTINGS', serialize( array(
    'provider' => 'aws',
    'access-key-id' => '********************',
    'secret-access-key' => '**************************************',
) ) );

We use Cloudflare in front of our EC2 instance and did experiment with disabling Cloudflare’s proxy feature while we were still attempting to connect to S3 using the IAM Role constant, but that appeared to make no difference.

If we can be of further assistance with this, please let us know. We will mark this matter as “resolved” since we do have a work-around.

Thank you for your help. The reboot, unfortunately, did not improve matters. I would be grateful for any other suggestions.