Font Deployment — PulseID Clusters
How fonts reach the serving fleet. Hand to anyone adding fonts.
- S3 source of truth:
s3://securedownload.pulsemicro.com/pulseid/fontpacks/<Alias>/ - Clusters: Saas1, Saas2, Saas6, Saas7 · Account
602113171834/us-east-1
Add a font
- Upload the file to the cluster's S3 fontpack, in the right subfolder:
.FONVivx/DG embroidery →app/.ttf/.otftext (print templates) →windows/- style files →
styles/
- That's it. Within ~30 min the pipeline does the rest automatically.
Two things that silently break it:
- Case:
<Alias>is capitalised and must match exactly —Saas6, notsaas6. - Prefix: wrong subfolder = the app can't find the font.
What happens automatically
The check runs at :00 and :30 every hour. When a cluster's fontpack has changed, FontGoldRollout (SSM Automation):
- installs the font on every running box (live immediately),
- bakes a new gold AMI so future / replaced boxes have it permanently (no fleet restart),
- installs again to catch any box that launched during the bake,
- mirrors the font into the matching stage fontpack.
Watch the PulseID › General Teams channel for "Gold bake started / finished" (or FAILED). If nothing changed in the fontpack, it is a silent no-op.
Mid-copy is safe. The run skips any fontpack touched in the last 5 minutes — so if you're still copying (or just finished) after :55 or :25, that :00/:30 run leaves your batch alone and the next scheduled run (30 min later) picks it up. It never bakes a half-copied set. Finish a copy a few minutes before :00/:30 and it goes on that run.
Gold is now the source of truth — there are no more 30-min State Manager associations. A fresh instance gets every font from the baked image.
Don't want to wait for :00/:30?
Normally you just wait — the next scheduled run (≤30 min) handles it. There is no self-service force button; the team's job is upload-and-wait.
Forcing a run is ops-only — it needs the Tsoft-ITOpsRole (not CloudShell / a normal login), because it requires ssm:StartAutomationExecution and iam:PassRole on SSMServiceRole. After assuming that role:
aws ssm start-automation-execution --document-name FontGoldRollout \
--parameters 'Cluster=Saas6'
It still no-ops if the fontpack hasn't changed (or is inside the 5-min settle window).
Verify a font landed on the boxes
# newest InstallFonts runs on a box
aws ssm list-command-invocations --instance-id <id> --filters "key=DocumentName,value=InstallFonts" \
--query "sort_by(CommandInvocations,&RequestedDateTime)[-3:].{When:RequestedDateTime,Status:Status}" --output table
# what the last run installed
aws ssm list-command-invocations --instance-id <id> --filters "key=DocumentName,value=InstallFonts" --details \
--query "CommandInvocations[-1].CommandPlugins[-1].Output" --output text | grep -i "download:"
"Font X could not be found": confirm the file is in S3 under the right cluster / prefix / case (aws s3 ls .../<Alias>/app/), then start the bake above and watch Teams for "finished".
Notes
- Saas1Blue is excluded (being retired) — it has no auto-gold.
- A gold bake takes a while; if two fonts are added close together they ride the same bake. A failed bake retries on the next 30-min tick (watch for a FAILED message in Teams).