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. The gitc0ffee annotation is unused. |
What happens to a non-conforming artifact
What Index does with a badly named artifact depends on which part of the name is wrong:
| Problem | Example | Result |
|---|---|---|
| The version is not a valid CalVer version | v1.2.3, latest, 2026-07-10 | Silently ignored. No deployment event and no Slack notification are generated. |
| The version is valid, but the annotation or region suffix is not | 2026.07.10.2_emea, 2026.07.10.2_EU, 2026.07.10.2_AMS_EMEA | Not deployed. A visible warning is generated so you can see that the name was rejected. |
If an upload seems to have done nothing and there is no event at all, the version itself was not recognized. Check the version part of the name first.
Holding back a deployment
Every conforming artifact you upload is deployed. There is no tag, annotation, or flag that stages an artifact without deploying it, and an annotation such as -rc.1 does not hold it back. To hold back a deployment, do not upload a conforming artifact until you want it to go live.
Some changes can't be made through auto-deployment. Contact your Index Representative if you need to change any of the following:
Your QPS
Queries Per Second (QPS). The number of bid requests a DSP processes per second. Also known as impressions per second. allocationYour compute resources
Your pod shape
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.
