Skip to content

Latest commit

 

History

History
68 lines (55 loc) · 3.04 KB

README.md

File metadata and controls

68 lines (55 loc) · 3.04 KB

Logo

Telophase


Documentation

Full documentation here: https://docs.telophase.dev

Why Telophase?

Automation and Compliance are key concerns when adopting a multi-account AWS setup. Telophase manages your AWS Organization as IaC, and deeply integrates with IaC providers, like Terraform or CDK. This integration allows:

  1. Workflow Automation: Automates account creation and decommissioning, integrating with existing automation workflows, like CI or ServiceNow.
  2. IaC <> Account Binding: Enables binding accounts to IaC blueprints for automatic provisioning of resources in a newly created account.
  3. Easier Compliance Deployment: Enables binding Service Control Policies (SCPs) to accounts as part of your Account provisioning workflow to make sure every Account is compliant. We make it easy to test SCPs before they are deployed.

Currently, Telophase is a CLI tool only. In the future, we plan to offer a web UI.

Install

If you'd like another method, please let us know by opening an issue!

Go

go install github.com/santiago-labs/telophasecli@latest

Homebrew

brew tap Santiago-Labs/telophasecli
brew install telophasecli

Quick links

Community

Join our Slack community: slack

Future Development

  • Support for multi-cloud organizations with a unified account factory.
    • Azure
    • GCP
  • Drift detection/prevention
  • Guardrails around account resources
  • Guardrails around new Accounts, similar to Control Tower rules.

Comparisons

Telophase vs Control Tower

Manage Accounts via code not a UI. Telophase leaves the controls up to you and your IaC.

Telophase vs CDK with multiple environments

Telophase wraps your usage of CDK so that you can apply the cdk to multiple accounts in parallel. Telophase lets you focus on your actual infrastructure and not worrying about setting up the right IAM roles for multi account management.