elastic-load-balancer

问题 I have a single ec2 instance running a website behind an elastic load balancer in aws. Mainly because I want to use Amazon's new and free ssl for https. my challenge is, I need to whitelist my IP address in the security groups so that I am the only person that can see this website (and I can selectively add people as needed). I've successfully whitelisted my IP address without a load balancer. my challenge is white listing my IP address with the load balancer proxy between my IP address and

问题 I'm trying to redirect all incoming Traefik from http to https, for a web application which gets served out of a docker container with a custom port. If I build this docker compose file, and scale the application everything works as expected. I'm able to request http and https of the application, but I try to accomplish that only https get served and http gets redirected to https. Since I use a Docker-Compose file, I don't have a Traefik.toml, and try to accomplish this without one. Docker

问题 I have problem with aws SSL configuration with google domain. Follwing is the configuration my website have. www.abc.com Google domain myloadbalancer-XXXXXX.elb.amazon.com aws load balancer I have created SSL certificate on ACM as shown in image attached AWS ACM screenshot Then i create loadblancer with Lister HTTPS and pointed to HTTP 80 port (EC2 instance on which website is running) Screen shot of AWS load balancer My google domain abc.com is pointing to loadbalancer url Problem is when i

问题 I have an airflow web server configured at EC2, it listens at port 8080. I have an AWS ALB(application load balancer) in front of the EC2, listen at https 80 (facing internet) and instance target port is facing http 8080. I cannot surf https://< airflow link > from browser because the airflow web server redirects me to http : //< airflow link >/admin, which the ALB does not listen at. If I surf https://< airflow link > /admin/airflow/login?next=%2Fadmin%2F from browser, then I see the login

问题 I have microservices(in different programming languages) running on an EC2 instance. On production I notice a few 502 Bad Gateway Errors when these services try to interact with each other. Also in the logs of the requested service it doesn't show any api call is being hit example service A calls service B, but in service B logs there is nothing to indicate that a call came from service A. Can it be AWS load balancer issue? Any help would be appreciated. Thanks in advance. Solution tried: We

问题 I am having an issue using Terraform (v0.9.2) adding services to an ELB (I'm using: https://github.com/segmentio/stack/blob/master/s3-logs/main.tf). When I run terraform apply I get this error: * module.solr.module.elb.aws_elb.main: 1 error(s) occurred: * aws_elb.main: Failure configuring ELB attributes: InvalidConfigurationRequest: Access Denied for bucket: my-service- logs. Please check S3bucket permission status code: 409, request id: xxxxxxxxxx-xxxx-xxxx-xxxxxxxxx My service looks like

问题 In my AWS environment there are some load balanced / autoscaled Elastic Beanstalk applications. I would like to have a load balancer in front of them, so any request to http://loadbalancer.com/app1 is routed to the first Elastic Beanstalk app, http://loadbalancer.com/app2 to the second and so on. I tried to set up an application load balancer with different listeners routing to different target groups. Unfortunately my solution is not ideal, because the target groups are bound to a fixed set

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

问题 My question is an extended version of this. In my case the security group has to restrict the access to Load Balancer 1. It has to have some white listed IPs. So, which IPs can I put here that can allow access of Load Balancer 1 from Auto Scaling Group 2 private instances? I have tried putting the Elastic IP of NAT Gateway as a whitelisted IP and it works. I want to understand why it is absolutely necessary to put this IP in Security Group to access the internet-facing ALB from the private

问题 I have a web app which runs behind Amazon AWS Elastic Load Balancer with 3 instances attached. The app has a /refresh endpoint to reload reference data. It need to be run whenever new data is available, which happens several times a week. What I have been doing is assigning public address to all instances, and do refresh independently (using ec2-url/refresh ). I agree with Michael's answer on a different topic, EC2 instances behind ELB shouldn't allow direct public access. Now my problem is