Skip to content

support REST API Gateway #1197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
deliahu opened this issue Jul 2, 2020 · 1 comment
Closed

support REST API Gateway #1197

deliahu opened this issue Jul 2, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@deliahu
Copy link
Member

deliahu commented Jul 2, 2020 •
edited
Loading

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
@deliahu deliahu added the enhancement New feature or request label Jul 2, 2020
@deliahu deliahu mentioned this issue Aug 2, 2020
Closed
@miguelvr
Copy link
Collaborator

miguelvr commented Jan 5, 2021

closed #1751

@miguelvr miguelvr closed this as completed Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@deliahu @miguelvr