Skip to content

Update AWS CLI to v2#287

Merged
joverlee521 merged 1 commit into
masterfrom
aws-v2
Jun 24, 2026
Merged

Update AWS CLI to v2#287
joverlee521 merged 1 commit into
masterfrom
aws-v2

Conversation

@joverlee521

@joverlee521 joverlee521 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Description of proposed changes

We are wanting to use AWS CLI features that are only available in v2.¹ In the last attempt to upgrade AWS, the main blocker was the fact that AWS_DEFAULT_REGION is now required.² For Nextstrain workflows, this is now mitigated by the fact that the shared pathogen-repo-build GH Action workflow sets the envvar.³ We have also been using awscli >= 2 in conda-base without any issues.⁴

¹ nextstrain/infra#72 (comment)
² #214 (comment)
³ https://github.com/nextstrain/.github/blob/5b32fb95e6613823e9cc12e06beec164503980f4/.github/workflows/pathogen-repo-build.yaml#L303
https://github.com/nextstrain/conda-base/blob/dc99d69d91420da760519d54be051452744351f4/src/meta.yaml#L54

Related issue(s)

Resolves #216

Checklist

  • Checks pass
  • Update changelog

We are wanting to use AWS CLI features that are only available in v2.¹
In the last attempt to upgrade AWS, the main blocker was the fact that
`AWS_DEFAULT_REGION` is now required.² For Nextstrain workflows,
this is now mitigated by the fact that the shared pathogen-repo-build
GH Action workflow sets the envvar.³ We have also been using awscli >= 2
in conda-base without any issues.⁴

¹ <nextstrain/infra#72 (comment)>
² <#214 (comment)>
³ <https://github.com/nextstrain/.github/blob/5b32fb95e6613823e9cc12e06beec164503980f4/.github/workflows/pathogen-repo-build.yaml#L303>
⁴ <https://github.com/nextstrain/conda-base/blob/dc99d69d91420da760519d54be051452744351f4/src/meta.yaml#L54>
@joverlee521 joverlee521 marked this pull request as ready for review June 22, 2026 18:22
@joverlee521

Copy link
Copy Markdown
Contributor Author

Will merge and release this tomorrow if there's no feedback.

@victorlin victorlin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Checked PR image:

$ nextstrain shell --image nextstrain/base:branch-aws-v2 ~/tmp -c 'aws --version'
Entering the Nextstrain runtime (docker)

aws-cli/2.35.7 Python/3.14.5 Linux/6.12.76-linuxkit exe/aarch64.debian.12

Comment thread Dockerfile
Comment on lines +214 to +215
# Using `xx-info march` to translate amd64 -> x86_64 and arm64 -> aarch64
# based on https://github.com/docker/buildx/discussions/2001

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nice find, this can probably replace builder-scripts/target-triple elsewhere.

Comment thread Dockerfile
# Using `xx-info march` to translate amd64 -> x86_64 and arm64 -> aarch64
# based on https://github.com/docker/buildx/discussions/2001
RUN XX_MARCH=$(xx-info march) \
&& curl -fsSL --proto '=https' "https://awscli.amazonaws.com/awscli-exe-linux-${XX_MARCH}.zip" -o "awscliv2.zip" \

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We have also been using awscli >= 2 in conda-base without any issues.

I'm guessing there's a good amount of AWS CLI usage not captured by pathogen repo CI (e.g. upload-to-s3), but we can just merge and monitor.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No obvious errors in today's pathogen workflows, will continue to monitor the rest of the week.

@joverlee521 joverlee521 merged commit a695dae into master Jun 24, 2026
74 checks passed
@joverlee521 joverlee521 deleted the aws-v2 branch June 24, 2026 17:02
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.

Revisit updating AWS CLI to v2

2 participants