Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex API Gateway
  • Getting started
    • Resource relationships
    • Networking
      • Overview
        • Static response
        • Access over HTTP
        • Cloud Functions
        • Serverless Containers
        • Smart Web Security
        • Object Storage
        • DataSphere
        • Data Streams
        • Message Queue
        • Managed Service for YDB
      • Greedy parameters
      • Generic HTTP method
      • Authorization using a Cloud Functions function
      • Authorization using a JWT
      • WebSocket protocol support
      • Data validation
      • CORS
      • Specification parameterization
      • Canary release
      • Request rate limit
      • Response code replacement
      • Transformation of response and request bodies
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Supported parameters
  • Extension specification
  • Use cases
  1. Concepts
  2. Specification extensions
  3. Integration options
  4. Serverless Containers

x-yc-apigateway-integration:serverless_containers extension

Written by
Yandex Cloud
Updated at April 24, 2025
  • Supported parameters
  • Extension specification
  • Use cases

The x-yc-apigateway-integration:serverless_containers extension invokes the relevant container and provides the HTTP request sent to the API gateway to it. In which case the Host header specifies the host used by the user to access the API gateway, not the container's host.

If a request contains the X-Forwarded-For header, the specified IP addresses and the IP address of the user that invoked the container are provided in this header. If this header is missing, the request only transmits the IP address of the user who invoked the container.

You can add an extension to a specification using the specification constructor.

Supported parametersSupported parameters

The table below lists the parameters specific to API Gateway API gateways. You can find the description of other parameters in the OpenAPI 3.0 specification.

Parameter Type Description
container_id string Container ID.
service_account_id string Service account ID used for authorization when accessing a container. Invoking a private container requires a service account with the serverless-containers.containerInvoker role or higher for that container. If you omit the parameter, the service_account_id top-level parameter value will be used.
context object This is an optional parameter. It provides the operation context, i.e., an object in YAML or JSON format. It is encoded in Base64 and provided to the container in the X-Yc-ApiGateway-Operation-Context header. The parameters are subsituted into context.

Extension specificationExtension specification

Specification example:

/example/{ID}:
    get:
      summary: Get ID
      operationId: getID
      tags:
        - example
      parameters:
        - name: ID
          in: path
          description: Return ID
          required: true
          schema:
            type: string
      x-yc-apigateway-integration:
        type: serverless_containers
        container_id: b095c95icnvb********
        service_account_id: ajehfe12hhl********

Example of proxying all requests to a container:

paths:
  /{proxy+}:
    x-yc-apigateway-any-method:
      x-yc-apigateway-integration:
        type: serverless_containers
        container_id: bba0hocqr8rl********
        service_account_id: ajegj8fnpmkm********
      parameters:
      - explode: false
        in: path
        name: proxy
        required: false
        schema:
          default: '-'
          type: string
        style: simple

Use casesUse cases

  • Running a containerized app in Yandex Serverless Containers

Was the article helpful?

Previous
Cloud Functions
Next
Smart Web Security
© 2025 Direct Cursus Technology L.L.C.