Skip to content

support REST API Gateway #1197

@deliahu

Description

@deliahu

Description

Currently, Cortex supports HTTP API Gateway, but there are some features in REST API Gateways that are not supported by HTTP API Gateways (and are difficult to get around), such as IAM authentication.

This would add the option for the user to specify whether to use the REST API Gateway or HTTP API Gateway.

Example config

networking:
  api_gateway: none | public  # current
  api_gateway: none | http_public | rest_public | rest_private  # proposal #1
  api_gateway: none | public_http | public_rest | private_rest  # proposal #2

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions