v1.0.10 — one-click CloudFormation deployment
New: one-click deployment (CloudFormation)
This release adds a second deployment path: a single CloudFormation template.
No local toolchain, no long-lived access keys — a browser is all you need.
Download
notiops-webchat.template.jsononly. The three.zipassets are
pulled into a bucket in your account automatically by the stack. You never
need to download them by hand.
- Download
notiops-webchat.template.jsonfrom the assets below. - CloudFormation console → Create stack → Upload a template file.
- Fill in
AdminEmail, tick the IAM acknowledgement, create — measured at ~4.5 minutes. - The stack outputs contain the Web Chat URL. Sign in as
adminwith the temporary
password mailed toAdminEmail(check the junk folder — the sender is
no-reply@verificationemail.com).
Full walkthrough, cost breakdown, upgrade/rollback and one-click teardown:
docs/DEPLOYMENT_ONECLICK.en.md
· 中文
Scope
Included — Web Chat (chat UI + BFF + Bedrock AgentCore agent, read-only by design),
FinOps dashboard on Cost Explorer data, AWS Support case management, AWS documentation Q&A.
Not included — Slack / Feishu bots, scheduled inspections, the admin dashboard,
CUR + Athena billing-detail drill-down, cross-account inspection. For those, use
./setup.sh — see docs/DEPLOYMENT.en.md.
The two paths can be run one after the other on the same account.
Before you create the stack
- Enable Bedrock model access for the Claude models in your chosen region
(us-east-1 or us-west-2 recommended). Without it the stack still reaches
CREATE_COMPLETEand you can log in, but every question fails with
AccessDeniedException— the most common "deployed but unusable". - The account needs egress to
github.comso the stack can fetch these assets. If your
egress allowlist blocks it, mirror the assets to a private S3 bucket and use the
ArtifactBaseUrl+ArtifactMirrorBucketparameters — see §7 of the deployment guide. - Tick "I acknowledge that AWS CloudFormation might create IAM resources".
- The template is ~93 KB, above CloudFormation's 51,200-byte
--template-bodylimit.
From the CLI, upload it to S3 first and pass--template-url.
Asset checksums (sha256)
0b8f5db42a6f91a6585ff50c8021f99f93f97119f835cc6a754061b8a0b259ae bff.zip
0fffa7a49cc1e36aa7a6d3f6e1843899a2874979f3cb4e7474c2ecd9fb82b7a8 chat-dist.zip
86e3b2a12db85e667e2483dc1bbe786ebdee78476480b0777b4692d8520f3e91 agent-code.zip
The template and the three zips are cryptographically bound to each other (the checksums
are baked into the template, and the release tag is part of each object key). Do not mix
assets across releases — the stack verifies every checksum before use.
Everything else in this release
See the file diff against v1.0.9.
to meet your organizational security, regulatory and compliance requirements before deployment.