aws-alb

问题 I'm trying to find a solution for the problem that seems like something very common. I have a k8s cluster ip service which exposes two ports: 8088 and 60004 I would like to expose these same ports on ALB and not use path based routing This works for exposing one service on 8088 port: --- apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myingress namespace: myns annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/healthcheck-path: /ping alb.ingress.kubernetes.io

问题 I'm trying to find a solution for the problem that seems like something very common. I have a k8s cluster ip service which exposes two ports: 8088 and 60004 I would like to expose these same ports on ALB and not use path based routing This works for exposing one service on 8088 port: --- apiVersion: extensions/v1beta1 kind: Ingress metadata: name: myingress namespace: myns annotations: kubernetes.io/ingress.class: alb alb.ingress.kubernetes.io/healthcheck-path: /ping alb.ingress.kubernetes.io

问题 I am setting up an AWS ECS Service using cloudformation and yaml syntax. At some point, in the relevant documentation there is a property called Role whose definitions is the following: Role The name or ARN of an AWS Identity and Access Management (IAM) role that allows your Amazon ECS container agent to make calls to your load balancer. Note In some cases, you might need to add a dependency on the service role's policy. For more information, see IAM role policy in DependsOn Attribute.

问题 I am trying to setup Authentication for some certain routes using AWS internet-facing Application load balancer. I've done all the steps from the official AWS documentation, and also using this one: https://www.thorntech.com/2018/09/user-authentication-alb-cognito/ I was testing via load balancer's DNS name, and it redirects me properly to the login form of Cognito, but after I am logged in it redirects to the load balancer, and it gives 500 Internal Server Error . URL is like so https:/