On Tue, Dec 10, 2024 at 11:09:59PM -0700, David Fifield via anti-censorship-team wrote:
I did try setting up a Front Door CDN profile (which is the recommended replacement for Edgio), following the migration instructions: https://learn.microsoft.com/en-us/azure/frontdoor/migrate-cdn-to-front-door I got the hostname: snowflake-broker-hadmaqbnc4dmcffs.z03.azurefd.net It works as an alias for the broker: curl -i https://snowflake-broker-hadmaqbnc4dmcffs.z03.azurefd.net/debug However, it apparently does not work with domain fronting, so is likely not actually useful. Front Door not working with domain fronting is consistent with prior announcements by Azure: https://github.com/net4people/bbs/issues/67
The Azure CDN invoice was much higher in December 2024 than usual – 24.43 USD, when usually it is less than 1 USD.
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-cos...
Almost all the cost is attributable to the Azure Front Door profile I set up as a test on 2024-12-11. The invoice breaks down as follows:
$22.63 Azure Front Door - Standard - Zone 1 $1.28 Azure CDN from Verizon - Standard - Zone 1 $0.53 Azure CDN from Verizon - Standard - Zone 2
"Azure CDN from Verizon" is the old Edgio CDN endpoint, which is due to stop working soon. "Azure Front Door" is the new CDN endpoint I set up as a test, which does not support domain fronting.
I thought at first that the cause was people using the new CDN profile, despite the lack of domain fronting, but I checked and the amount of traffic on the endpoint is practically zero. The explanation is actually that Azure Front Door is billed on an hourly basis, in addition to charging for the amount of traffic. There's a "base fee" per hour that works out to 35 USD per month.
https://azure.microsoft.com/en-in/pricing/details/frontdoor/ https://learn.microsoft.com/en-in/azure/frontdoor/billing
I'm going to delete the snowflake-broker-hadmaqbnc4dmcffs.z03.azurefd.net profile now.