AWS R53… how to achieve subnet based web application traffic routing to a region
I have DNS service provider(web application) as godaddy with CNAME record resolving to DNS value of application load balancer in @AWS. There is requirement where the webapplication request from customer network should route/resolve to specific AWS region based on IP address /subnet of customer. Is there a feature in R53 or load balancer to achive this. I see there is such feature in mircosoft @azure traffic manager to do subnet based routing!. Thank You
amazon-web-services haproxy amazon-route53 aws-load-balancer
add a comment |
I have DNS service provider(web application) as godaddy with CNAME record resolving to DNS value of application load balancer in @AWS. There is requirement where the webapplication request from customer network should route/resolve to specific AWS region based on IP address /subnet of customer. Is there a feature in R53 or load balancer to achive this. I see there is such feature in mircosoft @azure traffic manager to do subnet based routing!. Thank You
amazon-web-services haproxy amazon-route53 aws-load-balancer
add a comment |
I have DNS service provider(web application) as godaddy with CNAME record resolving to DNS value of application load balancer in @AWS. There is requirement where the webapplication request from customer network should route/resolve to specific AWS region based on IP address /subnet of customer. Is there a feature in R53 or load balancer to achive this. I see there is such feature in mircosoft @azure traffic manager to do subnet based routing!. Thank You
amazon-web-services haproxy amazon-route53 aws-load-balancer
I have DNS service provider(web application) as godaddy with CNAME record resolving to DNS value of application load balancer in @AWS. There is requirement where the webapplication request from customer network should route/resolve to specific AWS region based on IP address /subnet of customer. Is there a feature in R53 or load balancer to achive this. I see there is such feature in mircosoft @azure traffic manager to do subnet based routing!. Thank You
amazon-web-services haproxy amazon-route53 aws-load-balancer
amazon-web-services haproxy amazon-route53 aws-load-balancer
asked Nov 12 '18 at 9:40
CharlesDCharlesD
62
62
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It seems you need Route53's geolocation routing, as it works by mapping the IPs from the originating DNS queries to specific AWS resources, like in your case, the loadbalancer.
Here's a link to the resource: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo
1
Thanks for your response @Bernardo Salazar. Just read the link. looks like its geo location based routing. The routing policy handles traffic based on user geo location and route a specific ip or dns. Not the one i am looking for. Thank you anyways
– CharlesD
Nov 12 '18 at 11:36
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53259392%2faws-r53-how-to-achieve-subnet-based-web-application-traffic-routing-to-a-regi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It seems you need Route53's geolocation routing, as it works by mapping the IPs from the originating DNS queries to specific AWS resources, like in your case, the loadbalancer.
Here's a link to the resource: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo
1
Thanks for your response @Bernardo Salazar. Just read the link. looks like its geo location based routing. The routing policy handles traffic based on user geo location and route a specific ip or dns. Not the one i am looking for. Thank you anyways
– CharlesD
Nov 12 '18 at 11:36
add a comment |
It seems you need Route53's geolocation routing, as it works by mapping the IPs from the originating DNS queries to specific AWS resources, like in your case, the loadbalancer.
Here's a link to the resource: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo
1
Thanks for your response @Bernardo Salazar. Just read the link. looks like its geo location based routing. The routing policy handles traffic based on user geo location and route a specific ip or dns. Not the one i am looking for. Thank you anyways
– CharlesD
Nov 12 '18 at 11:36
add a comment |
It seems you need Route53's geolocation routing, as it works by mapping the IPs from the originating DNS queries to specific AWS resources, like in your case, the loadbalancer.
Here's a link to the resource: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo
It seems you need Route53's geolocation routing, as it works by mapping the IPs from the originating DNS queries to specific AWS resources, like in your case, the loadbalancer.
Here's a link to the resource: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo
answered Nov 12 '18 at 10:11
Bernardo SalazarBernardo Salazar
487
487
1
Thanks for your response @Bernardo Salazar. Just read the link. looks like its geo location based routing. The routing policy handles traffic based on user geo location and route a specific ip or dns. Not the one i am looking for. Thank you anyways
– CharlesD
Nov 12 '18 at 11:36
add a comment |
1
Thanks for your response @Bernardo Salazar. Just read the link. looks like its geo location based routing. The routing policy handles traffic based on user geo location and route a specific ip or dns. Not the one i am looking for. Thank you anyways
– CharlesD
Nov 12 '18 at 11:36
1
1
Thanks for your response @Bernardo Salazar. Just read the link. looks like its geo location based routing. The routing policy handles traffic based on user geo location and route a specific ip or dns. Not the one i am looking for. Thank you anyways
– CharlesD
Nov 12 '18 at 11:36
Thanks for your response @Bernardo Salazar. Just read the link. looks like its geo location based routing. The routing policy handles traffic based on user geo location and route a specific ip or dns. Not the one i am looking for. Thank you anyways
– CharlesD
Nov 12 '18 at 11:36
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f53259392%2faws-r53-how-to-achieve-subnet-based-web-application-traffic-routing-to-a-regi%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