Otdfbt

Does it make sense to use a wavelet that is equal to a sine of one period?

Parsing text written the millitext font

Create a cube from identical 3D objects

How to befriend someone who doesn't like to talk?

A life of PhD: is it feasible?

Suppose leased car is totalled: what are financial implications?

Why is it bad to use your whole foot in rock climbing

How (un)safe is it to ride barefoot?

What is the proper event in Extended Events to track stored procedure executions?

Professor Roman loves to teach unorthodox Chemistry

How to make a composition of functions prettier?

Make Gimbap cutter

Is it safe to dpkg --set-selections on a newer version of a distro?

Are regulatory compliance checks performed within the EU bloc?

Magento 2 | Is there an observable event for when the checkout begins?

What's the difference between DHCP and NAT? Are they mutually exclusive?

Is it advisable to add a location heads-up when a scene changes in a novel?

What does "lit." mean in boiling point or melting point specification?

Why is long-term living in Almost-Earth causing severe health problems?

Forgot passport for Alaska cruise (Anchorage to Vancouver)

What is this object?

Who is "He that flies" in Lord of the Rings?

C++ logging library

Are the guests in Westworld forbidden to tell the hosts that they are robots?

AWS Cloudfront Usecase: Geolocation For Web App With Cookies and Query String Params

AWS cloudfront with SNI + ELB with 443 to 80 redirection to EC2 issueHow to set up AWS Cloudfront for dynamic number of domains for a dynamic site?No Cache-Control Header for files from AWS CloudFront with S3 OriginEC2 with AWS CloudFront?Amazon route 53 + cloudfront + s3 -> with angularjs2 app in ec2AWS CloudFront doesn't find my ELB as an origin in Mumbai regionBlue/green deployment - AWS Cloudfront with ELB as custom originAWS deploying strategy for cached page/appSend custom Host header with CloudFrontIs it possible to avoid costs for invalid requests at AWS S3 or cloudfront during a DDoS attack?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

0

I want to make sure I have the correct usecase for AWS Cloudfront.

Typically I believe it is used to cache static assets, such as those put in AWS S3 storage.

For example, it may end up looking like this, in front of S3:

But I want my application to server different content based on geolocation. So I've put a Cloudfront in front of my ELB as well, so it can forward the CloudFront-Viewer-Country header to my ELB, to my EC2 (where my application sits).

But this application needs to be passed query strings, cookies (for logins) and allow post requests, etc etc that make the cache not really work / slow down the cache / aren't cached. So basically, if I'm just using the cache for geolocation and not much else, is there a way to configure it for this? Is it considered bad practice to put a cache like this in front of a dynamic application that will just water it down? It seems like a bad use case to just use it for geolocaton and not really to cache requests, especially if I have images in an S3 as well behind a separate CloudFront? Or is this fine? Can Cloudfront do full HTML caching so my server/database is almost never hit as an added bonus to geolocation to add more to its usecase when in front of an ELB?

Geolocation is a requirement for me, just not sure that Cloudfront is the right tool, or at the very least I want to make sure I'm not impacting performance by using it this way... if I'm basically paying for it to do geolocation and not serve as a cache in this case that's fine with me, I just don't want it to have an adverse effect.

amazon-web-services amazon-elb amazon-cloudfront

share|improve this question

asked May 27 at 23:08

Summer DeveloperSummer Developer

1319

add a comment | 

0

I want to make sure I have the correct usecase for AWS Cloudfront.

Typically I believe it is used to cache static assets, such as those put in AWS S3 storage.

For example, it may end up looking like this, in front of S3:

But I want my application to server different content based on geolocation. So I've put a Cloudfront in front of my ELB as well, so it can forward the CloudFront-Viewer-Country header to my ELB, to my EC2 (where my application sits).

But this application needs to be passed query strings, cookies (for logins) and allow post requests, etc etc that make the cache not really work / slow down the cache / aren't cached. So basically, if I'm just using the cache for geolocation and not much else, is there a way to configure it for this? Is it considered bad practice to put a cache like this in front of a dynamic application that will just water it down? It seems like a bad use case to just use it for geolocaton and not really to cache requests, especially if I have images in an S3 as well behind a separate CloudFront? Or is this fine? Can Cloudfront do full HTML caching so my server/database is almost never hit as an added bonus to geolocation to add more to its usecase when in front of an ELB?

Geolocation is a requirement for me, just not sure that Cloudfront is the right tool, or at the very least I want to make sure I'm not impacting performance by using it this way... if I'm basically paying for it to do geolocation and not serve as a cache in this case that's fine with me, I just don't want it to have an adverse effect.

amazon-web-services amazon-elb amazon-cloudfront

share|improve this question

asked May 27 at 23:08

Summer DeveloperSummer Developer

1319

add a comment | 

I want to make sure I have the correct usecase for AWS Cloudfront.

Typically I believe it is used to cache static assets, such as those put in AWS S3 storage.

For example, it may end up looking like this, in front of S3:

But I want my application to server different content based on geolocation. So I've put a Cloudfront in front of my ELB as well, so it can forward the CloudFront-Viewer-Country header to my ELB, to my EC2 (where my application sits).

But this application needs to be passed query strings, cookies (for logins) and allow post requests, etc etc that make the cache not really work / slow down the cache / aren't cached. So basically, if I'm just using the cache for geolocation and not much else, is there a way to configure it for this? Is it considered bad practice to put a cache like this in front of a dynamic application that will just water it down? It seems like a bad use case to just use it for geolocaton and not really to cache requests, especially if I have images in an S3 as well behind a separate CloudFront? Or is this fine? Can Cloudfront do full HTML caching so my server/database is almost never hit as an added bonus to geolocation to add more to its usecase when in front of an ELB?

Geolocation is a requirement for me, just not sure that Cloudfront is the right tool, or at the very least I want to make sure I'm not impacting performance by using it this way... if I'm basically paying for it to do geolocation and not serve as a cache in this case that's fine with me, I just don't want it to have an adverse effect.

amazon-web-services amazon-elb amazon-cloudfront

share|improve this question

asked May 27 at 23:08

Summer DeveloperSummer Developer

1319

share|improve this question

asked May 27 at 23:08

Summer DeveloperSummer Developer

1319

share|improve this question

asked May 27 at 23:08

Summer DeveloperSummer Developer

1319

asked May 27 at 23:08

Summer DeveloperSummer Developer

1319

asked May 27 at 23:08

Summer DeveloperSummer Developer

1319