GCE managed group (autoscaling) - Proxy/Load Balancer for both HTTP(S) and TCP requests
up vote
0
down vote
favorite
I have an autoscaling istance group, i need to setup a Proxy/Load balancer that take request and send it to the istance group.
I thinked to use a Load balancer, but I need to grab both HTTP(S) and TCP requests.
There is some way (or some workaround) to solve this?
google-compute-engine load-balancing static-ip-address
add a comment |
up vote
0
down vote
favorite
I have an autoscaling istance group, i need to setup a Proxy/Load balancer that take request and send it to the istance group.
I thinked to use a Load balancer, but I need to grab both HTTP(S) and TCP requests.
There is some way (or some workaround) to solve this?
google-compute-engine load-balancing static-ip-address
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an autoscaling istance group, i need to setup a Proxy/Load balancer that take request and send it to the istance group.
I thinked to use a Load balancer, but I need to grab both HTTP(S) and TCP requests.
There is some way (or some workaround) to solve this?
google-compute-engine load-balancing static-ip-address
I have an autoscaling istance group, i need to setup a Proxy/Load balancer that take request and send it to the istance group.
I thinked to use a Load balancer, but I need to grab both HTTP(S) and TCP requests.
There is some way (or some workaround) to solve this?
google-compute-engine load-balancing static-ip-address
google-compute-engine load-balancing static-ip-address
asked Nov 14 at 9:31
tidpe
477
477
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
For your use case, a single load balancing configuration available on Google Cloud Platform will not be able to serve the purpose. On the other hand, since you are using managed instance groups (Autoscaling), it can not be used as backend for 2 different load balancers.
As per my understanding, the closest you can go is by using Network load balancing (TCP) and install SSL certificate to handle HTTPS requests
on the instance level.
What do you mean for "setting up SSL on the instance level"?
– tidpe
2 days ago
I have updated my post on the SSL part. I hope this clarifies.
– Tariq
yesterday
But load balancer doesn't block the request to HTTPS? And in that case, i have the same problem. I can't point my HTTPS requests to a static ip, if that istance "die", ip change :/
– tidpe
21 hours ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
For your use case, a single load balancing configuration available on Google Cloud Platform will not be able to serve the purpose. On the other hand, since you are using managed instance groups (Autoscaling), it can not be used as backend for 2 different load balancers.
As per my understanding, the closest you can go is by using Network load balancing (TCP) and install SSL certificate to handle HTTPS requests
on the instance level.
What do you mean for "setting up SSL on the instance level"?
– tidpe
2 days ago
I have updated my post on the SSL part. I hope this clarifies.
– Tariq
yesterday
But load balancer doesn't block the request to HTTPS? And in that case, i have the same problem. I can't point my HTTPS requests to a static ip, if that istance "die", ip change :/
– tidpe
21 hours ago
add a comment |
up vote
0
down vote
For your use case, a single load balancing configuration available on Google Cloud Platform will not be able to serve the purpose. On the other hand, since you are using managed instance groups (Autoscaling), it can not be used as backend for 2 different load balancers.
As per my understanding, the closest you can go is by using Network load balancing (TCP) and install SSL certificate to handle HTTPS requests
on the instance level.
What do you mean for "setting up SSL on the instance level"?
– tidpe
2 days ago
I have updated my post on the SSL part. I hope this clarifies.
– Tariq
yesterday
But load balancer doesn't block the request to HTTPS? And in that case, i have the same problem. I can't point my HTTPS requests to a static ip, if that istance "die", ip change :/
– tidpe
21 hours ago
add a comment |
up vote
0
down vote
up vote
0
down vote
For your use case, a single load balancing configuration available on Google Cloud Platform will not be able to serve the purpose. On the other hand, since you are using managed instance groups (Autoscaling), it can not be used as backend for 2 different load balancers.
As per my understanding, the closest you can go is by using Network load balancing (TCP) and install SSL certificate to handle HTTPS requests
on the instance level.
For your use case, a single load balancing configuration available on Google Cloud Platform will not be able to serve the purpose. On the other hand, since you are using managed instance groups (Autoscaling), it can not be used as backend for 2 different load balancers.
As per my understanding, the closest you can go is by using Network load balancing (TCP) and install SSL certificate to handle HTTPS requests
on the instance level.
edited yesterday
answered Nov 21 at 18:50
Tariq
264
264
What do you mean for "setting up SSL on the instance level"?
– tidpe
2 days ago
I have updated my post on the SSL part. I hope this clarifies.
– Tariq
yesterday
But load balancer doesn't block the request to HTTPS? And in that case, i have the same problem. I can't point my HTTPS requests to a static ip, if that istance "die", ip change :/
– tidpe
21 hours ago
add a comment |
What do you mean for "setting up SSL on the instance level"?
– tidpe
2 days ago
I have updated my post on the SSL part. I hope this clarifies.
– Tariq
yesterday
But load balancer doesn't block the request to HTTPS? And in that case, i have the same problem. I can't point my HTTPS requests to a static ip, if that istance "die", ip change :/
– tidpe
21 hours ago
What do you mean for "setting up SSL on the instance level"?
– tidpe
2 days ago
What do you mean for "setting up SSL on the instance level"?
– tidpe
2 days ago
I have updated my post on the SSL part. I hope this clarifies.
– Tariq
yesterday
I have updated my post on the SSL part. I hope this clarifies.
– Tariq
yesterday
But load balancer doesn't block the request to HTTPS? And in that case, i have the same problem. I can't point my HTTPS requests to a static ip, if that istance "die", ip change :/
– tidpe
21 hours ago
But load balancer doesn't block the request to HTTPS? And in that case, i have the same problem. I can't point my HTTPS requests to a static ip, if that istance "die", ip change :/
– tidpe
21 hours ago
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53296908%2fgce-managed-group-autoscaling-proxy-load-balancer-for-both-https-and-tcp-r%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown