AWS credentials issue on stable about mapknitter HOT 7 OPEN

We had changed creds and not updated on stable, so made new keys, let's reboot and see!

from mapknitter.

Didn't work -- i do see this though, maybe we missed something? But it is working on production so i'm not sure why this wouldn't work:

Post-install message from paperclip:
##################################################
#  NOTE FOR UPGRADING FROM 4.3.0 OR EARLIER      #
##################################################

Paperclip is now compatible with aws-sdk-s3.

If you are using S3 storage, aws-sdk-s3 requires you to make a few small
changes:

* You must set the `s3_region`
* If you are explicitly setting permissions anywhere, such as in an initializer,
  note that the format of the permissions changed from using an underscore to
  using a hyphen. For example, `:public_read` needs to be changed to
  `public-read`.

For a walkthrough of upgrading from 4 to *5* (not 6) and aws-sdk >= 2.0 you can watch
http://rubythursday.com/episodes/ruby-snack-27-upgrade-paperclip-and-aws-sdk-in-prep-for-rails-5

from mapknitter.

I don't think the above is relevant, we have been on aws-sdk-s3 for a few years it seems.

Aws::Sigv4::Errors::MissingCredentialsError is exact - i checked AWS logs and there was no access at all. Why isn't it picking up the keys?

from mapknitter.

We just got staging working, by standardizing all references of AWS_ACCESS_KEY_ID -- it had been missing _ID in: amazon_s3.yml and mapknitter.env.

Strange because it was working in production in Google Cloud, where it drew on a stored app.yaml file that used _ID.

But now strangely AWS console says images are being uploaded (from stable, i believe, based on having done so in the timeframe successfully) but NOT using the newly made key we put in environment.sh. So is there another place it could be getting the key?

from mapknitter.

OK, no, correction - the new key IS being used. the access log must have been slow to load. It shows usage within a minute of my successful upload to staging. So that seems all good.

The only question now is whether we will break things upon deploying MK, by having changed some env var names in a working system.

from mapknitter.

We tried deploying to production but got:

error [email protected]: The engine "node" is incompatible with this module. Expected version ">= 13.0.0". Got "12.22.5"

from mapknitter.

Will try setting this here:

from mapknitter.