IBM Cloud Docs
Configure the metadata service for bare metal servers

Configure the metadata service for bare metal servers

Configure the metadata service by obtaining a bare metal server identity access token from the metadata service. Optionally, generate an IAM access token from this token to access IAM-enabled services in the account.

Accessing the metadata service by using the bare metal server identity access token service

To access the bare metal server metadata service, you must first obtain a bare metal server identity access token (a JSON Web Token). You can later generate an IAM token from the bare metal server identity access token and then use it to access IAM-enabled services.

Windows users have extra requirements to set up the metadata service. For more information, see Setting up Windows servers for using the metadata service

Bare metal server identity access token concepts

A bare metal server identity access token provides a security credential for accessing the metadata service. It's a signed token with a set of claims based on information about the bare metal server and information that is passed in the token request. The minimum version date to use the bare metal server identity access token feature is 1 March 2022.

To access the bare metal server identity, make a PUT "https://api.metadata.cloud.ibm.com/i /identity/v1/token call by using the Metadata service API that invokes the bare metal server hostname. Communication between the bare metal server and metadata service never stops with the host. You acquire the token from within the bare metal server. If https secure protocol is not enabled on your bare metal server, you can use your bare metal server IP address instead of the hostname.

In the request, you specify an expiration time for the token. The default is 5 minutes, but you can specify that it expires sooner or later (5 seconds to 1 hour).

The response (a JSON payload) contains the bare metal server identity access token. Use this token to access the metadata service.

You can also generate an IAM token from this token and use the API to call IAM-enabled services. For more information, see Generate an IAM token from a bare metal server identity access token.

Acquiring a bare metal server identity access token

Using the Metadata service API, make PUT /identity/v1/token call to get a bare metal server identity access token from the token service. The following example uses jq to parse the JSON API response and then extract the bare metal server identity access token value. You can use your preferred JSON parser.

In the example, the return value of the CURL command is the bare metal server identity access token, which is extracted by jq and placed in the identity_token environment variable. You use specify this variable in a GET call to the metadata service to reach the metadata endpoint. For more information, see Acquire a bare metal server identity access token.

The example uses jq as a parser, a third-party tool licensed under the MIT license. jq might not come preinstalled on all VPC images available when you create a bare metal server. You might need to install jq before use or use any parser of your choice.

identity_token=`curl -X PUT "https://api.metadata.cloud.ibm.com/identity/v1/token?version=2025-06-30"\
  -H "Metadata-Flavor: ibm"\
  -d '{
        "expires_in": 3600
      }' | jq -r '(.access_token)'`

The following JSON response shows the bare metal server identity access token character string, date, and time that it was created, date, and time that it expires, and expiration time you set. Keep in mind that the token expires in 5 minutes.

{
  "access_token": "eyJhbGciOiJSUzI1NiIsImtpZCI6IlZTSS1DUl91cy1lYXN0X2I5...",
  "created_at": "2025-06-30T11:08:39.363Z",
  "expires_at": "2025-06-30T11:13:39.363Z",
  "expires_in": 3600
}

Generate an IAM token from a bare metal server identity access token

To access IBM Cloud IAM-enabled services in the account, you can generate an IAM token from the bare metal server identity access token by using trusted profile information. After you generate the IAM token, you can use it to access IAM-enabled services, such as IBM Cloud Object Storage, Cloud Database Service, and the VPC APIs. You can reuse the token multiple times.

Make a POST /identity/v1/iam_tokens call and specify the ID of the trusted profile. This request uses the bare metal server identity access token and a trusted profile that is linked to a bare metal server to generate an IAM access token. The trusted profile can be linked either when you create the bare metal server or provided in the request body.

The IAM API used to pass the bare metal server identity access token and generate an IAM token is being deprecated. Beta users must migrate to the metadata service API to generate an IAM token by using POST /identity/v1/iam_tokens.

Example request:

iam_token=`curl -X POST "$vpc_metadata_api_endpoint/identity/v1/iam_tokens?version=2025-06-30"\
   -H "Authorization: Bearer $identity_token"\
   -d '{
       "trusted_profile": {
          "id": "Profile-8dd84246-7df4-4667-94e4-8cede51d5ac5"
       }
      }' | jq -r '(.access_token)'`

The JSON response shows the IAM token.

{
  "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ0aGVfYmVzdCI6I8...",
  "created_at": "2025-06-30T14:10:15Z",
  "expires_at": "2025-06-30T15:10:15Z",
  "expires_in": 3600
}

For more information about trusted profiles, see Using a trusted profile to call IAM-enabled services.

Generating a bare metal server identity certificate by using a bare metal server identity access token

Bare metal server identity certificates are required to successfully enable and use encryption in transit between bare metal servers and IBM Cloud® File Storage for VPC shares. To generate a bare metal server identity certificate for the bare metal server, make a POST /identity/v1/certificates call with the bare metal server identity access token and a certificate signing request (CSR).

You can obtain the certificate signing requests (CSRs) from the open source command-line toolkit, OpenSSL.

  1. The following command generates a Certificate Signing Request (CSR) and RSA Key Pair by using openssl. When you run the command, replace the country code US with your two-digit country code in '/C=US'.

    openssl req -sha256 -newkey rsa:4096 -subj '/C=US' -out ./sslcert.csr -keyout file.key -nodes
    

    If you're using a different software to create the CSR, you might be prompted to enter information about your location such as country code (C), state (ST), locality (L), your organization name (O), and organization unit (OU). Any one of these naming attributes can be used. Any other naming attributes, such as common name, are rejected. CSRs with Common Name specified are rejected because when you make the request to the Metadata API, the system applies bare metal server ID values to the subject Common Name for the bare metal server identity certificates. CSRs with extensions are also rejected.

  2. Format the csr before you make an API call to the metadata service by using the following command.

    awk 'NF {sub(/\r/, ""); printf "%s\\n",$0;}' sslcert.csr
    

Then, you can make the API request to the Metadata service. See the following example. The csr value is required. The expires_in value is optional. The default value for expiration is 3600, which equals 1 hour.

curl -X POST "$vpc_metadata_api_endpoint /identity/v1/certificates?version=2025-06-30" \
 -H "Authorization: Bearer $identity_token" \
 -d '{ "csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIICnTCCAYUCAQAwWDELMAkGA1UEBhMCVVMxEjAQBgNVBAgMCU1pbm5lc290YTES\nMBAGA1UEBwwJUm9jaGVzdGVyMSEwHwYDVQQKDBhJbnRlcm5ldCBXaWRnaXRzIFB0\neSBMdGQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCYBvW12cKEkRUu\nyPScs7Xjwu/m+W8pZSQf9wrBa7DBVLFCdh440xOuSnIbsm+BNgYz4wL6/8la+N/K\nff06CdEwy9HLhPYc2z62tECxOBhI1G9gnsRUwb6WHNY71VulZs+37/9Mgd/eQy2n\nKHULNEU7sjNpLYoguKX8GRV3etKDp3tlFQmB6cNGOAgB3aQDmhdAh7K6oftesm0R\n8C7nmFA4SSjaI+855JxoxadlB2cCA5boaQ2gNO6YhYbtuTrMicQb0MTlZmacqzqP\nAxXWD3yFmAuUCpa2tBFBsavSW/kc52m4ldcO60U6hARvOxcXDqrbwu8r1ieY+tcZ\ncqjjBi99AgMBAAGgADANBgkqhkiG9w0BAQsFAAOCAQEAgAqWjtH3yAsX8QfTa9Pv\n3kktYFQKFsBzntmFDdIrOkeGayWRCuSG06f3sHWH0RuGkpq1x/4bedjcyyNVSna7\nxYX6kPOQX5iqf9pISD7A0XIkfS6XAos7gOh/jadjtxSwPCkuztSqIPKObH9OClAE\nU1fYDEtZCaZxsUdLwWJwOzbsivT97g1UVnbJAEzAJrqyaV4cUbv/w/slytHF+GAg\nNoUvPD8NGOQ+VzuI2oQuK515cyHO1SXrJyvkEVwRVVr3SoasqqWIQRrIv6zgzgik\nLN+uQxpzL1EeTB8qKy7xjymo2y1PbmaZzVNQNaBnxJfLE522pfW69evBRJ1qhrby\nTQ==\n-----END CERTIFICATE REQUEST-----\n"}'

A successful response returns the new certificate with information such as its ID, and creation and expiration times.

{
  "certificates": [
    "-----BEGIN CERTIFICATE-----\nMIIDmTCCAoECFDGlhn2VlwNEQymsNpyt9rOiiiWDMA0GCSqGSIb3DQEBCwUAMIGJ\nMQswCQYDVQQGEwJVUzESMBAGA1UECAwJTWlubmVzb3RhMRIwEAYDVQQHDAlSb2No\nZXN0ZXIxDDAKBgNVBAoMA0lCTTEeMBwGA1UECwwVVmlydHVhbCBQcml2YXRlIENs\nb3VkMSQwIgYDVQQDDBtWUEMgRXhhbXBsZSBJbnRlcm1lZGlhdGUgQ0EwHhcNMjIx\nMTAxMTM1MDE0WhcNMjIxMTAxMTQyMDE0WjCBhzELMAkGA1UEBhMCVVMxEjAQBgNV\nBAgMCU1pbm5lc290YTESMBAGA1UEBwwJUm9jaGVzdGVyMQwwCgYDVQQKDANJQk0x\nHjAcBgNVBAsMFVZpcnR1YWwgUHJpdmF0ZSBDbG91ZDEiMCAGA1UEAwwZRXhhbXBs\nZSBTaGFyZSBDZXJ0aWZpY2F0ZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC\nggEBAM6JytY3R4zWo3zzw/dM9ldUw8TIDQ9dNt+0sm3bFHHlAXaSKvmI+Ls/uQoh\n9VPpRLTx+WyljnKNnkXC6BQOzlugjAfi8hE2f5CC0A0m58XcBiZqH5BwTeLI4vVZ\nO9pLySckkEtHcmFE4h70KS5+1jDApeOTTS6EJsQcal/AAVYg7PDyXr1jE2HTKxnt\nlXopB/+bvWmBQ2k50Km0h0D1n0Ipoqqwb1wwWCrzQ2ds2XNKCUGkCgN6buFiF2nN\nLYS1tsIaw6OsTx+VheNGlYdlOhMUVypCok9JQ85P4NU47O6YgITX1V63ewZBnn5p\napywqdg8K2X2YgU/tLdpl5Jz2ysCAwEAATANBgkqhkiG9w0BAQsFAAOCAQEABuOX\npxGbBQPdG3VGkNCYScZUcxocqmx4mCegBFfv4PjWU2+eG+3JikB3YWwqD11hixQm\n5Qwge/zMXzuKPs5D4yyblpDJlq5Iz/0VMjEl2paCHg9nm5Z3QaSydFH3SCGwfvld\nRn9ib6DSw4a58hmqON+CiWUSSibQy46gUsqVvYhq2lJimejTAN2DlePY2su1xvNV\nAdmDjmvO7j7YV/eWk6r7OgcqtVaAovN3okaybwxf8sLAFxLzp/aUaqXL10qJ/ISz\nVL+UHN7t5WzjHdh2OjDXwz0BOyhdbjyNX8ptKd+E0O21PsFFe8ErfShDh00g/ERP\nzXuEUsCxzTyWRTm8GA==\n-----END CERTIFICATE-----\n",
    "-----BEGIN CERTIFICATE-----\nMIIEADCCAuigAwIBAgIUDzQruKqvBY7+CS6DL0u93Na6cLMwDQYJKoZIhvcNAQEL\nBQAwgYExCzAJBgNVBAYTAlVTMRIwEAYDVQQIDAlNaW5uZXNvdGExEjAQBgNVBAcM\nCVJvY2hlc3RlcjEMMAoGA1UECgwDSUJNMR4wHAYDVQQLDBVWaXJ0dWFsIFByaXZh\ndGUgQ2xvdWQxHDAaBgNVBAMME1ZQQyBFeGFtcGxlIFJvb3QgQ0EwHhcNMjIxMTAx\nMDM0OTI5WhcNMjcxMDMxMDM0OTI5WjCBiTELMAkGA1UEBhMCVVMxEjAQBgNVBAgM\nCU1pbm5lc290YTESMBAGA1UEBwwJUm9jaGVzdGVyMQwwCgYDVQQKDANJQk0xHjAc\nBgNVBAsMFVZpcnR1YWwgUHJpdmF0ZSBDbG91ZDEkMCIGA1UEAwwbVlBDIEV4YW1w\nbGUgSW50ZXJtZWRpYXRlIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC\nAQEAxjvxOtSFKsJKl4teBLgkX4+myxhClz2Qmg5MnNQ+oyhyNrpYvjG3+O+DrSUK\nKTXzmWSkKU/6BKmHQPNdpd4ymbb0cG7wmpcU3YjjrSNFgd/o3CEK9M7+ofIuQtTX\nXNUQWX5rb3wBqEA1TWazVTZpphhhcGQ8u03VTKvoF4S2DI6L3brDJJ0w1DM9Isaa\nB2mS64VYMIj3jLry39ryGEoYq1a0tC4C9fET3V5NmUnIRNqVDnGGkYBy/57VRACU\nXxXcQuW6eoPYGk6Ho3eKly34eilF2n9xD/bB41R4NzaxO/0lHq+caI5r1WlnTXtF\nE8wLpFoYMkuC0qiKBesyuyef2QIDAQABo2YwZDAdBgNVHQ4EFgQU2MIYc9g4Z7Kj\n79u2HPGYyTk5QHwwHwYDVR0jBBgwFoAUVnTLKJHyjHUcRp22jx+d3uGqnrwwEgYD\nVR0TAQH/BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwDQYJKoZIhvcNAQELBQAD\nggEBADhOBfnBEaWVWCsZo3UR7UlP5/8i3mRgyFt4YkICPMacy2IcnDw8aoyjTO5b\n4BLO4J1m4AmcJnDJcFIEKLBSNbzsiDdP2rWIAAJKO4gKxdTArIuLgq7zrR74j46L\nn6IFwumKQRw0diGYD6wWIo/f9kGy1NQ46igmRYrEfzA5HWitEpF0mu6lz8mZ8m9s\na6CTEqwLFhP+qOcWtpGjNTa+OHENAmmAR4mR4Os4MsBBnb4RA//S/4suW419Cz8N\n1/Ul7KduYRKpRMSiS9YWbCvC5WiEvOvfp8Z4ecXlC+ohU5MLuCRPfP+blBvxNx2O\nsLotlbzDpim/gYiJCHgW3POlsLE=\n-----END CERTIFICATE-----\n"
  ],
  "created_at": "2025-06-30T13:50:14Z",
  "expires_at": "2025-06-30T14:50:14Z",
  "expires_in": 3600,
  "id": "9fd84246-7df4-4667-94e4-8ecde51d5ac5"
}

For more information, see Encryption in transit - Securing mount connections between file share and host.

Creating a trusted profile for the bare metal server

Trusted profiles for compute resource identities help you assign an IBM Cloud® IAM identity to an IBM Cloud® resource, such as a bare metal server. You can call any IAM-enabled service from a bare metal server without having to manage and distribute IAM secrets to the bare metal server. You can create a trusted profile when you generate an IAM token from a bare metal server identity access token and link it to the bare metal server. For more information, see Using a trusted profile to call IAM-enabled services.

Enabling or disabling the bare metal server metadata service

The bare metal server metadata service is disabled by default. To retrieve metadata from a bare metal server, enable the service on new bare metal servers or existing bare metal servers by using the VPC UI, CLI, API, or Terraform.

Enabling bare metal server metadata in the console

From the IBM Cloud® console, you can enable or disable the bare metal server metadata service.

Enable the metadata service for an existing bare metal server in the console

Use the UI to enable the metadata service on an existing bare metal server.

  1. Go to the list of bare metal servers. In the IBM Cloud console, click the Navigation Menu icon menu icon > Infrastructure VPC icon > Compute > Bare metal servers.

  2. Click the name of a bare metal server to go to the details page.

  3. Go to Advanced configuration details.

  4. Under Metadata, click the toggle (appears green).

Enable the metadata service when you create a new bare metal server in the console

The following procedure shows how to enable the metadata service when you create a new bare metal server.

  1. In the IBM Cloud console, click the Navigation Menu icon menu icon > Infrastructure VPC icon > Compute > Bare metal servers.

  2. Click Create.

  3. Provision the bare metal server.

  4. Go to Advanced options.

  5. Under Metadata, click the toggle (appears green).

For more information about creating bare metal servers, see Creating Bare Metal Servers on VPC.

Disable the metadata service in the console

This procedure shows how to disable the metadata service for a bare metal server on which it is enabled. By default, the metadata service is disabled when you create a new bare metal server.

  1. In the IBM Cloud console, click the Navigation Menu icon menu icon > Infrastructure VPC icon > Compute > Bare metal servers.

  2. Click a bare metal server from the list to go to its details page.

  3. Go to Advanced configuration details. Under Metadata, the click the toggle to off (appears gray).

Enable or disable bare metal server metadata from the CLI

Use the CLI to enable the metadata service when you create a new bare metal server or on an existing bare metal server.

Before you begin:

  1. Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in. For more information, see the CLI prerequisites.

  2. Make sure that you created an IBM Cloud VPC.

Enable or disable the metadata service when you create a bare metal server by using the CLI

Run the ibmcloud bare-metal-server-create command and set the metadata-service property to true. The metadata service is disabled by default. In the response, you see Metadata service enabled set to true.

ibmcloud is bare-metal-server-create test-bare-metal-server-1 7002c1cd-9b0b-43ee-8112-5124dedbe84b us-south-1  bx2-2x8  0711-08206578-d749-49ea-86c9-1014622d1c6f --image-id 9f0050d0-636b-4fe6-82ea-931664fd9d91 --metadata-service true

Creating bare metal server test under account VPC1 as user myuser@mycompany.com...

ID                         264060c2-e5e9-44d4-994f-eea4a6688172
Name                       test-bare-metal-server-1
CRN                        crn:v1:public:is:us-south-1:a/a1234567::bare-metal-server:264060c2-e5e9-44d4-994f-eea4a6688172
Status                     pending
Startable                  true
Profile                    bx2-2x8
Architecture               amd64
vCPUs                      2
Memory(GiB)                8
Bandwidth(Mbps)            4000
Metadata service enabled   true
Image                      ID                                          Name
                           9f0050d0-636b-4fe6-82ea-931664fd9d91        ibm-ubuntu-20-04-minimal-amd64-1

VPC                        ID                                          Name
                           7002c1cd-9b0b-43ee-8112-5124dedbe84b        test-vpc1

Zone                       us-south-1
Resource group             ID                                  Name
                           21cabbd983d9c4beb82690daab08717e8   Default

Created                    2022-08-08T22:12:11+05:30
Boot volume                ID   Name           Attachment ID                               Attachment name
                           -    PROVISIONING   954c1c47-906d-423f-a8c8-dd3adfafd278        my-vol-attachment1

Enable or disable the metadata service for an existing bare metal server from the CLI

Run the ibmcloud is bare-metal-server-update command and specify the bare metal server ID. To enable the metadata service, set the metadata-service parameter to true; to disable, set it to false. An example command for enabling the service looks like this:

ibmcloud is bare-metal-server-update e219a883-41f2-4680-810e-ee63ade35f98 --metadata-service true

Enable or disable bare metal server metadata from the API

Enable or disable the metadata service when you create a new bare metal server by using the API

The metadata service is disabled by default when you create a new bare metal server by making a POST /bare_metal_servers call.

You can enable the service by specifying the metadata_service parameter and setting enabled to true.

This example shows enabling the metadata service at bare metal server creation:

curl -X POST "$vpc_api_endpoint/v1/bare_metal_servers?version=2025-06-30&generation=2"\
-H "Authorization: Bearer $iam_token"\
-d '{
      "image": {
         "id": "9aaf3bcb-dcd7-4de7-bb60-24e39ff9d366"
      },
      "keys": [
         {
           "id": "363f6d70-0000-0001-0000-00000013b96c"
         }
      ],
      "name": "my-bare-metal-server",
      "metadata_service": {
         "enabled": true
      },
      .
      .
      .
   }'

The response shows that the metadata parameter set to true when you enable the service. You can also verify the metadata service setting by making a GET /bare_metal_servers/{id} call.

Enable or disable the metadata service for an existing bare metal server from the API

To enable or disable the service from an existing bare-metal-server, make a PATCH /bare_metal_servers/{id} call and specify the metadata_service parameter. By default, the enabled property is set to false. To enable the service, set it to true.

This example call shows enabling the metadata service for a bare metal server:

curl -X PATCH "$vpc_api_endpoint/v1/bare_metal_servers/$id?version=2025-06-30&generation=2"\
    -H "Authorization: Bearer $iam_token"\
    -d '{
          "metadata_service": {
            "enabled": true
          }
      }'

The response shows that the metadata parameter set to true when you enable the service. You can also verify the metadata service setting by making a GET /bare_metal_servers/{id} call.

Configure metadata settings by using the UI

You can configure features of the metadata service by using the UI. When the metadata service is enabled, expand the metadata window to access the metadata service settings.

Select a trusted profile by using the UI

You can select an existing trusted profile for the bare metal server metadata service.

Select a trusted profile when you provision a bare metal server To select a trusted profile, go to the default trusted profile option, then select a trusted profile from a list of preexisting trusted profiles.

For more information, see Create a trusted profile for the bare metal server.

Enable secure access by using the UI

You can enable secure access to the bare metal server metadata service. When secure access is enabled, the metadata service is accessible only to the bare metal server by encrypted HTTP secure protocol (HTTPS). When secure access is disabled, the metadata service is accessible only to the bare metal server by unencrypted HTTP protocol. Secure access is disabled by default.

More properties might be required in the following scenarios:

Enable secure access when you provision a bare metal server

To enable secure access when you provision a bare metal server, go to the Secure access setting in the Metadata window when you Create a bare metal server from the Bare metal servers for VPC page. Toggle the secure access switch so that it displays Enabled.

Enable secure access on an existing bare metal server

To enable secure access on an existing bare metal server, go to the Secure access setting on the Bare metal server details page of your bare metal server.

Configure metadata settings by using the CLI

You can enable and disable features of the metadata service by using the CLI.

The following example shows a bare metal server with the metadata service enabled.

$ ibmcloud is bare-metal-server bare-metal-server-name -q

ID                                    0716_9cc6d74d-4b77-4cca-b1f4-31cc6edefe01
Name                                  bare-metal-server-name
CRN                                   crn:v1:bluemix:public:is:us-south-1:a/a1234567::bare-metal-server:0716_9cc6d74d-4b77-4cca-b1f4-31cc6edefe01
Status                                running
Availability policy on host failure   restart
Startable                             true
Profile                               bx2-2x8
Architecture                          amd64
vCPUs                                 2
Memory(GiB)                           8
Bandwidth(Mbps)                       4000
Volume bandwidth(Mbps)                1000
Network bandwidth(Mbps)               3000
Lifecycle Reasons                     Code   Message
                                      -      -

Lifecycle State                       stable
Metadata service                      Enabled   Protocol   Response hop limit
                                      false     http       1

Image                                 ID                                          Name
                                      r006-1025e040-7d6f-408c-b4db-6156dc986fc7   ibm-ubuntu-22-04-1-minimal-amd64-2

Numa Count                            1
VPC                                   ID                                          Name
                                      r006-ac1c1ae4-5573-42eb-9194-854c9a3d5555   fode

.
.
.

Select a trusted profile by using the CLI

You can select an existing trusted profile for the bare metal server metadata service.

For more information, see Create a trusted profile for the bare metal server.

You can link a bare metal server to more than one trusted profile, but the properties of a bare metal server support only one default trusted profile setting.

After a server is provisioned, you can't add or remove a default trusted profile or its autolink

Enable secure access by using the CLI

You can enable secure access to the bare metal server metadata service. When secure access is enabled, the metadata service is accessible only to the bare metal server by encrypted HTTP Secure protocol (HTTPS). When secure access is disabled, the metadata service is accessible only to the bare metal server by unencrypted HTTP protocol. Secure access is disabled by default.

Certain properties might be required in the following scenarios:

Enable secure access when you provision a bare metal server

To enable secure access when you provision a bare metal server, specify a value for the --metadata-service-protocol option when you use the bare-metal-server-create command. For secure access, specify https. The default setting is unencrypted http.

ibmcloud is bare-metal-server-create BARE_METAL_SERVER_NAME VPC ZONE_NAME PROFILE_NAME SUBNET ... [--metadata-service-protocol http | https] ...

--metadata-service-protocol value : The communication protocol to use for the metadata service
  endpoint. Applies only when the metadata service is enabled. One of: http, https. (default: "http")

To enable secure access on an existing bare metal server, specify a value for the protocol subproperty of the metadata service when you use the bare-metal-server-update command.

Configure metadata settings by using the API

You can enable and disable features of the metadata service by using the API.

Select a trusted profile by using the API

You can select an existing trusted profile for the bare metal server metadata service. Use the GET /bare_metal_servers/{id}/initialization call and include the "default_trusted_profile".

For more information, see Create a trusted profile for the bare metal server.

You can link a bare metal server to more than one trusted profile, but the properties of a bare metal server support only one default trusted profile setting.

After a server is provisioned, you can't add or remove a default trusted profile or its autolink

Enable secure access by using the API

You can enable secure access to the bare metal server metadata service. When secure access is enabled, the metadata service is accessible only to the bare metal server by encrypted HTTP Secure protocol (HTTPS). When secure access is disabled, the metadata service is accessible only to the bare metal server by unencrypted HTTP protocol. Secure access is disabled by default. Certain properties might be required in the following scenarios:

Enable secure access when you provision a bare metal server

To enable secure access, when you provision a bare metal server with the POST /bare_metal_servers method, specify a value for the metadata_service.protocol property for your bare metal server. For secure access, specify https. The default setting is unencrypted http.

Enable secure access on an existing bare metal server

To enable secure access on an existing bare metal server, use the PATCH /bare_metal_servers/{id} method to update the bare metal server. Specify a value for the metadata_service.protocol property for your bare metal server. For secure access, specify https. The default setting is unencrypted http.

Activity tracking events for bare metal server metadata

Activity tracking events are triggered when you get a bare metal server identity access token and then use the service. For more information about these events, see Metadata service events.

Next steps

After you create a bare metal server identity access token and enable the metadata service, you can retrieve metadata for the bare metal server, SSH keys, and placement groups. For more information, see Use the metadata service for bare metal servers.