Hi,
I am replying to my own post. I found the solution. The key is to use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY rather than ACCESS_KEY_ID and SECRET_ACCESS_KEY. So that is different than my development environment which was happy with ACCESS_KEY_ID and SECRET_ACCESS_KEY.
I got the idea of using the AWS_ prefixed environment variable names from the question: Cannot load security credentials for AWS SDK. I think my previous attempts at searching for an answer on this forum were hindered by my including “rails” in my search terms. Going with just “AWS” got me on the path to finding the solution.
If someone could comment on why the environment variables changed names going from Development to Production I would greatly appreciate it.
Thanks,
Dennis