amazon-elb

问题 I'm using AWS Elastic Load Balancing (ELB) in front of 2 Linux Web Servers. But (based on my requirement) i need to know the Real IPs from the Web Servers' perspective, especially when i use netstat . I need to know the number of incoming connections from each IPs (from NETSTAT) , as in real time. So basically in Linux (without ELB in front) , below netstat command perfectly works: netstat -tn 2>/dev/null | grep :80 But now i can only see the internal IP(s) of the ELB ; which is making the

问题 From observer's perspective, symptoms are identical to the issue here Scenario is the same as well: Angular app which sends preflight requests to REST api, and preflight requests take in roughly 50% of times up to 1.3 seconds (illustration is the same as in the linked question). Also, websocket was frequently timing out until socket-io finally succeeded in establishing connection. Problem was more pronounced in Chrome and less in Safari/Firefox. However, we are using ALB and not ELB, and all

问题 From observer's perspective, symptoms are identical to the issue here Scenario is the same as well: Angular app which sends preflight requests to REST api, and preflight requests take in roughly 50% of times up to 1.3 seconds (illustration is the same as in the linked question). Also, websocket was frequently timing out until socket-io finally succeeded in establishing connection. Problem was more pronounced in Chrome and less in Safari/Firefox. However, we are using ALB and not ELB, and all

问题 I am trying to add SSL support for my site which is on AWS infrastructure. I am using (Ubuntu, Apache, cake-php). I installed the certificate from go daddy on AWS ELB per this guide. When I test my domain via HTTPS it works fine, but the site is also available via HTTP. I would like to redirect all calls to HTTP, but per the guide instructions the ELB and EC2 communicate via HTTP, so the protocol identified by my EC2 is on port 80, so the EC2 has no way to redirect the user, because all

问题 This blog post (here specifically) details how to configure connection draining for a 'classic' version 1 load balancer using the AWS::ElasticLoadBalancing::LoadBalancer type, like so: "ElasticLoadBalancer": { "Type": "AWS::ElasticLoadBalancing::LoadBalancer", "Properties": { "ConnectionDrainingPolicy": { "Enabled": "true", "Timeout": "300" }, ... } } How can I do this using the version 2 load balancer with type AWS::ElasticLoadBalancingV2::LoadBalancer ? My best guess from the documentation

问题 We like to enable HSTS to our IIS deployed web application. We have SSL terminating ELB Application load balancer. We have enabled the URL rewrite module in IIS and configured the x-Forward-Proto tag to decide and enable HSTS header in the response. Presently, ALB does not appear to pass custom headers from IIS to the ALB, to the end-user. We wanted to see if there is a way to enable HSTS either at ALB level where it can accept custom headers or if it can be set at IIS level and ALB can pass

问题 I'm trying to add an .ebextensions folder to the root level of my jar to be deployed to AWS elastic beanstalk. My folder structure is: main: --src --resources --.ebextensions When I build the jar my .ebextensions gets placed on the classpath of my target and therefore is not picked up by Elastic Beanstalk on deploy. Pom.xml <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <configuration> <fork>true</fork> <addResources>false</addResources>

问题 I'm trying to configure access to my EB environments, and would like to restrict HTTP access (through the ELB) to certain IP addresses. I have an out of the box EB app (a bunch, actually, with a few environments each) and would like be able to (a) restrict access to specific sets of IPs while (b) having all traffic come through the ELBs. Critically, I'd like to do this by (c) creating a few groups (e.g an admin SG that allows my IP, and a dev SG that allows a team's IPs, and a public SG that

问题 Question: When configuring Route 53 with AWS services such as CloudFront or ELB, which is better to use: an ALIAS A record or an ALIAS CNAME record? Background: An interesting thread developed on this question regarding the benefits of ALIAS records. Thread Link My intention is to create this question so that informed answers and knowledge can be collected in one place. 回答1: There is no "better," there's only one correct answer: the Alias RR type must be the same as the target RR. For

问题 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