Describe the bug
If a cache is added between the EC2 instance and RDS, but not between the EC2 instance and S3 then static get requests for S3 will still be forwarded to the cache, causing a reputation loss.
To Reproduce
Create a default setup, add a cache between the EC2 instance and DB. Observe that static 'get' requests to S3 a get routed to cache even though S3 is not behind the cache. This prevents a cache for the DB and a seperate one for S3 which might increase cache hit rates while using less load. (Or at least that's how I would expect it to work.
Expected behavior
EC2 should use the direct link to S3 rather than the cache.
Screenshots
Desktop (please complete the following information):
Describe the bug
If a cache is added between the EC2 instance and RDS, but not between the EC2 instance and S3 then static get requests for S3 will still be forwarded to the cache, causing a reputation loss.
To Reproduce
Create a default setup, add a cache between the EC2 instance and DB. Observe that static 'get' requests to S3 a get routed to cache even though S3 is not behind the cache. This prevents a cache for the DB and a seperate one for S3 which might increase cache hit rates while using less load. (Or at least that's how I would expect it to work.
Expected behavior
EC2 should use the direct link to S3 rather than the cache.
Screenshots
Desktop (please complete the following information):