Skip to content
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

Add Region: Resolve missing Key fatal error #29

Closed
wants to merge 1 commit into from

Conversation

AgentGoldPaw
Copy link

@AgentGoldPaw AgentGoldPaw mentioned this pull request Apr 17, 2021
@balexander
Copy link

Thanks for this fix. Any idea when this will get merged in?

@AgentGoldPaw
Copy link
Author

No idea. But if you need something for s3. I can post the workaround I have been using. The aws-sdk is included in actions so you can just use the regular sdk.

@balexander
Copy link

@drpym Thanks, I'd appreciate if you could post the work around

@AgentGoldPaw
Copy link
Author

AgentGoldPaw commented Apr 22, 2021

@balexander here you are

  - name: upload
     run: AWS_ACCESS_KEY_ID=${{secrets.AWS_ACCESS_KEY}} AWS_SECRET_ACCESS_KEY=${{secrets.AWS_SECRET_KEY}} aws s3 cp ./myfile.txt s3://${{bucketName}}/myFile.txt
     working-directory: /dir/where/file/is/

@AgentGoldPaw
Copy link
Author

AgentGoldPaw commented Apr 22, 2021

@balexander something to note: If you ubuntu-latest it will error out.
set

  os: [ubuntu-18.04]

sorry for another message, just wanted to make sure you saw this. You can also just AWS_REGION=region-here before aws and it should work on latest.

@woodyhayday
Copy link

Just to add here, changing os to [ubuntu-18.04] and using the mod @golden-protocol mentions:

  - name: upload
     run: AWS_ACCESS_KEY_ID=${{secrets.AWS_ACCESS_KEY}} AWS_SECRET_ACCESS_KEY=${{secrets.AWS_SECRET_KEY}} aws s3 cp ./myfile.txt s3://${{bucketName}}/myFile.txt
     working-directory: /dir/where/file/is/

... works for me.

Though I'm not certain this, (or #27), is a region bug, as I get it with one of two buckets in the same region. I wondered if it's because of the public/no public access?:
Screenshot 2021-11-01 at 15 01 57

... either way, thanks for the helpful workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants