Latitude.sh Terraform Provider: Shipped version 0.2.1 with support for deploying servers with SSH and user data and fixed an issue that prevented project settings from being updated.
Updated API URL: The default API URL is now api.latitude.sh. The old URL will continue working indefinitely.
Go client library: Released version 0.1.3.
Dashboard: Improved several aspects of the dashboard to provide better interactions with dropdowns, selects, and more.
API: Added the ipmi_status to GET /servers responses to retrieve the health status of a server's IPMI connection.
User permissions: Collaborators can now update the deploy config of a server.
Bandwidth alerts: Improved notifications for bandwidth alerts to avoid sending too many emails.
Create views and filters for your servers and IP addresses right inside the dashboard.
By creating a filtered view a new tab is added to your server or IP resource list. All of your team members get immediate access so you can easily share just the most relevant data with them.
Misconfiguration and bad installs can cause you to get locked out of your server.
Today we are releasing Rescue Mode as an additional way to troubleshoot your servers and regain access to your system.
When you put a server in rescue mode, we load a lightweight Ubuntu image into your server's memory. This allows you to SSH to the machine to fix issues, recover and transfer files, or simply change access credentials.
Rescue is available for all servers in all locations.
It is now easier to be on top of your monthly bandwidth consumption.
Enable Bandwidth Alerts with one click to get an email whenever the bandwidth quota for a region goes over 80%.
We’re happy to add Bogota, Colombia, as Latitude.sh's fifth location in LATAM, making us the region's most extensive Bare Metal cloud provider.
Latitude.sh now offers 15 Core locations you can deploy to instantly.
We are excited to announce that you can now deploy and version your Latitude.sh infrastructure with Terraform.
If you are an experienced Terraform user or just getting started, we've put together a guide that can get you up and running with Latitude.sh's provider in no time.
Thanks to the Capture Alpha team for their valuable contribution to this project. 🤝
The state of Virginia is known for being the number one region for data centers in the US, with a high concentration of major public clouds. Today, we're excited to introduce Ashburn as our eighth location in the United States.
With the launch of our Ashburn location, you are now 1 ms away from clouds like AWS and Azure.
While egress bandwidth fees are a very profitable source of revenue for public cloud providers, it ultimately hurts everyone.
They not only increase the complexity of running digital infrastructure by having CloudOps teams go out of their way to save costs but are slowing down the migration to the cloud by breaking the promise of cost reduction.
It is no surprise that we have always strived to make bandwidth management simpler and cheaper for our customers. Every Latitude.sh server comes with 20 TB of free egress bandwidth, we automatically pool bandwidth for your servers and offer bandwidth packages at rates as low as $0.00064 per GB.
Even with all of these benefits, you could go over your quota at some point.
To reduce operational complexity and surprise charges, and because our network has grown to a point where we can pass these savings on to our customers, we are reducing overage egress fees by 80%. Each GB over your quota will now cost just $0.01, down from $0.05.
Buenos Aires, Argentina, is our most requested location and has been running for a few months as a Custom region for Custom Deployments. Today, we're excited to extend server availability in Buenos Aires to all customers.
We're starting with the c2.small.x86 instance, with more instances coming later this year.
Invoices page: Improvements to detailed invoices make it easier to determine how much each resource costs.
Server create date: The server page shows when you deployed the server.
Credentials: We've improved how credentials are shown in the dashboard, and now show which SSH keys the server was deployed with. There's also a one-liner you can quickly copy to log in to your server.
Hostname edit: You can now edit the hostname of a server from the server details page and through the API.
User data templates give you a quick start when creating your scripts. We‘ve added templates for common use cases, like updating packages and sending Slack notifications to check in a new or reinstalled device with your team.
Get started by going to Project Settings → User data → Create from template
Check out the documentation as well.
Teams can now use their identity provider to log into Latitude.sh with SAML Single Sign-On. All major identity providers are supported, including Okta, Active Directory, OneLogin, and Auth0, and can be configured by going to the Settings section of the Settings & Billing page.
There's an optional Directory Sync feature, allowing teams to automatically sync users form a directory provider, adding and removing users automatically based on changes happening in your IAM.
User data are small scripts that run on a server's first boot, letting you quickly customize a new server the first time it boots after its deployment.
With user data, you can easily change the root password, notify of a new deployment on Slack, install packages, and more with just a few lines of code.
Check out the documentation as well.
We are continuing to ship features and improvements based on your feedback. Here are some recent changes.
Batch deploys: Create multiple servers in one go through the server create page. Check out the docs.
Private Networks beta: Go to the Layer 2 page in the dashboard to sign up for early access to one of our most requested features.
Filters: More filters have been added to the servers page, and you can now filter by region, hostname, and label, using operators like contains, is equal to, has prefix, and has suffix. Additionally, filters are now persisted in the URL, making sharing a specific view with your team easier.