Network Edge

142 Topics

3 Multicloud Network Designs for Simplified Multicloud Connectivity
If your organization is juggling multiple clouds, there’s a good chance network complexity is clogging progress. What if there were structured, strategic configurations that simplify multicloud connectivity—so you could scale with confidence and clarity?
ebaichtal
14 days ago Place What's New
24Views
0likes
0Comments
The Data Center is Evolving - Are You?
Times moves fast...don't they? As the line between public and private cloud continues to blur, we're seeing the very definition of "data center" evolve right alongside it. Colocation, edge, interconnection - these aren't just technologies anymore. They're becoming foundational building blocks in how hybrid cloud actually operates today. We used to think of hybrid as static: pair a hyperscaler with some on-prem gear and bada-bing, bada-boom, call it a day...right? Wrong. That model no longer cuts it. Now, we're watching new hybrid patterns emerge that are more agile, distributed, and value-driven. Let's face it, it's no longer about where the workloads are - it's about how infrastructure adapts to optimize performance, cost, and connectivity in real-time. What are you seeing in your markets? Are you rethinking their hybrid strategies through the lens of colocation and interconnection? Are edge facilities shifting the center of gravity? Would love to hear your take - what are your thoughts?
bjones
20 days ago Place Discussions
32Views
0likes
0Comments
Simplify App Delivery and Security with F5 and Equinix
Want to simplify global application deployment and secure partner access without physical infrastructure? Join F5 and Equinix on our upcoming webinar to discover how F5 Distributed Cloud Services on Equinix Network Edge can help you accelerate time-to-market, optimize costs, and maintain compliance. Secure your spot now by RSVPing here and learn how to simplify infrastructure for distributed AI applications. Featured Speakers: Rahul Phadke, Director of Product Management at F5 Joe Kanagusuku, Business Development Manager at F5 Mandar Joshi, Director of Product Management at Equinix
mjoshi
24 days ago Place Events
29Views
1like
0Comments
New Term-Based Discounts for Equinix Fabric Are Here
We're excited to introduce Equinix Fabric Term-Based Discounts for inter-metro i.e. remote virtual connections (VCs) between your own assets and to your service providers including hyperscalers such as AWS, Azure, Google Cloud and Oracle. This new pricing option is designed to help you save more while enjoying the high-performance connectivity you rely on. What's New? You now have the option to select 12, 24, or 36-month contracts for inter-metro VCs from your Fabric ports, Network Edge virtual devices and Fabric Cloud Router instances. Here's how you'll benefit: Lower Monthly Rates: Save between 15% and 50% compared to on-demand pricing. For example, a 1 Gbps inter-metro virtual connection between London to New York drops from $1005/month to just $503/month with a 36-month term-based plan. See how much you can save using the Fabric pricing calculator, accessible via the Fabric portal. Simple Provisioning: No approvals required. Just select your term in the self-service portal or Fabric API and enjoy the savings. Broad Capability Support: Applicable across Point-to-Point (EPL & EVPL), Multipoint-to-Multipoint (EP-LAN & EVP-LAN) and IP-WAN services supported by Fabric Cloud Router. Also supported for Z-side service tokens. Predictable Cost Structure: Term based contracts provided set monthly rates, making it easier for you to manage your annual budget. Things to Note Discounts are available only for inter-metro VCs (intra-metro i.e. local VCs are not eligible. Discounts are currently not supported on Network Edge virtual devices to AWS, but are coming soon. Term-based discounts cannot be added to existing VCs, so you’ll need to create a new VC with your chosen term. Why This Matters By locking in discounted rates, you can optimize costs and achieve predictable spending without sacrificing performance, reliability, or flexibility. This is the perfect opportunity to create cost-efficient connectivity solutions tailored to the demands of your business. We'd Love to Hear From You Tap into these savings today by selecting a term-based discount during your next VC provisioning. We’d love to hear how this pricing option benefits your operations. Share your feedback with the team!
GiannaDavis
4 months ago Place What's New
84Views
4likes
0Comments
Issues deploying Equinix Connections
I have managed to use several terraform modules without problem. I have used the palo alto cloudgenix vm modules, palo alto firewalls modules, device link modules, and fabric cloud router module. All work okay on the lastest version of equinix/equinix. However as I dive into other connections I get a lot version issues. For example. Leveraging the cloud-router-port connection. https://registry.terraform.io/modules/equinix/fabric/equinix/latest/examples/cloud-router-2-port-connection This would be used to connect the cloud router to the pa firewall mgmt interface. Documentation covers the following version. required_providers { equinix = { source = "equinix/equinix" version = ">= 2.9.0" } } } But code doesnt work without this version terraform { required_providers { equinix = { source = "equinix/equinix" version = "~> 1.26.0" } } } When using new versions error occurs. Failure. Ive redone this several times in my code base. ephemeral.aws_secretsmanager_secret_version.equinix_iac_credentials: Opening... ephemeral.aws_secretsmanager_secret_version.equinix_iac_credentials: Opening complete after 0s module.equinix_deployment.module.fw-mgmt-to-fcr-connection-ch-1a.equinix_fabric_connection.this: Creating... ╷ │ Error: 400 Bad Request Code: EQ-3142558, Message: Json syntax error, please check request body, Details: Unknown json property : aSide.accessPoint.router.package.code. Unexpected value '' │ │ with module.equinix_deployment.module.fw-mgmt-to-fcr-connection-ch-1a.equinix_fabric_connection.this, │ on ..\..\modules\cloud-router-2-port-connection\main.tf line 1, in resource "equinix_fabric_connection" "this": │ 1: resource "equinix_fabric_connection" "this" { I can get past this error and deploy the connection with an older version but then run into version issues when attempting to leverage the virtual-device-2-eia-connection https://registry.terraform.io/modules/equinix/fabric/equinix/latest/examples/virtual-device-2-eia-connection here the primary problem is that on older versions. there is no resource virtual-device-connection. only fabric-device-connection. One thought is to completely separate the fabric cloud router to port module Here is the original cloud router to port module main.tf resource "equinix_fabric_connection" "this" { name = var.connection_name type = var.connection_type bandwidth = var.bandwidth notifications { type = var.notifications_type emails = var.notifications_emails } a_side { access_point { type = "CLOUD_ROUTER" router { uuid = var.aside_fcr_uuid } } } z_side { access_point { type = var.zside_ap_type virtual_device { type = var.zside_vd_type uuid = var.zside_vd_uuid } interface { type = var.zside_interface_type id = var.zside_interface_id } location { metro_code = var.zside_location } } } order { purchase_order_number = var.purchase_order_number } } variables variable "connection_name" { type = string description = "Name of the Fabric connection" } variable "connection_type" { type = string description = "Type of the Fabric connection (e.g., IP_VC)" } variable "bandwidth" { type = number description = "Connection bandwidth in Mbps" } variable "notifications_type" { type = string default = "ALL" description = "Notification type" } variable "notifications_emails" { type = list(string) description = "Emails for notifications" } variable "purchase_order_number" { type = string default = "" } variable "aside_fcr_uuid" { type = string description = "UUID of the FCR device" } variable "zside_ap_type" { type = string default = "VD" } variable "zside_vd_type" { type = string default = "EDGE" } variable "zside_vd_uuid" { type = string } variable "zside_interface_type" { type = string default = "NETWORK" } variable "zside_interface_id" { type = number } variable "zside_location" { type = string } versions.tf terraform { required_providers { equinix = { source = "equinix/equinix" version = "~> 1.26.0" } } } module module "fw-mgmt-to-fcr-connection-ch-1a" { #FCR Router to FW Management Interface Connection source = "../../modules/cloud-router-2-port-connection" connection_name = "fcr-2-fw-mgmt-ch" connection_type = "IP_VC" bandwidth = 50 notifications_type = "ALL" notifications_emails = var.notifications purchase_order_number = "mgmt-connection" #aside Fabric Cloud Router aside_fcr_uuid = module.fcr_ch.id #zside Palo aAlto Firewall zside_ap_type = "VD" #Virtual Device zside_vd_type = "EDGE" zside_vd_uuid = module.pa_vm_ch.id zside_interface_type = "NETWORK" zside_interface_id = 1 # Palo Alto Firewall Management Port zside_location = "CH" #metro code }
Solved
mikecalabrese
5 months ago Place Discussions
187Views
1like
5Comments
Terraform Module Equinix Internet Access. Does it exist?
I scavenged the terraform registry looking for a Equinix Internet Access Terraform module. ] I found an example of a connection to EIA.This is the only thing that comes up in the registry as EIA. https://github.com/equinix/terraform-equinix-fabric/tree/v0.22.0/examples/virtual-device-2-eia-connection But none that creates the EIA itself. Can anyone answer if this may or may not be supported in terraform and if so, what would the resource name be for it? The GUI terminology doesn't always translate one for one, so maybe I'm missing something.
mikecalabrese
5 months ago Place Discussions
80Views
0likes
2Comments
Creating an Azure ExpressRoute and Virtual Connections in the Fabric Portal
In this video, we'll cover how to create an Azure ExpressRoute and Virtual Connections in the Fabric Portal. We start by locating our resource group in the Azure Portal and creating a new ExpressRoute in Azure. Then we head back to the Fabric Portal and create a connection to the new ExpressRoute. Once that's established, we'll head back over to the Azure Portal to configure Private Peering and we wrap it up by confirming the device interfaces of our new connection in the Virtual Device Inventory. Connect to Azure ExpressRoute through the Fabric Portal today: https://fabric.equinix.com/
shanzlafayette
5 months ago Place Videos & Guides
37Views
0likes
0Comments
Creating a Virtual Connection with AWS Direct Connect
In this video, we'll cover how to create a virtual connection with AWS Direct Connect from a Network Edge device. First we'll configure a new connection in the Fabric Portal, then locate and accept the connection in the AWS Portal. We'll create a virtual interface, demonstrate how to connect it on the Equinix side and configure the router bgp. Finally, we'll cover how to de-provision the connection on both the AWS and Equinix side. Create a new connection in the Fabric Portal today: https://fabric.equinix.com/
shanzlafayette
5 months ago Place Videos & Guides
9Views
0likes
0Comments
How to Choose Between Network Edge and Fabric Cloud Router
Here's a quick breakdown to help you compare Network Edge and Fabric Cloud Router for your next deployment. Learn more about Fabric Cloud Router
Kevin_Odom
5 months ago Place Videos & Guides
20Views
1like
0Comments
Service Token Feature Enhancements
In this video, we'll show you how to create Z-side Service Tokens and connect them to Network Edge devices and Multipoint Networks. We'll begin by providing a high-level overview of Service Tokens and compare and contrast them with Network Edge Service Profiles. Then we'll create a Z-side Service Token and connect it with a Network Edge Device. Next, we'll create a Z-side Service Token and connect it with a Multipoint Network. Head to the Fabric Portal to create a Service Token today: https://portal.equinix.com/
Kevin_Odom
5 months ago Place Videos & Guides
12Views
0likes
0Comments