Certificates resources

Azion Terraform Provider resource and data sources that create and read digital certificates: azion_digital_certificate and azion_digital_certificates.

Last updated

View as Markdown Agent setup
View in Terraform Registry

A digital certificate is the SSL/TLS certificate and private key pair that lets an application answer over HTTPS. The Azion Terraform Provider manages the certificates of Certificate Manager with one resource and reads them with two data sources.

Certificate resources

ResourceDescription
azion_digital_certificateCreates and manages a digital certificate.

azion_digital_certificate requires three string arguments: name, the name of the certificate; certificate, the SSL/TLS certificate in PEM format; and private_key, the private key in PEM format. It exports id, a string that holds the unique ID of the certificate. The Terraform Registry page of the resource lists every argument.

Data sources

Data sourceDescription
azion_digital_certificatesLists digital certificates.
azion_digital_certificateReads one digital certificate.

Example

This configuration pins the provider, creates a certificate from a certificate file and a private key file in the certificates folder of the module, reads the existing certificates, and outputs the ID of the certificate. It reads your personal token from the api_token variable that the Azion Terraform Provider quickstart declares.

HCL
01terraform {
02 required_providers {
03 azion = {
04 source = "aziontech/azion"
05 version = "2.0.0"
06 }
07 }
08}
09
10provider "azion" {
11 api_token = var.api_token
12}
13
14# Create digital certificate
15resource "azion_digital_certificate" "my_cert" {
16 name = "certificate-mydomain"
17 certificate = file("${path.module}/certificates/mydomain.pem")
18 private_key = file("${path.module}/certificates/mydomain-key.pem")
19}
20
21# Query existing certificates
22data "azion_digital_certificates" "all" {}
23
24output "certificate_id" {
25 value = azion_digital_certificate.my_cert.id
26}

To keep the certificate and the private key out of the configuration code, declare them as sensitive variables. This block replaces the azion_digital_certificate resource of the configuration above:

HCL
01variable "ssl_certificate" {
02 type = string
03 description = "SSL certificate in PEM format"
04 sensitive = true
05}
06
07variable "ssl_private_key" {
08 type = string
09 description = "SSL private key in PEM format"
10 sensitive = true
11}
12
13resource "azion_digital_certificate" "my_cert" {
14 name = "my-certificate"
15 certificate = var.ssl_certificate
16 private_key = var.ssl_private_key
17}

A shorter form, with cert.pem and key.pem at the root of the module, is on Resources and data sources.

Applications resources

The resources that manage applications, their cache settings, rules, device groups, and function instances.

Edge DNS resources

The resources that manage DNS zones, their records, and their DNSSEC settings.

Security resources

The resources that manage firewalls, WAF rule sets, and network lists.

Migrate from provider v1.x to v2.0

The changes to make when a configuration still uses provider v1.x and API v3.