AWS Cloudfront with Geolocation policy vs Route53

Can we use CloudFront with Geolocation policy or Cloudfront internally have this feature and can be used alone to satisfy? Or Route53 is correct option while having requirement to serve request from nearest geo-location for global website to improve the customer experience.

Also, i am not clear whether we can use both cloudfront with Route53 together or not ?
Thanks.

edited Jan 2 at 9:37

Andy Aldo

673623

asked Jan 2 at 8:08

Vinay

add a comment |

Also, i am not clear whether we can use both cloudfront with Route53 together or not ?
Thanks.

edited Jan 2 at 9:37

Andy Aldo

673623

asked Jan 2 at 8:08

Vinay

add a comment |

Also, i am not clear whether we can use both cloudfront with Route53 together or not ?
Thanks.

edited Jan 2 at 9:37

Andy Aldo

673623

asked Jan 2 at 8:08

Vinay

Also, i am not clear whether we can use both cloudfront with Route53 together or not ?
Thanks.

amazon-web-services amazon-cloudfront amazon-route53

edited Jan 2 at 9:37

Andy Aldo

673623

asked Jan 2 at 8:08

Vinay

edited Jan 2 at 9:37

Andy Aldo

673623

asked Jan 2 at 8:08

Vinay

edited Jan 2 at 9:37

Andy Aldo

673623

edited Jan 2 at 9:37

Andy Aldo

673623

edited Jan 2 at 9:37

Andy Aldo

673623

asked Jan 2 at 8:08

Vinay

asked Jan 2 at 8:08

Vinay

asked Jan 2 at 8:08

Vinay

add a comment |

2 Answers
2

active

oldest

votes

Yes, You can use Route53 along with CloudFront for the best results with Alias records (When you purchase your domain with AWS only if you purchased it from outside AWS then you can directly configured/add your CloudFront details there as in this case adding Route53 will increase the number of ip visits. Read More here).

CloudFront will distribute your content over 100+ edge location which will decrease your response time with low latency and save your cost as well. It will deliver the content from the nearest location.

Route53 will manage your DNS things.

CloudFront is more than enough for the delivery of content from the nearest edge location. It will also help you to copy data to multiple edge locations as well.

It's like Content Delivery Network(CloudFront) + DNS(Route53).

Read this for good understanding.

When you create a web distribution, you specify where CloudFront sends requests for the files that it distributes to edge locations. CloudFront supports using Amazon S3 buckets and HTTP servers (for example, web servers) as origins.

Route53 is a DNS service and is an origin for data. The term Origin is a term for where the original data resides before it is cached in the CDN (CloudFront).

edited Jan 4 at 6:02

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

Thanks Shivang, I got my answer we can use Route 53 and CloudFront together. However, i am not clear on one thing, one response says it will not help much if we use both together but your response shows more positiveness and says it will bring best results while use both together. Now, is it really overhead or this is good to use ? Based on your experience if you can let me know What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:41

@Vinay I have edited my answer. Please accept it as answer if it's resolved your query.

– Shivang Agarwal
Jan 4 at 6:03

Thanks for your response.! It helps.

– Vinay
Jan 4 at 19:28

add a comment |

Both cloudfront and Route53 have different purpose.Route 53 is a DNS service whereas Cloudfront is CDN service to serve static (and dynamic) content.

You can use the cloudfront with Route 53 Geolocation Routing. But the location wise content delivery is already enabled in cloudfront, so geolocation policy wont help that much. If you are not using cloudfront and you want to distribute traffic based on user location, then you can use Route53 geolocation policy to route traffic to the nearest app server though ELB (elastic load balancer).For example, you might want all queries from Europe to be routed to an ELB load balancer in the Frankfurt region. So here you are deciding which server is going to server the traffic from specific region. but in case of cloudfront, it caches the content at the nearest data center ( edge location), when the first request is hit. And next request from that region are automatically served through that edge location.

Cloudfront: It is a web service that speeds up distribution of your static and dynamic web content, such as .html, .css, .js, and image files, to your users. The content is cached at edge location (data center). In cloudfront you specify the distribution from where the content needs to be server.

Route 53: Its a DNS service which provide translation of your easily remember DNS name (like google.com) into more complex server name serving the actual content.

You can use cloudfront and Route53 together by creating alias record in route 53 which points to your cloudfront distribution.

edited Jan 4 at 4:36

answered Jan 2 at 9:48

Sangam Belose

2,03941828

Thanks Sangam for your reply. I got some information however, also raise one question on your response related to whether it is good practice or not. What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:44

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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54003091%2faws-cloudfront-with-geolocation-policy-vs-route53%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

Route53 will manage your DNS things.

CloudFront is more than enough for the delivery of content from the nearest edge location. It will also help you to copy data to multiple edge locations as well.

It's like Content Delivery Network(CloudFront) + DNS(Route53).

Read this for good understanding.

Route53 is a DNS service and is an origin for data. The term Origin is a term for where the original data resides before it is cached in the CDN (CloudFront).

edited Jan 4 at 6:02

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

Thanks Shivang, I got my answer we can use Route 53 and CloudFront together. However, i am not clear on one thing, one response says it will not help much if we use both together but your response shows more positiveness and says it will bring best results while use both together. Now, is it really overhead or this is good to use ? Based on your experience if you can let me know What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:41

@Vinay I have edited my answer. Please accept it as answer if it's resolved your query.

– Shivang Agarwal
Jan 4 at 6:03

Thanks for your response.! It helps.

– Vinay
Jan 4 at 19:28

add a comment |

Route53 will manage your DNS things.

CloudFront is more than enough for the delivery of content from the nearest edge location. It will also help you to copy data to multiple edge locations as well.

It's like Content Delivery Network(CloudFront) + DNS(Route53).

Read this for good understanding.

Route53 is a DNS service and is an origin for data. The term Origin is a term for where the original data resides before it is cached in the CDN (CloudFront).

edited Jan 4 at 6:02

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

Thanks Shivang, I got my answer we can use Route 53 and CloudFront together. However, i am not clear on one thing, one response says it will not help much if we use both together but your response shows more positiveness and says it will bring best results while use both together. Now, is it really overhead or this is good to use ? Based on your experience if you can let me know What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:41

@Vinay I have edited my answer. Please accept it as answer if it's resolved your query.

– Shivang Agarwal
Jan 4 at 6:03

Thanks for your response.! It helps.

– Vinay
Jan 4 at 19:28

add a comment |

Route53 will manage your DNS things.

CloudFront is more than enough for the delivery of content from the nearest edge location. It will also help you to copy data to multiple edge locations as well.

It's like Content Delivery Network(CloudFront) + DNS(Route53).

Read this for good understanding.

Route53 is a DNS service and is an origin for data. The term Origin is a term for where the original data resides before it is cached in the CDN (CloudFront).

edited Jan 4 at 6:02

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

Route53 will manage your DNS things.

CloudFront is more than enough for the delivery of content from the nearest edge location. It will also help you to copy data to multiple edge locations as well.

It's like Content Delivery Network(CloudFront) + DNS(Route53).

Read this for good understanding.

Route53 is a DNS service and is an origin for data. The term Origin is a term for where the original data resides before it is cached in the CDN (CloudFront).

edited Jan 4 at 6:02

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

edited Jan 4 at 6:02

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

answered Jan 2 at 9:43

Shivang Agarwal

1,110615

Thanks Shivang, I got my answer we can use Route 53 and CloudFront together. However, i am not clear on one thing, one response says it will not help much if we use both together but your response shows more positiveness and says it will bring best results while use both together. Now, is it really overhead or this is good to use ? Based on your experience if you can let me know What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:41

@Vinay I have edited my answer. Please accept it as answer if it's resolved your query.

– Shivang Agarwal
Jan 4 at 6:03

Thanks for your response.! It helps.

– Vinay
Jan 4 at 19:28

add a comment |

Thanks Shivang, I got my answer we can use Route 53 and CloudFront together. However, i am not clear on one thing, one response says it will not help much if we use both together but your response shows more positiveness and says it will bring best results while use both together. Now, is it really overhead or this is good to use ? Based on your experience if you can let me know What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:41

@Vinay I have edited my answer. Please accept it as answer if it's resolved your query.

– Shivang Agarwal
Jan 4 at 6:03

Thanks for your response.! It helps.

– Vinay
Jan 4 at 19:28

Thanks Shivang, I got my answer we can use Route 53 and CloudFront together. However, i am not clear on one thing, one response says it will not help much if we use both together but your response shows more positiveness and says it will bring best results while use both together. Now, is it really overhead or this is good to use ? Based on your experience if you can let me know What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:41

@Vinay I have edited my answer. Please accept it as answer if it's resolved your query.

– Shivang Agarwal
Jan 4 at 6:03

Thanks for your response.! It helps.

– Vinay
Jan 4 at 19:28

add a comment |

Both cloudfront and Route53 have different purpose.Route 53 is a DNS service whereas Cloudfront is CDN service to serve static (and dynamic) content.

You can use the cloudfront with Route 53 Geolocation Routing. But the location wise content delivery is already enabled in cloudfront, so geolocation policy wont help that much. If you are not using cloudfront and you want to distribute traffic based on user location, then you can use Route53 geolocation policy to route traffic to the nearest app server though ELB (elastic load balancer).For example, you might want all queries from Europe to be routed to an ELB load balancer in the Frankfurt region. So here you are deciding which server is going to server the traffic from specific region. but in case of cloudfront, it caches the content at the nearest data center ( edge location), when the first request is hit. And next request from that region are automatically served through that edge location.

Route 53: Its a DNS service which provide translation of your easily remember DNS name (like google.com) into more complex server name serving the actual content.

You can use cloudfront and Route53 together by creating alias record in route 53 which points to your cloudfront distribution.

edited Jan 4 at 4:36

answered Jan 2 at 9:48

Sangam Belose

2,03941828

Thanks Sangam for your reply. I got some information however, also raise one question on your response related to whether it is good practice or not. What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:44

add a comment |

Both cloudfront and Route53 have different purpose.Route 53 is a DNS service whereas Cloudfront is CDN service to serve static (and dynamic) content.

You can use the cloudfront with Route 53 Geolocation Routing. But the location wise content delivery is already enabled in cloudfront, so geolocation policy wont help that much. If you are not using cloudfront and you want to distribute traffic based on user location, then you can use Route53 geolocation policy to route traffic to the nearest app server though ELB (elastic load balancer).For example, you might want all queries from Europe to be routed to an ELB load balancer in the Frankfurt region. So here you are deciding which server is going to server the traffic from specific region. but in case of cloudfront, it caches the content at the nearest data center ( edge location), when the first request is hit. And next request from that region are automatically served through that edge location.

Route 53: Its a DNS service which provide translation of your easily remember DNS name (like google.com) into more complex server name serving the actual content.

You can use cloudfront and Route53 together by creating alias record in route 53 which points to your cloudfront distribution.

edited Jan 4 at 4:36

answered Jan 2 at 9:48

Sangam Belose

2,03941828

Thanks Sangam for your reply. I got some information however, also raise one question on your response related to whether it is good practice or not. What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:44

add a comment |

Both cloudfront and Route53 have different purpose.Route 53 is a DNS service whereas Cloudfront is CDN service to serve static (and dynamic) content.

You can use the cloudfront with Route 53 Geolocation Routing. But the location wise content delivery is already enabled in cloudfront, so geolocation policy wont help that much. If you are not using cloudfront and you want to distribute traffic based on user location, then you can use Route53 geolocation policy to route traffic to the nearest app server though ELB (elastic load balancer).For example, you might want all queries from Europe to be routed to an ELB load balancer in the Frankfurt region. So here you are deciding which server is going to server the traffic from specific region. but in case of cloudfront, it caches the content at the nearest data center ( edge location), when the first request is hit. And next request from that region are automatically served through that edge location.

Route 53: Its a DNS service which provide translation of your easily remember DNS name (like google.com) into more complex server name serving the actual content.

You can use cloudfront and Route53 together by creating alias record in route 53 which points to your cloudfront distribution.

edited Jan 4 at 4:36

answered Jan 2 at 9:48

Sangam Belose

2,03941828

Both cloudfront and Route53 have different purpose.Route 53 is a DNS service whereas Cloudfront is CDN service to serve static (and dynamic) content.

You can use the cloudfront with Route 53 Geolocation Routing. But the location wise content delivery is already enabled in cloudfront, so geolocation policy wont help that much. If you are not using cloudfront and you want to distribute traffic based on user location, then you can use Route53 geolocation policy to route traffic to the nearest app server though ELB (elastic load balancer).For example, you might want all queries from Europe to be routed to an ELB load balancer in the Frankfurt region. So here you are deciding which server is going to server the traffic from specific region. but in case of cloudfront, it caches the content at the nearest data center ( edge location), when the first request is hit. And next request from that region are automatically served through that edge location.

Route 53: Its a DNS service which provide translation of your easily remember DNS name (like google.com) into more complex server name serving the actual content.

You can use cloudfront and Route53 together by creating alias record in route 53 which points to your cloudfront distribution.

edited Jan 4 at 4:36

answered Jan 2 at 9:48

Sangam Belose

2,03941828

edited Jan 4 at 4:36

answered Jan 2 at 9:48

Sangam Belose

2,03941828

answered Jan 2 at 9:48

Sangam Belose

2,03941828

answered Jan 2 at 9:48

Sangam Belose

2,03941828

Thanks Sangam for your reply. I got some information however, also raise one question on your response related to whether it is good practice or not. What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:44

add a comment |

Thanks Sangam for your reply. I got some information however, also raise one question on your response related to whether it is good practice or not. What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:44

Thanks Sangam for your reply. I got some information however, also raise one question on your response related to whether it is good practice or not. What is industry wide acceptable pattern for such use cases ?

– Vinay
Jan 3 at 15:44

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Bdtjtk