gherkai-deploy-aws
gherkai 的 AWS 部署 provider：一条命令在你自己的 AWS 账户里建齐 gherkai --backend cloud 所需的资源——运行状态表、事件表、产物桶、Fargate 集群、镜像仓库、让 run 在云端自动推进的后台组件、网络与最小权限角色——并把官方 worker 基础镜像同步进你账号的镜像仓库、登记成名为 base 的默认镜像（自己 build 的定制镜像用 gherkai deploy push-worker 推）。
装上它，gherkai deploy 与 gherkai destroy 才能真正执行，并带上 --vpc、--stop-timeout、--container-engine 等部署选项；没装时这两条命令仍在帮助里，运行会提示先装 gherkai[deploy-aws] 并以退出码 2 结束。只有部署方需要装，团队里只提交 run 的人不必装。
安装
uv tool install 'gherkai[deploy-aws]' # 随命令行的 extra 安装，需 Python ≥ 3.13
部署机上还需要 Node ≥ 22 在 PATH 上（底层用 AWS CDK）与容器引擎 docker（拉取官方 worker 基础镜像并推送到你账号的 ECR）。
最小用法
gherkai deploy --vpc default --prefix gherkai- # 建或更新云端后端
gherkai destroy --vpc default --prefix gherkai- # 拆掉后端；数据类资源保留
destroy 不删数据类资源：两张 DynamoDB 表、产物桶与镜像仓库都保留，防止误删历史与镜像。它们需要手动清理，用同一前缀重新部署前尤其要注意。
--vpc 必给，没有隐式默认；--prefix 不给时用默认 gherkai-，给了则须与提交侧 gherkai run / submit 的 --prefix 一致。三种 VPC 取值、某个 account 与 region 第一次要执行的 gherkai deploy --bootstrap、用 gherkai deploy --diff 预览将要改动哪些资源、以及拆除后的手动清理步骤，见云端后端文档：https://github.com/zhiyanliu/gherkai/blob/HEAD/docs/user-guide/cloud-backend.md 。
文档
- 部署、升级、worker 镜像与清理的完整流程：https://github.com/zhiyanliu/gherkai/blob/HEAD/docs/user-guide/cloud-backend.md
- 环境变量与选项总表：https://github.com/zhiyanliu/gherkai/blob/HEAD/docs/user-guide/configuration.md
- 报错了先看哪：https://github.com/zhiyanliu/gherkai/blob/HEAD/docs/user-guide/troubleshooting.md
- 每版变更：https://github.com/zhiyanliu/gherkai/blob/HEAD/CHANGELOG.md
1 maintainer
Metadata
1 maintainer
Release files for gherkai-deploy-aws 1.4.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gherkai_deploy_aws-1.4.8.tar.gz | 86.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gherkai_deploy_aws-1.4.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 178.8 kB
Release files / gherkai_deploy_aws-1.4.8.tar.gz
| Download URL | gherkai_deploy_aws-1.4.8.tar.gz |
|---|---|
| Size | 86.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58a1aab1b28a24675fc9256705a5615b6e2ef815f542c6e3f112ae87813f4df4
|
|
BLAKE2b-256 checksum How to use checksums |
c3578c2f75787dab9e706c01d4e22a24da7086847370663812f89ab87bc20e7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / gherkai_deploy_aws-1.4.8-py3-none-any.whl
| Download URL | gherkai_deploy_aws-1.4.8-py3-none-any.whl |
|---|---|
| Size | 92.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba21cea53e302d39e83e89c8c814842de55e5812ce9d5eda111e8f5d6ddc1037
|
|
BLAKE2b-256 checksum How to use checksums |
58e16d08e7b2f1d599ed2ab4a8a0f7366f9ca5a4c43dda3239a1111c52e1783a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log
