transiliencecloud onboarding
Resources · templates & scripts

Inspect first. Install with intent.

Review the production template and installer. Keep customer-specific connection values in the approved workflow.

AWS · CloudFormation

AWS audit-role stack

Production review snapshot · 17 KB

Download YAML ↓
Inspect SHA-256 fingerprintc0a23d4cda6066ec6757b218e53b28fd56e9708bddd6799c5a61d5dc536ff594
Azure · Bash installer

Azure installer

Production review snapshot · 33 KB

Download script ↓
Inspect SHA-256 fingerprint8a77c933adf51b20d8b5f7c59c9673343ba1248531ce2acfad8588bebd1062fe
Download the snapshot manifest (.json) ↓

The downloadable files are byte-for-byte snapshots of Transilience’s publicly hosted production assets fetched on 14 October 2026. Each has a SHA-256 fingerprint. They contain installation logic, not your organization’s connection token. Compare the upstream asset again before a new deployment; production code can change.

AWS CloudFormation#

Review the YAML and its IAM trust/policies. To install, start with the customer-specific Quick Create link from Integrations so the organization, one-time token, and callback are correct. Do not upload this template with guessed connection values.

Current upstream template · Installation guide

Azure Cloud Shell script#

Download and inspect the Bash installer; do not pipe unfamiliar remote code straight into a shell. The full-evidence profile includes Azure roles and tenant-wide application consent, and it creates a dedicated app secret. Run only the exact reviewed customer-specific command and approved scope. The script is for Azure Cloud Shell Bash, not a PowerShell session.

Current upstream installer · Cloud Shell guide

Review a downloaded file’s fingerprint#

# macOS
shasum -a 256 transilience-security-audit.yaml
shasum -a 256 azure-compliance.sh
# Linux / Azure Cloud Shell
sha256sum transilience-security-audit.yaml azure-compliance.sh

Compare the output to the fingerprints above. A matching fingerprint confirms the snapshot’s bytes, not that permissions are appropriate for your account.

Prefer a manual installation?#

Follow the AWS console procedure or Azure portal procedure instead. All trust-policy placeholders must be replaced with current approved values; never copy example tenant or workspace IDs from screenshots.

Keep moving

Make the next step a confident one.

Verify the connection →

Find your next step.

Search runs locally. No queries leave your browser. Esc to close.