808: Authenticate backend via cloudfront function #904
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ont secret injection)
chriswilty
force-pushed
the
808-authenticate-backend
branch
2 times, most recently
from
b558eea to
296cead
Compare
chriswilty
force-pushed
the
808-authenticate-backend
branch
from
296cead to
de24e4d
Compare
chriswilty
added a commit
that referenced
this pull request
Apr 25, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Apr 29, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Jul 5, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Jul 15, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Jul 15, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Jul 16, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Sep 25, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Sep 25, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Oct 22, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
chriswilty
added a commit
that referenced
this pull request
Oct 22, 2024
* Prevent unauthorized API access using a CloudFront proxy * Make UI auth opt-in * Correct document loading and cache control
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This work adds authentication to the backend. Rather more complex than the simple authorization function you can use with API Gateway, this instead uses:
Also fixes a case-sensitivity problem that caused React DocViewer to invoke a HEAD request even though file type is already known, for our documents.
Resolves #808
Concerns
Lambda@Edge Functions have no free tier, so every request is going to cost us (though only a fraction of a cent). The limiting factor meaning we cannot use a cheaper, lightweight Cloudfront Function is the time it takes to fetch the JWKS on first usage (cold start). If we can run deployment via CodePipeline, we might be able to download the JWKS from cognito in the build, and inject that into a Cloudfront Function, for a super-fast verification process.
Checklist
Have you done the following?