-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS credentials issue on stable #1714
Comments
We had changed creds and not updated on stable, so made new keys, let's reboot and see! |
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:
|
I don't think the above is relevant, we have been on aws-sdk-s3 for a few years it seems.
|
We just got staging working, by standardizing all references of Strange because it was working in production in Google Cloud, where it drew on a stored 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 |
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. |
We tried deploying to production but got:
|
Will try setting this here: Line 48 in da8ec9d
|
* up node to v16 for webgpu in #1714 * Delete .travis.yml * gitpod
* up node to v16 for webgpu in publiclab#1714 * Delete .travis.yml * gitpod
After publishing #1712, I'm seeing a 500 upon uploading images:
The text was updated successfully, but these errors were encountered: