Using Fortanix Confidential Computing Manager to Build an Enclave OS Nginx Application


This guide will walk you through creating an Enclave OS Nginx application that will use the HTTPS protocol for communication. The application will use a certificate issued by the Fortanix Confidential Computing Manager (CCM) to establish the HTTPS protocol and the application will be deployed on a Virtual Machine in Azure.


  • A Fortanix CCM account.
  • A Microsoft Azure account.
  • Deploy Fortanix Node Agent from the Azure marketplace as described in Step 6 of the Quickstart Guide – Fortanix.

  • On the virtual machine, install docker using the following command:
    sudo apt install

Using CLI

Authenticate with Fortanix CCM

Before you can issue any requests, you first need to authenticate to Fortanix CCM using the following commands:

Session tokens are short-lived and you will occasionally have to issue a refresh API request whenever you get {"message": "Forbidden", "code": "FORBIDDEN"}.
curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -X POST
cpath=$(mktemp -p "/tmp" -t "fortanix_ccm_cookie.XXXXX")
For security reasons, it is best not to type in your credentials in the terminal windows. Instead, create a file to hold the credentials and pass the file to curl as shown below.
machine login <username> password <password>

where <username> and <password> need to be replaced with the email address and password of your Fortanix CCM account.
curl --netrc-file access-file -c $cpath -X POST

Get all Accounts

Use the GET command shown below to get all the accounts and select the account using the account_id.

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -X GET

Select the Account

if you have multiple accounts with CCM you may see a large response for the previous request. Each account starts with the name of the account, followed by the acct_id, as shown below. Make sure to select the acct_id, which belongs to the account you want to deploy your application with. {"name":"fortanix-test","acct_id":"e5fd5441-4ffc-4a4c-af63-bddb488524c2","created_at":1609863607000,"roles":["MANAGER"],"status":"ACTIVE","features":["workflows"],"approval_state":"APPROVED"}
curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -X POST<acct_id>

Create an Application

To create an Nginx application, you must first create a docker image with SSL enabled and deploy it to a public registry.

Nginx Configuration File to Enable SSL to Listen on Port 443

Create a default.conf file which is used by Nginx as shown below:

server {
listen 443;
ssl on;
ssl_certificate /etc/ssl/nginx.crt;
ssl_certificate_key /etc/ssl/nginx.key;
server_name localhost;
server_tokens off;

location / {
root /usr/share/nginx/html;
index index.html index.htm;
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
#redirect server error pages to the static page /50x.html

Dockerfile for Creating an Nginx Docker Container

The docker file fetches the latest Nginx container from and updates the container with the new configuration created above.

FROM nginx:latest

COPY default.conf /etc/nginx/conf.d/

Build the docker on your local system and push it to your desired registry.

docker build -t <repository-prefix>/nginx-ssl-nocert:latest .

docker push <repository-prefix>/nginx-ssl-nocert
Replace <repository-prefix> with your public or private repository prefix

Create the app.json file

Create the app.json config file that contains the application details.

"description":"nginx web server app with SSL enabled.",
"rw_dirs": ["/var/cache/nginx", "/etc/ssl"],
Replace <registry-prefix> with the location of your registry used previously where the Nginx container was pushed.

The certificate and private key will be generated by Fortanix CCM at the time of deployment and Enclave OS will place them in the default path of Nginx when the container runs in Azure.

As part of the config, you must specify the domain URL for whitelisting by Fortanix CCM so that the Enclave OS can be accessed. The same domain URL is assigned to the certificate so that the public certificate can be generated against this domain. As an example, in this case, we created a domain, but this can be any URL of your choice. DNS record will need to be set up in your infrastructure to route to the VM for this domain.

Create Application

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -H "Content-Type: application/json" -d @app.json -X POST

Note the app_id value returned as part of the above command. It will be used later.

As an example: "app_id":"de40482c-2092-4a25-b9a2-635eb55c5d97"

Fetch the Domain Whitelisting Tasks

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -X GET > all_domain_tasks.json

All the tasks fetched will be stored in all_domain_tasks.json file. Select the task_id to approve the task in the next step.

Approve a Task

Among the tasks fetched in the previous step, approve the application-specific task using the task_id.

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -s -H "Content-Type: application/json" -d '{"status":"APPROVED"}' -X PATCH<task_id>

Create an Image

Creating an image of the application requires two steps:

  1. Create a build.json file with the registry credentials for the docker container created previously (only needed if it is a private registry) and the registry credentials for the docker container where CCM can push the Enclave OS container
  2. Issuing a CCM command to convert the Nginx container to an Enclave OS container

Create a build.json file

Create a build.json file with the following content.

"app_id": "${app_id}",
"username": "<account-id>",
"password": "<password>"
"input_docker_version": "latest",
"username": "<account-id>",
"password": "<password>"
"output_docker_version": "sgx"

Replace <account-id> and <password> with the credentials for the registries which will be used for input and output.

Replace the <app_id> as per below.

First, get the list of all apps and identify the app_id for the app created in the above steps (this is only needed if you did not note the app_id previously)

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -X GET

Convert the Image

Convert the image using the command below (which uses the build.json created above)

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -s -H "Content-Type: application/json" -d @build.json -X POST

Now check that your docker registry contains the converted container.

After the image has been converted by Fortanix CCM and before it can be run in attested mode, it will require approval. This is to ensure that only approved images can run on the enrolled compute nodes with Fortanix CCM. The following section describes how to approve the image.

Fetch all the Image Whitelist Tasks

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -X GET

All the image whitelist tasks will be stored in all_build_tasks.json file. Select the image whitelist task ID to approve the image in the next step.

Approve the Image Whitelist Task

curl -b $cpath -c $cpath -H "X-CSRF-Header:true" -s -H "Content-Type: application/json" -d '{"status":"APPROVED"}' -X PATCH<task_id>

The image is created and whitelisted.

Next, run the following command on a machine running the node agent to run the Nginx Enclave OS application.

Run the Application

To run the application, you must first log in to the machine on which the Node Agent was deployed.

For the node attestation type Enhanced Privacy ID (EPID)/Data Center Attestation Primitives (DCAP), use the command:

docker run --device /dev/sgx:/dev/sgx -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket -e NODE_AGENT_BASE_URL=http://<node-agent-ip>:9092/v1/ -p <port-mapping> <converted-image-id>

In this example use the following <port-mapping> and converted-image-id.

docker run --device /dev/sgx:/dev/sgx -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket -e NODE_AGENT_BASE_URL=http://<node-agent-ip>:9092/v1/ -p 8121:443 <registry-prefix>/nginx-ssl-fortanix-cert-eos:sgx
  • <node-agent-ip> is the IP address of the compute node enrolled with Fortanix Confidential Computing Manager (CCM).
  • 9092 is the port on which Node Agent and Enclave OS communicate

Test Nginx (Enclave OS) App

There are two ways to verify that the Enclave OS application is successfully running and using the Fortanix CCM-issued certificate.

  1. Log into the compute node where the Node Agent and the Nginx applications are deployed. Run the following command to view the Nginx response and associated certificate.
    curl --verbose -k
    It is possible to use localhost as shown below, but this will show a certificate error since the certificate was created for a specific domain.
    curl -verbose -k https://localhost:8121
    The response will include the CCM-issued certificate information as well as the Nginx HTML page (same tests shown in the image below). Also, ensure that it’s a 200 OK response.
  2. Go to a browser and open the following URL: Nginx_App13.png
    Figure 1: Test Nginx
    The browser will show a certificate warning as the root CA is unrecognized by the browser. Proceed to advance and continue to the site.

Using Fortanix Confidential Computing Manager UI

Log in to Fortanix CCM

Get all Accounts

To get the accounts using Fortanix CCM UI, log in to Fortanix CCM to see the available accounts.


Figure 3: Get the accounts

Select the Account

To select an account using Fortanix CCM UI, click the SELECT ACCOUNT button, and then click the GO TO ACCOUNT button to enter the account.


Figure 4: Select accounts

Create an Application

Create an Nginx application using the configuration provided in the app.json file above.

To create an application using Fortanix CCM UI, navigate to the Applications tab and click + APPLICATION to add an application.


Figure 5: Create an application

To create an application using Fortanix CCM UI, go to the Add application form and add the details of the application.

Figure 6: Create an application

Next section allows a user to add labels. For this example, no labels were added.

For the certificate section add the following:

Figure 7: Configure certificates

For the advanced sections make sure to add the Nginx directories which need to be set up as read/write.

Figure 8: Advanced settings

Click Next at the bottom of the page to create the application.

Create an Image

Once you create the "nginx-fortanix-cert-eos" application, click NEXT, you will see the Add image page where you have to configure the tags for the input/output image and credentials for the registry where the container will be fetched from and the converted container pushed to.

Figure 9: Create an image of an application

In the Create image form and add the details of the image.

Figure 8: Create an image of an application

Once the credentials and the tags have been set up, Click CREATE at the bottom of the page.

View the Image Whitelist Tasks

To view the image whitelisting tasks using Fortanix CCM UI, click the Tasks tab.

Figure 9: View and approve image whitelisting task

Approve the Image Whitelist Task

To approve the image whitelisting task for the "nginx-ssl-fortanix-cert-eos" application using Fortanix CCM UI, click the APPROVE button in Figure 9 above.

Next, run the following command on a machine running the node agent to run the application.

Run the Application

For the node attestation type Enhanced Privacy ID (EPID)/Data Center Attestation Primitives (DCAP), use the command:

docker run --device /dev/sgx:/dev/sgx -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket -e NODE_AGENT_BASE_URL=http://<node-agent-ip>:9092/v1/ -p <port-mapping> <registry-prefix>/<converted-image-id>

In our case, we will use the following <port-mapping> and <converted-image-id>.

docker run --device /dev/sgx:/dev/sgx -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket -e NODE_AGENT_BASE_URL=http://<node-agent-ip>:9092/v1/ -p 8121:443 <registry-prefix>/nginx-ssl-fortanix-cert-eos:sgx


  • <node-agent-ip> is the IP address of the compute node registered on Fortanix CCM.
  • 9092 is the port on which Node Agent listens up
  • converted-image-id is the converted app that can be found in the Images tab under the Image Name column in the Images table.
  • Please use your own inputs for Node IP, Port, and Converted Image in the above format. The information in the example above is just a sample.
  • add the following flag along with the command to get more details:
    • -e ENCLAVEOS_LOG_LEVEL=debug - to get debug log
    • -p 7622:80 -p 8038:443 - to map the application custom port to 80 or 443

To verify and monitor the application, click the Applications tab, and verify that there is a running application image associated with it and displayed with the application in the detailed view of the application.

Figure 10: Deployed application



Please sign in to leave a comment.

Was this article helpful?
0 out of 0 found this helpful