-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jurisdiction support for GDPR & FedRAMP #34
base: main
Are you sure you want to change the base?
Conversation
Keep in mind that |
Well, this explains so much. Thanks @daliborgogic! |
Maybe I spoke a little too quickly before consuming coffee. After taking another look at the code, am I not already trying to apply the jurisdiction to the Durable Object?
Unless I'm missing a bigger piece here. Thoughts @daliborgogic? |
Need to check if if (env.JURISDICTION && request.cf.jurisdiction) {
// If jurisdiction is specified, it takes precedence over region
} else {
// Fall back to region-based routing if no jurisdiction is specified
} edit: regarding GDPR & FedRAMP imho is better to use Regional Services. Because Workers may still access Durable Objects constrained to a jurisdiction from anywhere in the world. |
Thanks for pointing that out @daliborgogic :) I don't disagree that Regional Services is the better approach for GDPR and FedRAMP compliance – however, there's no good way to enforce those rules via Wrangler. It would be wonderful if I could declare it in my
Going back to your previous suggestion... When I do as suggested, I still don't see the
|
"Durable Objects do not currently change locations after they are created."
My mistake, sorry. I'll try to do a minimal reproduction |
Purpose
This code allows users to deploy their durable objects in a manner that adheres to GDPR protocol. Values you can choose for
JURISDICTION
in your wrangler file include:eu
fedramp
If no entry exists for
JURISDICTION
then it will fallback to using theREGION
as a suggested deployment region, and if no region is specified then a normal deployment happens where the first request origin location to the DO is likely where the DO will exist.Tasks
colo
value adheres toeu
andfedramp
locations in the following cURLVerify
Currently it appears we are receiving errors when deploying the durable object and attempting to access it with the above cURL. Here is the stacktrace:
Before
After