What we manage
EC2, Auto Scaling groups, RDS and Aurora, ECS and EKS node groups, Redshift
Access we ask for
IAM role with read-only discovery; start/stop scoped to the resources you tag
CloudValet reads your estate through the provider's own APIs and pushes what it finds into the places your team already watches.
Cloud providers
What we manage
EC2, Auto Scaling groups, RDS and Aurora, ECS and EKS node groups, Redshift
Access we ask for
IAM role with read-only discovery; start/stop scoped to the resources you tag
What we manage
Virtual machines, VM scale sets, Azure SQL, AKS node pools, App Service plans
Access we ask for
Service principal with Reader, plus a narrow start/stop role assignment
What we manage
Compute Engine, instance groups, Cloud SQL, GKE node pools
Access we ask for
Service account with Viewer, plus instance admin on the projects you choose
Provider names and marks are used to show what CloudValet connects to. They do not imply a partnership, sponsorship or certification. We will say so plainly when one exists.
Where the signals land
Parking confirmations and IAM change alerts in the channel that owns the account.
The same alerts, posted to a Teams channel with the plain-English summary attached.
Every event as JSON, so you can route it into PagerDuty, Jira or your own service.
CSV exports of parked resources, schedules and access findings for finance reviews.
SAML and OIDC sign-in with role-based access, on Enterprise.
Read and write access to schedules and findings for teams with their own tooling.
Managed providers
We are looking for a small number of managed service providers and consultancies to build the multi-tenant side of CloudValet with us. Separate customer estates, delegated access, and proof of what was parked.
Talk about a reseller setupWhat we bring