Skip to content
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

Will AzCopy also be affected by *.azureedge.net going away? #2903

Open
o-l-a-v opened this issue Jan 3, 2025 · 7 comments
Open

Will AzCopy also be affected by *.azureedge.net going away? #2903

o-l-a-v opened this issue Jan 3, 2025 · 7 comments
Assignees

Comments

@o-l-a-v
Copy link

o-l-a-v commented Jan 3, 2025

Dotnet are changing all links pointing to any azureedge.net subdomain because it will likely be taken down shortly.

I guess this affects AzCopy download links to?

Example redirect from https://aka.ms/downloadazcopy-v10-windows goes to https://azcopyvnext.azureedge.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip.

@gapra-msft
Copy link
Member

Hi @o-l-a-v Yes, we have migrated our aka ms links to the updated CDN URLs.

The aka ms links will now point to URLs that start with https://azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net/

@droopy4096
Copy link

@gapra-msft shall we expect https://azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net to remain static moving forward? Automation pieces do rely on ability to fetch specific versions on binaries for specific platforms which would be difficult if above URL were not maintained as "static"

@o-l-a-v
Copy link
Author

o-l-a-v commented Jan 10, 2025

@derdanu
Copy link
Collaborator

derdanu commented Jan 13, 2025

PR already merged and live by @schoag-msft

@vijaytdh
Copy link

I have the same question as @droopy4096 , will azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net be static because we need to whitelist this in our environment (it does not help to use the aks.ms domain because it redirects).

@o-l-a-v
Copy link
Author

o-l-a-v commented Jan 13, 2025

For context to what @vijaytdh asks for. @schoag-msft said dotnet/core#9671 (comment):

Please don't pull from any of the *.azureedge.net or *.azurefd.net for any service - you should be using the custom domains that front the CDN endpoints or the canonical aka.ms links. In the case of AzCopy, those links can always be found at https://aka.ms/downloadazcopy. Each platform we distribute for has its own aka.ms link that points to the most current release.

AFAIK, unless you only want the latest version:

There is currently no domain in front of azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net that can be used to get a specific version?

@vijaytdh
Copy link

vijaytdh commented Jan 13, 2025

For context to what @vijaytdh asks for. @schoag-msft said dotnet/core#9671 (comment):

Please don't pull from any of the *.azureedge.net or *.azurefd.net for any service - you should be using the custom domains that front the CDN endpoints or the canonical aka.ms links. In the case of AzCopy, those links can always be found at https://aka.ms/downloadazcopy. Each platform we distribute for has its own aka.ms link that points to the most current release.

AFAIK, unless you only want the latest version:

There is currently no domain in front of azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net that can be used to get a specific version?

Thanks for the quick response. I probably didn't explain the use case very well:

  • The aka.ms URLs will redirect to azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net
  • So in an environment that does not have unfettered internet access - whitelisting aka.ms doesn't help because it is redirected to another URL under azurefd.net
  • If you don't have the option to whitelist Azure Front door azurefd.net e.g. allow access to anything behind front door - then people would have to whitelist azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net so that's where the question around if that domain is static is coming from. We are aware of aka.ms but sadly it doesn't really help in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants