Skip to main content

Install SleakOps on your infra

SleakOps can bring an existing AWS setup under management instead of provisioning everything from scratch. Import mode connects SleakOps to infrastructure you already run — an AWS account, its network, and an EKS cluster — without recreating any of it.

Import features are enabled per company — contact SleakOps to enable them for yours.

Prerequisites​

  • An AWS account with existing infrastructure to import.
  • Permissions to run CloudFormation stacks in that account.
  • An admin user in SleakOps.

The import journey​

Importing existing infrastructure follows a fixed sequence:

  1. Import the provider.
  2. Import the accounts.
  3. Configure the network.
  4. Import the cluster.

What you can import​

ResourceWhat it does
ProviderConnect SleakOps to an AWS Organization you already run.
AccountDeclare an existing AWS account and connect it via CloudFormation.
Network configurationComplete the network inputs SleakOps needs for an imported account.
ClusterRegister an existing EKS cluster in SleakOps.
DependencyRegister an existing managed resource (RDS, S3, SQS, Redis…) as a SleakOps Dependency.
ProjectAdopt an existing deployment as a SleakOps Project.
DomainReuse an existing Route53 hosted zone for an Environment.
NodePoolRegister an existing EKS node pool.
AddonsImport an addon's manifests, or adopt one already running in the cluster.
Essential addonsSee which core addons SleakOps installs on an imported cluster (AWS Auth) and which you add on demand.