Contact your Akamai account team to enable this functionality
Cloud Interconnects for Azure offers similar functionality to Cloud Interconnects for Google Cloud, but is not yet offered as a self-serviceable behavior. To enable Cloud Interconnects for Azure, please contact your Akamai account team.
Cloud Interconnects for Azure maximizes traffic flow through Private Network Interconnects (PNIs) established with Microsoft Azure. PNIs are private connections that provide an optimal network path for the traffic sent between the Azure infrastructure and Akamai edge servers.
Cloud Interconnect for Azure enables zero egress costs from Azure for traffic destined for Akamai over these PNIs. It is supported for Azure regions in the following countries:
- North America: North Central US , WestCentralUS, Central US, USEast, USEast-2, USWest, USWest-2
- Europe: EuropeWest, EuropeNorth, Germany, France, UK South, UK West
- Asia:JapanEast, JapanWest, East South East (Singapore), South India, West India
- Australia: Australia East, Australia South
Cloud Interconnects enables optimal routing between Akamai and Azure, but egress savings are applied by Azure and may be subject to additional restrictions by Azure.
Before you enable Cloud Interconnects, make sure you add the cloud hostname to your configuration as part of the Origin Server behavior.
By default, Cloud Interconnects enables the Allow All Methods on Parents Server behavior.
Cloud Interconnects incorporates several features to optimize its use, such as SureRoute and Origin IP Access Control List. It uses origin Access Control List (ACL) to provide you with a small CIDR list that is used by Akamai to access your origin. You can use this CIDR list as an IP ACL that works like SiteShield.
Cloud Interconnects overrides any SureRoute and SiteShield configurations for the cloud origins it applies to. If you have a property with multiple origins, some of which don't use Cloud Interconnects, then you should retain any SureRoute or SiteShield configurations that apply to those origins. However, if after you adopt Cloud Interconnects, no other such alternate origins remain, you may want to remove the SureRoute and SiteShield behaviors to simplify your configuration. See the following table for the summary of different scenarios.
|Azure-only origins on configuration||Multi-cloud origins on configuration|
|SureRoute||Azure origin ignores pre-existing SureRoute behavior. It uses Cloud Interconnects built-in SureRoute feature.
You can remove SureRoute to simplify your configuration.
|Azure origin uses a built-in SureRoute feature as part of the Cloud Interconnects behavior. Other origins use SureRoute standalone behavior.
Don't remove the SureRoute behavior.
|SiteShield||Azure origin ignores pre-existing SiteShield behavior. It uses Cloud Interconnects built-in SiteShield feature.
You can remove the SiteShield behavior to simplify your configuration.
|Azure origin uses the built-in SiteShield Route feature as part of the Cloud Interconnects behavior. Other origins use SiteShield standalone behavior.
Don't remove the SiteShield behavior.
In addition, if you previously enabled SiteShield, update your firewall ACL.
To enable Cloud Interconnects for Azure, contact your Akamai account team. Working with your account team, you will:
- Determine whether your Azure origin is a region in which Akamai has a PNI
- Enable your routing preference within Azure
- Be enabled on the correct map using custom metadata and your new Azure hostname as the origin
- Validate that interconnects are working
- Set up monitoring
For more information about enabling your routing preference, see the following Microsoft Azure documentation:
Updated 28 days ago