Developer & APIs

Essentially what the title says. I'm attempting to programmatically get the list of colocation users and their roles/permissions. It doesn't appear there's an easy way to do this with the existing API. That said, when I view my users in the portal ordinarily, I see GET /api/ecp/users/getUsersSo it's definitely there, I'm assuming it's just not available to normal users, only to Equinix internally. Any chance someone here has an idea?

I have been trying to get the locations, but getting the error code 500.  What is permission code?

Hi,we have a presence in different Equinix data centers and retrieve billing information via the Billing v2 API. We observed that the information we obtain for the Japan invoice (and that one only) has inconsistent (dare I say wrong?) tax amount values across time:For invoices from 2024-02 (oldest I have) until 2024-05 (which is not downloadable anymore due to the 12 month limit but I have a local copy) the Japanese line items behave exactly like all others we can observe, namely: non-zero taxAmount (10% of recurringAmount) and recurringAmount + taxAmount = totalAmount.For invoices from 2024-06 until 2024-08 (both in the snapshot I had from a few months ago and the one I just took now) the Japanese line items now still has a non-zero taxAmount (10% of recurringAmount) but totalAmount = recurringAmount. Checking a few entries we saw that the netAmount is the same as in previous entries which makes me assume that the totalAmount does not include any tax amount.For invoices from 2024-09 o

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?

Those already using Ansible can now take advantage of templates to demonstrate configuring Layer 2 connectivity to AWS S3. You can also follow the prerequisites in the related GitHub repo to test this as a new user.Step 1: Use the initial template to rapidly create a project, VLAN, VRF, and prep for BGP peering on the virtual circuit.Step 2: Finish setting up the interconnection in Fabric console manually and accept the Direct Connect request in AWS.Step 3: Use the final playbook which takes care of deploying the VPC, the S3 VPC endpoint, the Virtual Private Gateway attached to your Direct Connect, and finally configures the end to end BGP peering.This playbook has been added to the examples section of the Ansible Collection Equinix page.

Check out the latest October 2024 Equinix API Update. For details on new or updated APIs, we recommend looking at the Release Notes, organized by product in the Developer Portal API Documentation.

Those looking to explore Nutanix on Equinix Metal are likely to have two concerns in mind: ease of migration and security.Thankfully, two examples have recently been added to the Equinix Terraform directory that demonstrate exactly how a user can accomplish these two things.Nutanix Clusters Setup and Protection Policy - walks a user through creating two Nutanix Clusters on Equinix Metal rapidly, create a protection policy between them, and then practice creating a VM in one cluster and migrating it to the other cluster. Nutanix on Equinix Metal with Active Directory Authentication - helps a user create a cluster on Equinix, add an AD server VM, configure AD authentication, and map a few sample roles to the AD. Both examples use a combination of Terraform and manual Prism console steps, promoting understanding while deploying with speed and convenience.  Consider walking through these examples if you're interested in exploring Nutanix on Equinix Metal or learning more about ma

What can you learn in 60 seconds? A lot, actually! We're now creating Youtube Shorts to teach you in bite-size snippets.Let me and @stevemar know which topics you'd like us to cover!Here I talk about IPConfig and IFConfig, which dives into your computer's network - like VPNs, ethernet ports, and more! 

Hey everyone! We’re thrilled to be hosting our second Demo Day of 2024, this time all about Infracode! If you’re already an infrastructure expert slinging Terraform or just starting out, we’ve got experts from across the industry to share their experiences with you!We’ll have folks like Marino Wijay of Kong talking about Platform best practices for AI, Jared Watts talking about Crossplane, and Engin Diri to talk to us about Pulumi. We’ve even got two of our Equinix DevRel Engineers, Chris Privitere and Oscar Cobles to talk about Kubernetes Cluster API and using Terraform to interconnect Equinix Metal and your AWS cloud.See our Event Page for more information and/or join us live at the link below so you can post your questions for our speakers directly in the chat!Can’t wait to see you in the chat!P.S. -- if you can’t make it, or you’re getting this late, don’t panic! Our full session will be embedded below 

Check out the latest August 2024 Equinix API Update. For details on new or updated APIs, we recommend looking at the Release Notes, organized by product in the Developer Portal API Documentation.

In this video, we explore Terraform as the industry standard for provisioning on Equinix Metal. We’ll discuss the advantages of a declarative approach using HashiCorp Configuration Language (HCL), which enables reproducible and repeatable server environments. Join us for a demonstration of setting up Equinix Metal, including authentication and creating projects and devices with user data for automated configurations. Thank you for watching, and don’t miss the other videos in this series! 

Hello,I'd like to configure a redundant connection to Azure using dot1q encapsulation.The documentation for migration from v3 to v4 states that we need to include  "linkProtocol": { "type": "QINQ", "vlanSTag": 2002 }, in the zSide definition. That was not necessary in the v3 API.I'm not sure what the technical background for that value is.Specifically: Can we always use the same VLAN ID in connections to different Azure environments when using unique VLAN IDs on the aSide?Any help is appreciated.

I have created a Claim that includes a Device, Port, PortVlanAttachment and a Vlan. In order to create the Port I have to pass the Device Eth1 port UUID to the 'spec.forProvider.portId' of the Port Kind. This works and picks up the vlan info, but upon deleting the claim, the port is not deleted automatically as expected. The following event messages can be seen: Conflicting configuration arguments: "vlan_ids": conflicts with vxlan_ids Warning CannotObserveExternalResource 8s (x10 over 6m27s) managed/metal.equinix.jet.crossplane.io/v1alpha1, kind=port cannot run refresh: refresh failed: Conflicting configuration arguments: "vlan_ids": conflicts with vxlan_ids Conflicting configuration arguments: "vxlan_ids": conflicts with vlan_ids The spec of the object looks like this:  Spec: Deletion Policy: Delete For Provider: Bonded: false Port Id: b561e487-fbb0-4a2c-98e7-22da331ed316 Vlan Ids: 73f648b5-9b6b-4076-a6ab-673aa45c7152 Vxlan Ids:

When editing an existing Metal Vlan resource's spec to add a description, the string is applied to the managed resource but is not updated in the UI. If the description is included in the original Vlan resource spec during creation, the UI shows the description. apiVersion: metal.equinix.jet.crossplane.io/v1alpha1 kind: Vlan metadata: name: myvlan1 spec: forProvider: description: | Dummy native VLAN for purposes of enabling tagging on the trunk port. projectId: <uuid> metro: svIf the spec.forProvider.description is left out during the creation, then editing the resource and applying the change will not cause the description to show up in the UI. I'm not sure if this is expected or not. 

We have recently launched a   for accessing your developer settings such as App Management and EMG subscriptions. With the improved UI, you can: Access your developer settings via Equinix portal and discover our product and services using a single unified login. Easily and efficiently manage your Equinix apps and subscriptions (including the ability to search, filter and sort) When logging in, you will be redirected to Equinix Customer Portal where you can sign in using your email login credentials. To access the app dashboard or EMG subscription, use the left navigation and select Developer Settings. There is no impact to existing apps and subscriptions and your integration will continue to work.    

After I spin up a Metal Device using the Crossplane Equinix provider, it comes up but in the events I see the following. I'm not sure if it is expected or a bug?Managed resource event message:Events:Type Reason Age From Message---- ------ ---- ---- -------Normal CreatedExternalResource 3m7s managed/metal.equinix.jet.crossplane.io/v1alpha1, kind=device Successfully requested creation of external resourceWarning CannotObserveExternalResource 13s (x6 over 30s) managed/metal.equinix.jet.crossplane.io/v1alpha1, kind=device cannot run plan: plan failed: Instance cannot be destroyed: Resource equinix_metal_device.my-gateway-sv-4x2x4-4gfpq has lifecycle.prevent_destroy set, but the plan calls for this resource to be destroyed. To avoid this error and continue with the plan, either disable lifecycle.prevent_destroy or reduce the scope of the plan using the -target flag.Field in XRD for plan is: "plan: m3.small.x86"Environment:Crossplane v1.16Equinix Provider: v0.6.1K8s: Kind 1.27

I’m having some trouble using the Equinix providers within a Claim and I’m not sure where the problem lies. The issue is that I am trying to take the ID uuid from the Device status.atProvider.id and update a status.id field in my xrd claim, but the status never seems to get updated. This works fine with the AWS provider as an example.In my example I want to grab the UUID of the device and populate the Claim XRD's status.id field, but I do not see this population happening. I use the same technique with the upbound AWS provider so I know it is valid.Within the composition.yaml: - type: ToCompositeFieldPath  fromFieldPath: status.atProvider.id  toFieldPath: status.id Has anyone else gotten this to work?

In this video, David Flanagan a.k.a. Rawkode, does a deepdive on the Equinix Terraform CDK. David will discuss the advantages of using Terraform CDK for your Equinix provisioning, emphasizing the benefits of a declarative approach to code. This method allows for reusable snippets across teams, reducing redundant work. We'll demonstrate how to create a function to find the cheapest server configuration and show how this refactored code can be published and shared via various platforms like NPM and PyPy. Thank you for joining this walkthrough on provisioning Equinix Metal devices with Terraform CDK. Be sure to check out the other demo videos in this series. See you next time!   

In this video, David Flanagan, a.k.a. Rawkode, does a deep dive on the Equinix GO SDK. David explores how to leverage webhooks and APIs with the Equinix SDK to build pipelines for remediation, automation, and notifications. We'll demonstrate how to send GET requests, showing the requests made and their results. This approach allows for dynamic capacity checks based on environment variables, integrated seamlessly with your infrastructure. This was a brief yet insightful introduction to the Equinix SDK. Go ahead, experiment with the Equinix SDK, and share your creations with us. Until next time, have a great day!  

when I am trying below command from my servercurl -v https://api.equinix.comits giving below errorerror:0A000438:SSL routines::tlsv1 alert internal errorIt was working fine earlier. I am using below APIs for validating Azure Keyhttps://api.equinix.com/fabric/v4/connections/validateBut now even authentication API is also not working

Check out the latest June 2024 Equinix API Update. For details on new or updated APIs, we recommend looking at the Release Notes, organized by product in the Developer Portal API Documentation.

Come join Equinix's Chris Privitere!Nutanix Terraform Cluster Provisioning simplifies the process of setting up cloud environments. By using a few lines of code, you can efficiently configure and deploy clusters. This method ensures a streamlined and consistent setup, reducing manual errors. It's a reliable solution for managing complex IT infrastructures. LINKSNutanix WorkshopCreate an AccountDeploy Labs

When running Terraform to provision and manage Equinix Fabric, Metal, and Network Edge, you may want to run Terraform from a restricted environment. Network filtering ACLs will need a predictable set of IP ranges to permit. This discussion will help you discover the IP services, ports, and address ranges your Terraform runner environment will need access to. We'll also discuss alternative ways to run Terraform configuration. If your ACLs permit the Terraform runner environment outbound HTTPS (TCP 443) and responses, that would cover everything Terraform needs to start provisioning infrastructure on Equinix. We'll assume we don't have unrestricted access and dig in a little further. Upon running, `terraform init`, Terraform will attempt to use DNS (UDP/TCP 53) services and HTTPS services to download provider plugins, such as the Equinix Terraform provider.  The default host for fetching these plugins is registry.terraform.io, managed by Hashicorp. This is the defacto hub for public

Check out the latest May 2024 Equinix API Update. For details on new or updated APIs, we recommend looking at the Release Notes, organized by product in the Developer Portal API Documentation.

In this video, Steve Martinelli from Equinix interviews Phil Estes, a Principal Engineer at AWS. They discuss Phil’s background in software development and his involvement in open-source projects, particularly in the container runtime world. Phil talks about his work on Docker, Containerd, and a new project called Finch, which provides a wrapper for container runtime tools. They also discuss the adoption of Containerd and the reasons why many managed Kubernetes services switched from Docker to Containerd. Phil shares his favorite open-source moments and mentions upcoming speaking engagements. He encourages people to try out Finch and provides information on where to learn more about the project.