What does Hyperglance count as a resource?

Find out what types of resource count towards your Hyperglance licence in AWS, Azure, and Kubernetes

In this article, you'll find the full list of resource types that Hyperglance counts towards its licence limit. Each of the following platforms has its own list:

When we calculate how many resources you'll need to be licensed for, we include an instance/VM, load balancer, gateway, S3 bucket, database instance, or peering connection with all of its associated data, that is defined as a single entity or instance by its primary source platform.

Interfaces, links, attributes, and chart data don't count toward your resource limit.

Amazon Web Services

In AWS, these are the types of resource that do count towards your Hyperglance licence limit:

  • EC2 Instance
  • EBS Volume
  • ECS Task
  • Internet Gateway
  • Egress Only Internet Gateway
  • VPN Gateway
  • NAT Gateway
  • Customer Gateway
  • Application Load Balancer
  • Network Load Balancer
  • Elastic Load Balancer
  • Dynamo DB Table
  • Dynamo DB Accelerator
  • RDS Instance
  • RDS Aurora Serverless
  • Peering Connection
  • S3 Bucket
  • Lambda Function
  • Route53 Policy Record
  • Route53 Hosted Zone
  • Route53 Record Set
  • Redshift Cluster Node
  • Transit Gateway
  • EKS Cluster

Microsoft Azure

In Azure, these are the types of resource that do count towards your Hyperglance licence limit:

  • Virtual Machine
  • Disk
  • Load Balancer
  • Route Tables Classic
  • Storage Accounts Classic
  • Domain Names Classic
  • SQL Database
  • SQL Server
  • PostgreSQL Server
  • MySQL Server
  • Application Gateways
  • Virtual Network Gateways
  • Local Network Gateways
  • Peering Connection
  • Web App
  • Function
  • Logic App
  • Cosmos DB Container
  • Redis Cache
  • API Management Service
  • Event Grid Topic
  • Virtual Machine Scale Set
  • Scale Set Instance

Kubernetes

In Kubernetes, these are the types of resource that do count towards your Hyperglance licence limit:

  • Container
  • ClusterIP
  • ExternalName
  • Ingress
  • Cluster
  • LoadBalancer
  • Node
  • NodePort
  • Persistent Volume
  • Persistent Volume Claim
  • Pod
  • Volume