Skip to content

Use unversioned S3 bucket and move S3 path to config#45

Merged
kimandrews merged 5 commits into
mainfrom
update-s3-bucket-params
Feb 5, 2026
Merged

Use unversioned S3 bucket and move S3 path to config#45
kimandrews merged 5 commits into
mainfrom
update-s3-bucket-params

Conversation

@kimandrews
Copy link
Copy Markdown
Collaborator

@kimandrews kimandrews commented Jan 28, 2026

Description of proposed changes

  • Switch S3 caching from nextstrain-data bucket to nextstrain-data-unversioned bucket since versioning is not needed for the tbprofiler and snippy outputs
  • Move the full S3 destination path (bucket + prefix) to the config rather than defining the prefix in multiple scripts
  • Rename s3_bucket config option to s3_dst_unversioned with this reasoning:
    • _dst because it now contains the full destination path, not just the bucket name
    • _unversioned because we want to reserve the s3_dst parameter name for future changes that will upload build metadata and VCF to nextstrain-data

Related issue(s)

Closes #41
Closes #43

Checklist

  • Checks pass
  • Copy snippy and tbprofiler data from old bucket (nextstrain-data) to new bucket (nextstrain-data-unversioned)
  • Update changelog

@kimandrews kimandrews marked this pull request as ready for review January 29, 2026 00:55
* Makes the S3 path configurable in just one place rather than hardcoded in multiple scripts.
* Renames s3_bucket to s3_dst_unversioned since it now contains the full destination path, not just a bucket name.
@kimandrews kimandrews force-pushed the update-s3-bucket-params branch from 460cc03 to 882d565 Compare January 30, 2026 01:09
Comment thread build-configs/nextstrain-automation/config.yaml Outdated
This makes the format consistent between s3_dst_unversioned and deploy_url
Copy link
Copy Markdown
Contributor

@joverlee521 joverlee521 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good from inspection, just need to test.

- build-configs/nextstrain-automation/deploy.smk

s3_dst_unversioned: "s3://nextstrain-data-unversioned/files/workflows/tb/"
s3_dst_unversioned: "s3://nextstrain-data-unversioned/files/workflows/tb"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As part of this change, I also deleted the bad files that were uploaded in the trial run as discussed in Slack.

aws s3 rm s3://nextstrain-data-unversioned/files/workflows/tb// --recursive

Copy link
Copy Markdown
Contributor

@joverlee521 joverlee521 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to merge after latest trial run.

@kimandrews kimandrews merged commit de2be87 into main Feb 5, 2026
7 checks passed
@kimandrews kimandrews deleted the update-s3-bucket-params branch February 5, 2026 04:02
@joverlee521
Copy link
Copy Markdown
Contributor

Scheduled automated run worked as expected. Will need to follow up to clean up files on the versioned S3 bucket.

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.

Move s3 path prefix from shell scripts to config Use an unversioned AWS S3 bucket for tbprofiler and snippy outputs

2 participants