英文:
API keys in GCP API Gateway - 300 limit
问题
我正在构建一个 API 服务。所有 API 端点都由 GCP API 网关前端化。所有我的客户都将获得一个唯一的 API 密钥来访问我的 API 端点。Google 云允许我使用 API 和服务中的凭据服务生成唯一的 API 密钥，但有一个 300 个 API 密钥的限制。如何绕过这个限制？人们如今如何处理客户的 API 密钥？
附注：APIGEE 太复杂且成本高昂。在后端实施自定义解决方案是一种耗时的选择，我目前没有这个选项。
英文:
I am building an api service. All api endpoints are fronted by GCP api gateway. All my customers will be given a unique api key to access my api endpoints. Google cloud allows me to generate unique API keys using the Credential service in API & Service. but there is a limit of 300 API keys. How do I bypass this limit? How do people handle api keys for clients nowadays?
ps: APIGEE is way to complicated and costly. Implementing my own custom solution in the backend is a time consuming option I don't currently have.
答案1
得分: 1
目前没有GCP本地解决方案，我将不得不迁移到AWS API Gateway。
AWS可以生成高达10000个API密钥，但他们还有一种实现自定义授权器的方法：https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-use-lambda-authorizer.html。
自定义授权器方法正是我正在寻找的，有人已经向GCP API Gateway团队提交了此功能请求：https://issuetracker.google.com/issues/226426383。
英文:
there is no GCP native solution, and I will have to move to the AWS API Gateway.
AWS can generate up to 10000 api keys, but they also have a way to implement a custom authorizer https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-use-lambda-authorizer.html.
The custom authorizer method is exactly what I am looking for and someone has submitted this feature request to the GCP API Gateway team: https://issuetracker.google.com/issues/226426383
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论