Closed rafaelsilvaa10 closed 4 years ago
Hi, ALB supports cognito & waf. The missing gap between ALB and APIGW i know is throttling. So if ALB supports all features you need, then it can be acting as a gateway(without using APIGateway)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
Hello, I have some applications (apis) configured in k8s, all of them have a configured ingress controller (alb) , already work normally.
However, as per my company's policy, all external apis, need to go through a gateway. It was then that I configured the apigateway(aws) pointing to my ingress endpoint(alb). I was not successful, I believe that the apigateway(aws) works only with nlb.
Here we use basic resources of the apigateway (aws), such as auth cognito, acl waf e timeout...
Is it worth saying that ingress (Alb) can be my final endpoint, acting as a gateway? does anyone have this scenario? if positive, how did you treat?
Thank you all.