To be able to auto-deploy your container successfully, your image tag and your S3 model folder name must use the following naming convention:
<version>[-<annotation>][_<REGION>]
Version (required). YYYY.0M.0D.MICRO, all numeric: the date the artifact was cut plus a counter that increments for repeat artifacts on the same day, e.g. 2026.07.10.2. Exactly four parts. This is an opinionated variant of CalVer.
Annotation (optional). A hyphen followed by a label such as a commit SHA, ticket, or artifact number (-gitc0ffee). Letters, digits, hyphens, and dots only, no underscores. It is recorded against your deployment events but has no effect on deployment: a label like -rc.1 does not hold an artifact back.
Deployment region (optional). One of _AMS, _EMEA, or _APAC. One region maximum, upper-case only. Omit it to deploy to every region; that bare form is the only way to express "everywhere."
| Suffix | Region |
|---|---|
_AMS | Americas |
_EMEA | Europe, Middle East & Africa |
_APAC | Asia-Pacific |
Examples
| Tag | Result |
|---|---|
2026.07.10.2 | Deploys to every region |
2026.07.10.2_EMEA | Deploys to EMEA only |
2026.07.10.2-gitc0ffee_EMEA | Deploys to EMEA; gitc0ffee is unused |
Only upload artifacts of this format if you intend for them to be deployed.
If an upload seems to have done nothing, check your events: no event at all means the version itself was not recognized and the artifact was ignored. We ignore all artifacts not matching this format.
Note: global deployments overwrite region-specific deployments. A global upload overwrites every region, including one which could be running a region-specific artifact. It is recommended that all artifacts stick to being either global or region-specific to avoid unintended overwrites.
