FYI: change to aggregation coordinator selection in M119 (currently in Beta)

1,084 views

Skip to first unread message

Akash Nadan

unread,

Oct 19, 2023, 4:32:41 PM10/19/23

to Attribution Reporting API announcements

Hi everyone,

We are planning to implement a change to aggregation coordinator selection in M119 (currently in Beta)

As part of this change, we will be deprecating the “PrivacySandboxAggregationService” parameter. If you are currently doing local testing, then you will need to make the following change to avoid any incompatibility:

Begin using the new parameter “AggregationServiceMultipleCloudProviders:aws_cloud” (default option) or “AggregationServiceMultipleCloudProviders:gcp_cloud” to specify the origin for the GCP public key endpoint.
- Example: --enable_features="AggregationServiceMultipleCloudProviders:aws_cloud/https%3A%2F%2Fmyaws.com/gcp_cloud/https%3A%2F%2Fmygcp.com”
Serve the public key at: origin + .well-known/aggregation-service/v1/public-keys path
- Example: https://myaws.com/.well-known/aggregation-service/v1/public-keys and https://mygcp.com/.well-known/aggregation-service/v1/public-keys in the above example
This change will not have any impact on production testing

Please reach out if you have any questions.

Thanks,

Akash

Reply all

Reply to author

Forward

0 new messages