amazon-elb

问题 I have an AWS Elastic Beanstalk environment that is created with an Elastic Load Balancer, and which specifies the default ELB security group ("ELB created security group used when no security group is specified during ELB creation") as the source for inbound HTTP. If I replace this default ELB security group as the source for my environment's security group's inbound rules with a port range does traffic still come through the ELB and is it still filtered by the ELB's security group's rules

问题 I have an AWS Elastic Beanstalk environment that is created with an Elastic Load Balancer, and which specifies the default ELB security group ("ELB created security group used when no security group is specified during ELB creation") as the source for inbound HTTP. If I replace this default ELB security group as the source for my environment's security group's inbound rules with a port range does traffic still come through the ELB and is it still filtered by the ELB's security group's rules

问题 I am currently using Spark on AWS EMR, but when this is behind a Load Balancer (AWS ELB), it is redirecting the traffic from https to http, which then ends up getting denied because I don't allow http traffic through the load balancer for the given port. It appears that this might derive from Yarn being a proxy as well, but I have no idea. 来源： https://stackoverflow.com/questions/56412083/spark-history-server-behind-load-balancer-is-redirecting-to-http

问题 I am currently using Spark on AWS EMR, but when this is behind a Load Balancer (AWS ELB), it is redirecting the traffic from https to http, which then ends up getting denied because I don't allow http traffic through the load balancer for the given port. It appears that this might derive from Yarn being a proxy as well, but I have no idea. 来源： https://stackoverflow.com/questions/56412083/spark-history-server-behind-load-balancer-is-redirecting-to-http

问题 I'm trying to set up a simple HTTP to HTTPS redirect for traffic going to a Kubernetes cluster. The SSL termination is happening on the ELB. When I try to use the nginx.ingress.kubernetes.io/ssl-redirect = true it results in an infinite redirect which led me to setting up a config map to handle this (nginx-ingress: Too many redirects when force-ssl is enabled). Now there seems to be no redirection happening at all. My ingress service is defined as: apiVersion: v1 kind: Service metadata:

问题 I'm trying to set up a simple HTTP to HTTPS redirect for traffic going to a Kubernetes cluster. The SSL termination is happening on the ELB. When I try to use the nginx.ingress.kubernetes.io/ssl-redirect = true it results in an infinite redirect which led me to setting up a config map to handle this (nginx-ingress: Too many redirects when force-ssl is enabled). Now there seems to be no redirection happening at all. My ingress service is defined as: apiVersion: v1 kind: Service metadata:

问题 One way (or server side) TLS/HTTPS with Amazon Elastic Load Balancing is well documented Support for two-way (or client side) TLS/HTTPS is not as clear from the documentation. Assuming ELB is terminating a TLS/HTTPS connection: Does ELB support client authenticated HTTPS connections? If so, does a server served by ELB recieve a X-Forwarded-* header to identify the client authenticated by ELB? ELB does support TCP forwarding so an EC2 hosted server can establish a two-way TLS/HTTPS connection

问题 I've had this issue before. When running WordPress (or other PHP scripts) behind Amazon's EC2 Load Balancer, the scripts do not realize they are being ran on the https:// protocol and results in issues such as endless redirect loops, and HTTPS warnings ("Some content on this page is being requested in a non-secure way..."). I found a solution here, but requires modifying WordPress core, which is no good for updatability: https://wordpress.org/support/topic/when-behind-amazon-web-services

问题 I'm using Amazon EC2, and I want to put an internet-facing ELB (load balancer) to 2 instances on a private subnet. I am using VPC with public and private subnets. If I just add the private subnet to the ELB, it will not get any connections. If I attach both subnets to the ELB then it can access the instances, but it often will get time-outs. (Refer Screenshot 1) If I attach to only public subnet then my instance attached to ELB gets OutOfService because I do not have any instance in the

问题 This doesn't seem to be working right now. I'm using Faye with NodeJS behind an Amazon ELB. When I switch on HTTPS the connections can no longer be brokered. I found a question here unanswered: https://forums.aws.amazon.com/message.jspa?messageID=283293 . Anyone able to get this working? Are there any work around outside of running my own instance of HAProxy? 回答1: I confirm, based on our own tests, that configuring ELB on TCP/SSL, instead oh HTTP/HTTPS, makes the trick with WebSockets. The