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
Copy file name to clipboardExpand all lines: doc/readme.md
+2-8Lines changed: 2 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -208,7 +208,7 @@ since it only contains non-secret information:
208
208
* The expiration time of the access
209
209
210
210
* The username of the person that generated the token
211
-
211
+
212
212
* A free-text field describing the granted access
213
213
214
214
Since the party issuing tokens, and the party verifying tokens are the same, we
@@ -231,13 +231,7 @@ Cache-key][CF-cache-cookie].
231
231
232
232
Normally, you can configure a generic Lambda function via Environment Variables.
233
233
Lambda@Edge is tricky in this regard, since it does not support Environment
234
-
Variables. We worked around this issue by abusing the Tags.
235
-
236
-
The configuration itself is stored in an S3 bucket as JSON files. The name of
237
-
this S3 bucket is passed as a regular environment variable to the Python Lambda
238
-
functions, but as a Tag to the Lambda@Edge function. The Lambda@Edge function
239
-
performs a `lambda:GetFunction` on itself (it can find out its own name from the
240
-
`context` object at runtime) to read its own Tags.
234
+
Variables. In order protect this critical internet-facing infrastructure, we limit dependencies to other services. Config is stored locally and can be updated based on environment (account id) with specific config files. It is critical to keep this configuration in sync with reality.
0 commit comments