aws-load-balancer

What is the best way to restrict access to an Application Load Balancer?

由 核能气质少年 提交于 2020-04-12 08:20:26
问题 Ideally, I'd like to lock down my ALB so that it can only be accessed by API Gateway. I've looked into whether I can associate API gateway with an Inbound Rule - however, I have found that API Gateway cannot be associated with an IP address, or a security group. I've also looked into an Internal facing ALB, but I've been unable to get these working as VPC link only supports NLB. Any help will be greatly appreciated - I've been looking in the Gateway Settings but cannot find this option. What

Exposing kubernetes app using AWS Elastic LoadBalancer

由 一笑奈何 提交于 2019-12-25 18:32:42
问题 I created an internal AWS elastic application loadbalancer and in AWS console it shows its state as active. Note that I created this ALB using a jenkins job and in the job I have specified my AWS EC2 instance server which is configured as my kubernetes master. And I can see following details after the job was completed successfully. In AWS console under description, I can see below details - DNS internal-myservices-987070943.us-east-1.elb.amazonaws.com Scheme internal Type application IP

ECS service with two Load Balancers for same port: internal and internet-facing

由 可紊 提交于 2019-12-24 06:31:06
问题 I'm having trouble while trying to apply a modification on a ECS cluster. Particularities of the environment: Cluster has 2 services: blue and green. Currently both services are associated to an Application Load Balancer that is exposed to the Internet. What I want to do: add another ALB, in this case an internal one, to receive requests from private subnets in the VPC for the same service (same container, same port). When trying to apply those modifications I'm getting the following error:

Cannot connect to internet-facing NLB forwarding traffic to a private instance

由 非 Y 不嫁゛ 提交于 2019-12-11 13:25:03
问题 I have configured a cloud with following configuration VPC with a public and private subnet in two availability zones. Public subnet has an internet gateway and private subnet has a NAT gateway configured An internet-facing Network Load Balancer allowing TCP traffic configured in both availability zones A target group to forward traffic from the load balancer An EC2 instance in private subnet configured with haproxy listening at port 80. It's security group is configured to accept TCP traffic

500 error trying to authenticate via AWS Application load balancer and Cognito

由 和自甴很熟 提交于 2019-12-11 07:52:22
问题 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:/

EKS in private Subnet , Load Balancer in public subnet

由 别等时光非礼了梦想. 提交于 2019-12-09 15:52:32
问题 I am running EKS in private subnet and thus unable to create an internet facing load balancer but was able to create Internal LoadBalancer. Is there any way I can create Loadbalancer(probably Manually) in public subnet and point to the pods running in EKS in the private subnet. I was thinking of creating the chain of load balancer in which External load balancer will point to internal load balancer but that too is not possible as the IP address of the internal load balancer is reserved IP.

EKS in private Subnet , Load Balancer in public subnet

由 风格不统一 提交于 2019-12-04 03:59:45
I am running EKS in private subnet and thus unable to create an internet facing load balancer but was able to create Internal LoadBalancer. Is there any way I can create Loadbalancer(probably Manually) in public subnet and point to the pods running in EKS in the private subnet. I was thinking of creating the chain of load balancer in which External load balancer will point to internal load balancer but that too is not possible as the IP address of the internal load balancer is reserved IP. Can I try some other way to route the traffic from the internet to pod? I had the same issue and it was

How to divert the traffic to targer servers without port number in URL

由 纵然是瞬间 提交于 2019-12-02 23:08:20
问题 I have 4 web servers, These web servers hosts nearly 8 different websites. I am planning to use path based routing like http://myexample.com/website1/.. For example when i deployed by application on port 8580 and create the path based rule in ALB.. and hit the url it is not working. Instead i had to use http://myexample.com:8580/website1. Please help to resolve this, how can i remove the port number from URL. Since all these are internal application under single domain. I do not have an

How to divert the traffic to targer servers without port number in URL

由 别来无恙 提交于 2019-12-02 13:19:19
I have 4 web servers, These web servers hosts nearly 8 different websites. I am planning to use path based routing like http://myexample.com/website1/ .. For example when i deployed by application on port 8580 and create the path based rule in ALB.. and hit the url it is not working. Instead i had to use http://myexample.com:8580/website1 . Please help to resolve this, how can i remove the port number from URL. Since all these are internal application under single domain. I do not have an option of using different domain names or different load balances. The reason is your load balancer
订阅 aws-load-balancer