transiliencecloud onboarding
Interactive planner

Your cloud. Your scope. Your plan.

Choose a path before you grant access. Nothing here connects to your cloud or sends your information.

01 — Choose your path

Let’s make this straightforward.

Planning only. No cloud API calls. No credentials collected.

A connection that fits your environment#

Automated installation and manual setup lead to the same objective: approved evidence access in the right customer organization. They do not necessarily grant identical permissions. Review the selected method’s access profile before installing.

Bring these to the installation#

  • Your customer organization in Transilience, and a current connection link or command from Integrations or your authorized Transilience contact.
  • The AWS account IDs or Azure tenant and subscription IDs that you have approved for assessment.
  • An administrator who can create the connector identity and approve its permissions. Azure may require two administrators with different responsibilities.
  • Your data-access approval and a named owner for credential rotation and offboarding.

Keep human and service access separate#

The assessment connector is a service identity. If an engineer also needs interactive access, use the separate AWS engineer-access guide and an individually approved work email. A human login does not replace the connector.

Know where the boundary is#

This public portal is documentation, not a credential broker. It cannot create a tenant-specific connection token, verify a live installation, or receive cloud secrets. The planner stays in your browser. Installation and verification happen in your cloud account and your authenticated Transilience workspace.

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.