https://github.com/inceptionstack/lowkey/blob/main/bootstraps/telegram/BOOTSTRAP-TELEGRAM.md instruct to create Secret Manager as follow:
aws secretsmanager create-secret \ --name /faststart/telegram-bot-token \ --secret-string "YOUR_BOT_TOKEN_HERE" \ --region us-east-1
However, this prevent openclaw gateway to restart as the secret id cannot contain /
09:01:17 [gateway] loading configuration…
09:01:18 [gateway] resolving authentication…
09:01:18 [gateway] starting...
09:01:20 [secrets] [SECRETS_RELOADER_DEGRADED] Error: Exec secret reference id must match /^[A-Za-z0-9][A-Za-z0-9._:/-]{0,255}$/ and must not include "." or ".." path segments (example: "vault/openai/api-key"). (ref: exec:aws-sm:/faststart/telegram-bot-token).
09:01:20 [gateway] wrote stability bundle: /home/ec2-user/.openclaw/logs/stability/openclaw-stability-2026-05-13T09-01-20-392Z-4882-gateway.startup_failed.json
Gateway failed to start: Error: Startup failed: required secrets are unavailable. Error: Exec secret reference id must match /^[A-Za-z0-9][A-Za-z0-9._:/-]{0,255}$/and must not include "." or ".." path segments (example: "vault/openai/api-key"). (ref: exec:aws-sm:/faststart/telegram-bot-token).
Recreating the secret without the leading / in the id fixed the issue.
https://github.com/inceptionstack/lowkey/blob/main/bootstraps/telegram/BOOTSTRAP-TELEGRAM.md instruct to create Secret Manager as follow:
aws secretsmanager create-secret \ --name /faststart/telegram-bot-token \ --secret-string "YOUR_BOT_TOKEN_HERE" \ --region us-east-1However, this prevent openclaw gateway to restart as the secret id cannot contain
/Recreating the secret without the leading
/in the id fixed the issue.