AmdMetal · From order to access
Four steps: configure, pay, receive delivery, and log in
Orders, machines, and access details are linked in the console. Delivery emails provide notifications; login credentials are available in the machine details.
Configuration and payment create the order; delivery notifications and credential retrieval are handled separately. Once an AmdMetal server is delivered, connect over SSH or RDP. Delivery is not promised within a fixed timeframe.
Select the 128GB or 256GB memory configuration, then choose additional drives, bandwidth, extra IPv4 addresses, an operating system, and a billing period. Before submitting, check each selection and the amount due for the current term. Availability is confirmed in real time by the console.
Have ready: memory requirements, disk plan, number of IP addresses, and operating system needs.
Before confirming payment, select one of the methods listed on the configuration page. All charges are in USD. The amount due is the monthly total multiplied by the number of months in the selected billing period, paid upfront for the full term.
Check the configuration, billing period, and final amount due. A redirect alone does not confirm payment.
The delivery email includes the order number, machine ID, and console link to identify the order and server being delivered. Passwords are not sent in plain text by email; connection credentials are available in the console.
Keep the order number and machine ID for future reference and support requests.
Sign in to the console with the account associated with the order, then find the connection address and login credentials in the relevant machine details. If the account has multiple servers, match the machine ID to the delivery email before checking the details.
Retrieve the connection address and actual login credentials; do not assume a default username or port.
Use SSH for Linux, FreeBSD, and Proxmox VE; use RDP for Windows Server. For servers with multiple IPv4 addresses, connect using the first address. The remaining addresses are for allocation to services within the operating system.
Check that the selected operating system, connection address, and client are compatible.
Both server configurations use an AMD EPYC 7543P with 32 cores and 64 threads; the difference is memory capacity. The data center is in Tokyo, Japan. Review the server's resources and how they will be allocated to workloads, rather than choosing a location.
Both the 128GB and 256GB configurations use DDR4-3200 ECC memory. The memory configuration cannot be upgraded on the same server after provisioning. To switch configurations later, a separate server must be ordered, and workload migration and data transfer must be handled independently.
Budget for database caches, virtual machine memory, and operating system overhead—not just current application usage.
Each server includes 2×1TB NVMe drives, each directly attached, with no hardware RAID. Add 0–2 2TB NVMe drives if needed. These are also independently attached and do not form a hardware array automatically.
Plan the layout for the operating system, workload data, software RAID, or a ZFS mirror in advance. If redundancy is required, account for the effect of mirroring on usable capacity.
Each server includes 1 dedicated IPv4 address, with up to 255 additional addresses, for a total of 256. Choose the number of addresses and operating system during configuration. Additional addresses do not replace the first management connection address.
Choose from 14 free operating systems or Windows Server, billed monthly. Windows is available in English, Traditional Chinese, or Simplified Chinese; confirm the required language before submitting the order.
AmdMetal itemizes the server, additional drives, bandwidth, extra IPv4 addresses, and Windows licensing in the monthly total. Free operating systems have no licensing charge. Before paying, check the itemized configuration and amount due for the current term.
Monthly billing is 1 month, quarterly billing is 3 months, half-year billing is 6 months, and annual billing is 12 months. All four billing periods have no discounts, setup fees, or contracts.
Payment methods are those listed on the configuration page before payment is confirmed. Changing the billing period changes the one-time amount due for the current term; it does not change the server specifications or monthly line items.
If a payment needs to be checked, keep the order number and describe the issue in a console support ticket. Do not treat an opened payment page, a return from the payment client, or an email notification on its own as confirmation of payment.
Notifications and sensitive connection details are provided separately. The AmdMetal delivery email identifies the server being delivered. Before connecting, open the console and retrieve the connection details for that machine.
| Information | Where to find it | Purpose |
|---|---|---|
| Order number | Delivery email | Identifies the rental record and the relevant order for billing or delivery queries. |
| Machine ID | Delivery email | Identifies a specific server; check each machine by its ID when there are multiple servers. |
| Console link | Delivery email | Opens the account to view delivered servers and their details. |
| Connection address and login credentials | Machine details in the console | Used to connect over SSH or RDP. Passwords are not sent in plain text by delivery email. |
If delivery information is unclear, sign in to the console and check the order and machine details. Do not include login passwords, private keys, or complete workload data in a support ticket.
A successful remote connection means access is ready, not that the workload has been deployed. AmdMetal is responsible for hardware and networking; customers are responsible for operating system configuration, workload data, and backups. Complete these preparations before moving production workloads onto the server.
Confirm that the installed operating system matches the order, then install software updates and security patches using the appropriate method. For SSH, key-based authentication is recommended. Verify that the new login method works before changing existing authentication settings.
Open the service ports required by the workload, and keep the current management connection available while changing rules. On servers with multiple addresses, use the first IPv4 address for SSH or RDP and bind the others within the operating system according to the network plan.
The two NVMe drives are not preconfigured as RAID-1. For local redundancy, configure software RAID or a ZFS mirror independently. Confirm the target drives and data locations before setup to avoid overwriting existing data.
A disk mirror is not a substitute for an independent backup. Keep off-site copies of workload data, databases, and important configuration files, and verify the recovery process. Before migration or reinstallation, confirm separately that all required data has been exported.
Delivery and data expiry rules for NVIDIA DGX Spark are covered separately. See AmdMetal DGX Spark specifications and rental details.
AmdMetal renewals follow the original billing period, with the amount due still calculated as the monthly total multiplied by the number of months in the term. Memory cannot be upgraded on the existing server. Order the required configuration separately and plan the migration, validation, and switchover for the existing workload.
For reboot, reinstallation, connection, or billing issues, sign in to the console and submit a support ticket. Include the order number, machine ID, the action that led to the issue, and a screenshot of any error to help identify the affected server. Before reinstallation or disk operations, confirm that backups are in place.
For a first order, check the resources and billing period. Delivery and access details for existing orders are available in the AmdMetal console.