Yandex API Gateway

API gateways are configured in a declarative way using specifications. A specification is a JSON or YAML file with an API gateway description based on the OpenAPI 3.0 standard. In Yandex API Gateway, the specification is supplemented with extensions that you can use for integrating with other cloud platforms.

The API supports two authorization methods:

• Authorization via function. Implement authorization in a convenient language and deploy it as a YC Functions function, and then just specify this function as an authorizer in the OpenAPI specification of the API gateway.
• Authorization using JWT. The API gateway itself verifies the signature of the JWT token, validates its fields, checks the relevance of the token and whether it has the rights necessary to obtain a specific resource. Just configure the JWT authorizer in the OpenAPI specification of the API gateway.

• Cloud Functions — calls the specified function.
• Object Storage — transmits a request to Object Storage to distribute static files.
• DataSphere — calls the DataSphere node deployed as a separate microservice.
• Data Streams — allows you to access Data Streams to perform an operation with a data stream.
• Serverless Containers — redirects the query to the specified container.
• Message Queue — allows you to access Yandex Message Queue to work with message queues.
• Managed Service for YDB — allows you to perform operations with documents tables in the Yandex Managed Service for YDB database.

Yes, the API Gateway has the ability to proxy HTTP requests to a specified URL. You can also configure a mode of full proxying of all requests with query parameters, headers, and a request body.

Yes, you can enable validation of requests and responses in the API gateway.

Yes, the API gateway can be connected to a VPC cloud network, then it will have access not only to the internet, but also to user resources located on the specified network, such as databases, virtual machines, etc.

In the API Gateway specification, standard integrations can be configured for the main events of work via WebSocket: establishing connections, sending data, closing/terminating connections. Also, additional methods are being added to the Yandex Cloud public API (SDK, GPS, YC) for managing WebSocket connections from the client server code: get connection data, send data to the client, close the connection.

Yes. To use CORS, describe the preflight request processing rule in the API Gateway specification. You can configure automatic processing of preflight requests for a specific path, different paths, or for the entire API gateway.