Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
© 2022 Yandex.Cloud LLC
Yandex Application Load Balancer
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Target groups
      • Create target group
      • Edit a target group
      • Delete a target group
    • Backend groups
      • Create a backend group
      • Edit a backend group
      • Delete a backend group
    • HTTP routers
      • Create HTTP router
      • Edit an HTTP router
      • Delete an HTTP router
    • L7 load balancers
      • Create an L7 load balancer
      • Edit an L7 load balancer
      • View L7 load balancer statistics
      • View the L7 load balancer logs
      • Get the ID of the log group of the L7 load balancer
      • Stop and restart an L7 load balancer
      • Delete an L7 load balancer
    • Ingress Controller for Managed Service for Kubernetes
      • Install an Ingress controller
      • Create or update resources based on configuration
  • Practical guidelines
    • Setting up virtual hosting
    • Creating a load balancer with DDoS protection
    • Integrating an L7 load balancer with the CDN and Object Storage
    • Blue-green deployment for switching between service versions
    • Terminating TLS connections
    • Writing load balancer logs to PostgreSQL
  • Concepts
    • Overview
    • Load balancers
    • HTTP routers
    • Backend groups
    • Target groups
    • Quotas and limits
  • Tools
    • Ingress Controller for Managed Service for Kubernetes
      • Overview
      • How it works
      • Security groups
      • Service accounts
  • Access management
  • Pricing policy
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • BackendGroupService
      • HttpRouterService
      • LoadBalancerService
      • TargetGroupService
      • VirtualHostService
      • OperationService
    • REST
      • Overview
      • BackendGroup
        • Overview
        • addBackend
        • create
        • delete
        • get
        • list
        • listOperations
        • removeBackend
        • update
        • updateBackend
      • HttpRouter
        • Overview
        • create
        • delete
        • get
        • list
        • listOperations
        • update
      • LoadBalancer
        • Overview
        • addListener
        • addSniMatch
        • create
        • delete
        • get
        • getTargetStates
        • list
        • listOperations
        • removeListener
        • removeSniMatch
        • start
        • stop
        • update
        • updateListener
        • updateSniMatch
      • TargetGroup
        • Overview
        • addTargets
        • create
        • delete
        • get
        • list
        • listOperations
        • removeTargets
        • update
      • VirtualHost
        • Overview
        • create
        • delete
        • get
        • list
        • removeRoute
        • update
        • updateRoute
  • Ingress controller reference
    • Overview
    • Ingress
    • HttpBackendGroup
    • Service
  • Log reference
  1. Pricing policy

Pricing for Yandex Application Load Balancer

Written by
Yandex Cloud
  • What goes into the cost of using Application Load Balancer
    • Example of cost calculation
  • Pricing

What goes into the cost of using Application Load Balancer

When using the Application Load Balancer service, you pay for the actual use of computing resources of every active load balancer. The service is charged on an hourly basis.

The load balancer consumption is measured in resource units. One resource unit includes:

  • 1000 requests per second (RPS).
  • 4000 concurrently active connections.
  • 200 new connections per second.
  • 22 MB (176 Mbit) of traffic per second.

The amount of load balancer's resource units consumed per hour is calculated based on the indicator demonstrating the highest consumption rate compared to the threshold. Calculated values of resource units are rounded up to an integer.

The number of resource units is calculated separately for each availability zone. The minimum number of units per hour per zone is 2. The load balancer usage isn't charged in the availability zones where the inbound traffic is disabled.

When calculating the number of resource units, hourly maximums for indicators are used.

Example of cost calculation

A load balancer located in one availability zone, ran for an hour with the following indicators:

  • 6000 RPS.
  • 30000 parallel active connections.
  • 500 new connections per second.
  • 20 MB of traffic per second.

Here's the calculation of the cost for this hour and for the month comprised of 720 hours with the same indicators:

RPS: 6000 / 1000 = 6
Active connections: 30000 / 4000 = 7.5 ~ 8
New connections: 500 / 200 = 2.5 ~ 3
Traffic: 20 / 22 = 0.9090... ~ 1
Minimum number of resource units in the zone: 2

Number of resource units: 8

8 × 0.01776 = $0.14208

Hourly total: $0.14208
Monthly total: 0.14208 × 720 = $102.2976

Here $0.01776 is the cost per resource unit.

Pricing

Number Price, without VAT
One resource unit $0.017760

Was the article helpful?

Language / Region
© 2022 Yandex.Cloud LLC
In this article:
  • What goes into the cost of using Application Load Balancer
  • Example of cost calculation
  • Pricing