This simple action uses the vanilla AWS CLI to sync a directory (either from your repository or generated during your workflow) with a remote S3 bucket.
Place in a .yml
file such as this one in your .github/workflows
folder. Refer to the documentation on workflow YAML syntax here.
name: Sync Bucket
on: push
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@master
- name: Upload binary to S3 bucket
uses: aws-robotics/aws-robomaker-github-actions/[email protected]
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
AWS_REGION: 'eu-central-1'
AWS_S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
FILES: 'file1.txt file2.txt file3.txt'
with:
args: --acl public-read
Key | Value | Type | Required |
---|---|---|---|
FILES |
The local file(s) you wish to upload to S3. For example, ./myfile.txt . |
env |
Yes |
DEST |
The key name of destination S3 object in the bucket. For example, dest_folder/ or dest_file.txt . |
env |
No |
AWS_REGION |
The region where you created your bucket in. For example, eu-central-1 . Full list of regions here. |
env |
Yes |
The following variables should be added as "secrets" in the action's configuration.
Key | Value | Type | Required |
---|---|---|---|
AWS_S3_BUCKET |
The name of the bucket you're syncing to. For example, golang-deployment-bucket . |
secret |
Yes |
AWS_ACCESS_KEY_ID |
Your AWS Access Key. More info here. | secret |
Yes |
AWS_SECRET_ACCESS_KEY |
Your AWS Secret Access Key. More info here. | secret |
Yes |
This project is a fork of jakejarvis/s3-sync-action. It is distributed under the MIT license.