1.0 Introduction
The Fortanix Confidential Computing Manager (CCM) Terraform Provider transforms the functionality of the Fortanix CCM RESTful API into easy-to-consume, human-readable configuration files. Using the Fortanix CCM Terraform Provider, you can eliminate the need to understand how to consume raw Fortanix CCM APIs.
This article provides an overview of the Terraform Provider, including its installation and supported features.
2.0 Download
Download the Fortanix CCM Terraform Provider from here.
3.0 Features
The Fortanix CCM Terraform Provider SDK supports the following operations:
3.1 Authentication
Fortanix CCM Terraform Provider supports Username and Password-based authentication methods for users.
3.2 Builds
A Fortanix CCM build is a particular software release or a version of an application. Each build is associated with a trusted workload identity (for example, an enclave measurement such as MRENCLAVE for SGX-based workloads).
NOTE
A build can be created only after the corresponding application has been created for the respective build. For detailed instructions to create an application, refer to Create an Application.
You can create and delete the following types of application builds in Fortanix CCM:
Enclave OS (Operating System):
AWS Nitro Enclaves
Enclave Development Platform (EDP)
Intel SGX
AWS Nitro Enclaves
Application Configuration Instance (ACI)
Advanced Micro Devices (AMD) Secure Encrypted Virtualization (SEV) – Secure Nested Paging (SNP)
Azure Confidential Virtual Machine (CVM)
You can approve an application build after it is created. When a build is approved, Fortanix CCM recognizes workloads with the associated identity as trusted instances of the corresponding application and issues certificates with the application’s domain name(s) to those workloads.
4.0 References
For detailed information on the Terraform Provider client, refer to Fortanix CCM Terraform Provider.