Forum Widgets
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 }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.Tell a Story About Your First Data Center Migration.
They say you never forget your first data center migration - probably because it's like herding cats during a fire drill. I'm curious - what went sideways, what saved the day, and what would you never do again? Let's hear all the chaos, drama, or pizza-fueled heroics! 🍕🎖️Meet the Product Managers!
Hello Equinix Community, Today, we're opening a new chapter in our commitment to fostering transparency and community by introducing you to the incredible individuals behind our innovative products. The essence of Equinix has always been a blend of technology and community. We understand that the pulse of any tech-driven organization is its products, and behind those products, there's a team of dedicated, passionate individuals: our Product Managers. This thread offers a unique opportunity for our customers to get to know these dedicated professionals on a personal level. Our product team is thrilled to be a part of this platform, as it offers us a direct channel to engage, share, and grow with all of you. We see the Equinix Community not just as a space for interactions, but as a bridge to understand your needs, address your questions, and co-create the future. Here’s what to anticipate: Personal Introductions: Our Product Managers from various domains will be stepping forward to share about themselves, their roles, and the inspirations behind the products they steer. Behind-the-Scenes Stories: Insights into the ideation, challenges, and milestones of our product journeys – straight from those who live and breathe them. Open Dialogue: We're building a two-way street. Engage directly with our product teams, share your feedback, or ask anything you've ever wondered about our offerings. Sharing Expertise: Expect enlightening discussions, from technological deep dives to evolving market trends, all from the experts behind our product lineup. I invite our vibrant community to dive into these conversations, ask questions, and truly get to know the people who shape the products and services you trust.
Do not notify via email after scheduled report is generated
Hi, I'm using the reports v1 API to generate ONE_TIME reports and every time the report is finished, I get an email telling me as much. However, I want to prevent this email from going out every time. I've figured out that I can use the parameters array with name notifyEmails to add additional emails that should be notified but I can't seem to be able to remove the email tied to my account. Is there any way to achieve what I want?Meet the Equinix Team attending Mobile World Congress
Mobile World Congress 2025 is approaching - Are you attending? When it comes to the future of AI-ready, scalable digital infrastructure – the Equinix team of experts is here to help. Here’s a chance for you to meet the team in advance and connect in person in Barcelona! Let’s begin! Hi, I’m Efraim! Senior Principal Solutions Architect at Equinix. My dedication lies in bridging technology and bridging transformation, particularly in areas such as Cloud Computing, Artificial Intelligence, and Agility. You can find some of my recent Equinix blogs here. I'’ll be at MWC – let's connect and catch up on Cloud, AI, Programming, and my love of Cats.Is a Digital Services Agreement (DSA) required to order/use Fabric Cloud Router (FCR)?
Hey Community! We often get questions about Fabric Cloud Router and we’re here to help clarify for others who might have the same question in the future. If you’ve got additional questions about FCR, ask them in Community! What is a Digital Services Agreement (DSA)? The Digital Services Agreement is a document that is presented to users when setting up a Billing Account to order digital services like Fabric Cloud Router. If this is your first time ordering digital services with Equinix and you do not have an existing Billing Account (or sometimes called a Cloud Billing Account), you’ll be directed to digitally sign the DSA. If you're creating additional Billing Accounts, you will be asked whether you want to use an existing Digital Services Agreement or sign a new Digital Services Agreement. If you need guidance on either DSA option, please review this documentation. [Example only for reference and may not reflect latest version of DSA] I’m a new customer; do I need to sign a Fabric DSA? Yes, if you are a new customer and using Fabric for the first time, you’ll log into the Fabric Portal to order an FCR and be prompted to follow the click-through DSA. This is meant to allow and support our new customers who are looking to quickly onboard and use Fabric. What about if I'm an existing Equinix customer using Fabric for the first time, do I need to sign a DSA? Great question! If an existing Equinix customer clicks through Fabric for the first time they would also be prompted with the click-through DSA, however, if this customer already has an existing MCA/GTC Agreement with Equinix, these can be associated (by the Sales / Legal Ops) to a Billing Account for Fabric, and once that's correctly completed, the Billing Account should how as Active for the customer in the Portal and they will not be prompted to sign the click-through DSA. I already have a MCA/GTC agreement, but I’m getting prompted about a DSA. If an MCA/GTC agreement has been associated with the billing account for Fabric and the customer is still being prompted with the click-through DSA: The association of the MCA/GTC to the billing account may not be setup correctly and we recommend to contact support. The user logged into the Portal may not be associated with the correct Fabric Account/Project that has access to the active billing account.
