Support
If you run into an issue or have a question, the fastest way to get help is through Support, in the main sidebar of the console — it combines an AI-powered chat with support tickets for your account. Before reaching out, it's worth a quick search here in the docs: most day-to-day questions are already answered in a tutorial or FAQ.
What our support covers
- Errors in the SleakOps platform itself.
- Errors in infrastructure resources automatically managed by SleakOps (clusters, environments, dependencies, addons).
- Help updating resources provisioned with SleakOps.
- Infrastructure state locks (resources stuck in a state).
- Support finding workarounds for customizations the platform doesn't cover.
Where to look first
For a few common questions, the fastest answer is one you can get yourself, right now:
- Something's wrong in your application or its code — that's owned and debugged by your own team; SleakOps manages the infrastructure your application runs on, not the application itself. As a first step, you can run an AI-powered Autodiagnostic on the workload to guide the investigation.
- The application feels slow — start with Grafana to see what your workloads are actually using, before assuming it's an infrastructure problem.
- Questions about your Dockerfile or build configuration — see Configure your Dockerfile for what's supported out of the box.
- You want to understand or reduce your AWS spend — see the Cost Review Guide to read what you're already spending, and AWS Cost Optimization Strategies for concrete ways to bring it down.
- Choosing AWS services or designing your architecture — see the Responsibility Model below and AWS's own documentation for guidance; these decisions are yours to make for your application.
Responsibility at a glance
| SleakOps | You | |
|---|---|---|
| Platform & infrastructure | Clusters, networking, provisioning, and the resources SleakOps creates for you — as long as you don't modify them directly in AWS, outside the platform. | Configure environment variables, define resource requirements, and monitor usage |
| Your application | Provide runtime environment, CI/CD pipelines capabilities, and observability tools (logs/metrics) | Your code, its dependencies, and its performance |
| Data & backups | Expose the resource's backup settings in the dependency form (e.g. the RDS "Automated Backup" toggle and retention period) | Define and manage backup and restoration policies for your dependencies — RDS, S3, RabbitMQ — and their secure storage (see Responsibility Model) |
Still not sure?
If you're not sure whether something is covered, just ask — reach out through Support and we'll point you in the right direction.