You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tile requests come into the CloudFront distribution (as they do already)
CloudFront sends them to an S3 Website set up to serve a bucket of cached tiles
The S3 website configuration is set to redirect back to the CloudFront distribution, prepending latest/ to the request path
The CloudFront distribution sends all requests that start with latest/ to the API gateway
The first request for a tile will thus be filled by API Gateway, i.e. by an actual Lambda function spinning up and making the tile. But before returning it, the Lambda function will write the tile to the bucket so later requests for the same tile will find it there. The code changes are in a separate issue: #635.
So the task is to set up the Terraform config to provision CloudFront and S3. Until the code side is done, all requests will fall back to the API gateway (though we could manually add tiles to the bucket to test the cache response).
The text was updated successfully, but these errors were encountered:
See the issue comment and branch. The idea is to set things up so that
latest/
to the request pathlatest/
to the API gatewayThe first request for a tile will thus be filled by API Gateway, i.e. by an actual Lambda function spinning up and making the tile. But before returning it, the Lambda function will write the tile to the bucket so later requests for the same tile will find it there. The code changes are in a separate issue: #635.
So the task is to set up the Terraform config to provision CloudFront and S3. Until the code side is done, all requests will fall back to the API gateway (though we could manually add tiles to the bucket to test the cache response).
The text was updated successfully, but these errors were encountered: