Billable resources for Snyk Cloud

How does Snyk count resources?

Snyk Cloud identifies security issues in your cloud environment’s resource configurations, relationships and network connections to ensure your applications and infrastructure are secure. While we detect and secure hundreds of types of resources in public cloud environments — including but not limited to servers, storage, network settings, IAM — billable resources are only a subset of Compute and Storage resource types. Snyk counts each of the following as a billable resource:
Virtual Machine
Snyk Cloud counts Virtual Machine instances as billable. Examples include AWS EC2 Instances, Azure Virtual Machines, and Google Compute Instances.
Serverless Function
Snyk Cloud counts Serverless Functions as billable. Snyk Cloud does not count function executions. Examples include AWS Lambdas, Azure Functions, and Google Cloud Functions.
Managed Application Service
Snyk Cloud counts Managed Application Services, which allow deployment of applications in the Cloud without managing underlying infrastructure, as billable. For these types of services, Snyk Cloud counts the “Application” or “Service” configuration resource. Examples of billable Managed Application Services include AWS Elastic Beanstalk Applications, Azure App Services, and Google App Engine Applications.
Managed Container Service
Snyk Cloud counts Managed Container Services, which typically orchestrate sets of running containers, as billable. Snyk Cloud does not count the individual running container instances or executions. Examples of billable Managed Container Services include AWS ECS Services, Azure Container Instance Groups, and Google Cloud Run Services.
Managed Kubernetes Service
Snyk Cloud counts Kubernetes clusters managed by Managed Kubernetes Services as billable. Snyk Cloud does not count workloads (pods) or services running within the cluster.
Examples of billable Managed Kubernetes Services include Amazon Elastic Kubernetes Service (EKS) Clusters, Azure Kubernetes Service (AKS) Clusters, and Google Kubernetes Engine (GKE) Clusters.
Database Service
Snyk Cloud counts Database Services instances as billable. If the instance cannot be counted, Snyk Cloud counts the next highest configuration resource for the database, sometimes called a Cluster or Account. Examples of billable Database Instances include AWS RDS Instances, AWS Redshift Clusters, Azure SQL Managed Instances, Azure Cosmos DB Accounts, Google SQL Database Instances and Google BigTable Instances.
In-Memory Storage Service
Snyk Cloud counts In-Memory Storage Services, which are typically utilized as in-memory data stores or distributed caches as billable. Examples of billable In-Memory Storage Services include AWS Elasticache Clusters, Azure Redis Cache, and Google Redis Instances.
Object Storage
Snyk Cloud counts object storage containers which are typically used to store files or binary large objects (blob) data as billable. Snyk does not count individual folders or data within these containers. Examples of billable Object Storage include AWS S3 Buckets, Azure Storage Accounts, and Google Storage Buckets.