This module creates a self-signed certificate and writes it alongside with its key to SSM Parameter Store (or alternatively AWS Secrets Manager).
This project is part of our comprehensive "SweetOps" approach towards DevOps.
It's 100% Open Source and licensed under the APACHE2.
We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!
Security scanning is graciously provided by Bridgecrew. Bridgecrew is the leading fully hosted, cloud-native solution providing continuous Terraform security and compliance.
| Benchmark | Description |
|---|---|
| Infrastructure Security Compliance | |
| Center for Internet Security, KUBERNETES Compliance | |
| Center for Internet Security, AWS Compliance | |
| Center for Internet Security, AZURE Compliance | |
| Payment Card Industry Data Security Standards Compliance | |
| National Institute of Standards and Technology Compliance | |
| Information Security Management System, ISO/IEC 27001 Compliance | |
| Service Organization Control 2 Compliance | |
| Center for Internet Security, GCP Compliance | |
| Health Insurance Portability and Accountability Compliance |
IMPORTANT: We do not pin modules to versions in our examples because of the difficulty of keeping the versions in the documentation in sync with the latest released versions. We highly recommend that in your code you pin the version to the exact version you are using so that your infrastructure remains stable, and update versions in a systematic way so that they do not catch you by surprise.
Also, because of a bug in the Terraform registry (hashicorp/terraform#21417), the registry shows many of our inputs as required when in fact they are optional. The table below correctly indicates which inputs are required.
For a complete example, see examples/complete.
module "self_signed_cert" {
source = "cloudposse/ssm-tls-self-signed-cert/aws"
# Cloud Posse recommends pinning every module to a specific version
# version = "x.x.x"
namespace = "eg"
stage = "dev"
name = "self-signed-cert"
subject = {
common_name = "example"
organization = "Cloud Posse"
organizational_unit = "Engineering"
}
validity = {
duration_hours = 730
early_renewal_hours = 24
}
allowed_uses = [
"key_encipherment",
"digital_signature",
"server_auth"
]
subject_alt_names = {
ip_addresses = ["10.10.10.10"]
dns_names = ["example.com"]
uris = ["https://example.com"]
}
}Here is an example of using this module:
examples/complete- complete example of using this module.
Available targets:
help Help screen
help/all Display help for all targets
help/short This help short screen
lint Lint terraform code
| Name | Version |
|---|---|
| terraform | >= 0.13.0 |
| aws | >= 3.0 |
| tls | >= 3.2.0 |
| Name | Version |
|---|---|
| aws | >= 3.0 |
| tls | >= 3.2.0 |
| Name | Source | Version |
|---|---|---|
| this | cloudposse/label/null | 0.25.0 |
| Name | Type |
|---|---|
| aws_acm_certificate.default | resource |
| aws_secretsmanager_secret.certificate | resource |
| aws_secretsmanager_secret.private_key | resource |
| aws_secretsmanager_secret_version.certificate | resource |
| aws_secretsmanager_secret_version.private_key | resource |
| aws_ssm_parameter.certificate | resource |
| aws_ssm_parameter.private_key | resource |
| tls_cert_request.default | resource |
| tls_locally_signed_cert.default | resource |
| tls_private_key.default | resource |
| tls_self_signed_cert.default | resource |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| additional_tag_map | Additional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id.This is for some rare cases where resources want additional configuration of tags and therefore take a list of maps with tag key, value, and additional configuration. |
map(string) |
{} |
no |
| allowed_uses | List of keywords each describing a use that is permitted for the issued certificate. Must be one of of the values outlined in self_signed_cert.allowed_uses. |
list(string) |
n/a | yes |
| asm_recovery_window_in_days | Number of days that AWS Secrets Manager waits before it can delete the secret. This value can be 0 to force deletion without recovery or range from 7 to 30 days.This value is ignored if var.certificate_backends is not ASM, or if var.certificate_backend_enabled is false. |
number |
30 |
no |
| attributes | ID element. Additional attributes (e.g. workers or cluster) to add to id,in the order they appear in the list. New attributes are appended to the end of the list. The elements of the list are joined by the delimiterand treated as a single ID element. |
list(string) |
[] |
no |
| basic_constraints | The basic constraints of the issued certificate. Currently, only the CA constraint (which identifies whether the subject of the certificate is a CA) can be set.Defaults to this certificate not being a CA. |
object({ |
{ |
no |
| certificate_backend_kms_key_id | The KMD Key ID (ARN or ID) to use when encrypting either the AWS SSM Parameters or AWS Secrets Manager Secrets relating to the certificate. If not specified, the Amazon-managed Key alias/aws/ssm will be used if var.certificate_backends contains SSM,and alias/aws/secretsmanager will be used if var.certificate_backends is ASM. |
string |
null |
no |
| certificate_backends | The certificate backend to use when writing secrets related to the self-signed certificate. The value specified can either be SSM (AWS Systems Manager Parameter Store), ASM (AWS Secrets Manager), and/or ACM (AWS Certificate Manager).Defaults to SSM. |
set(string) |
[ |
no |
| certificate_backends_base64_enabled | Enable or disable base64 encoding of secrets before writing them to the secrets store. | bool |
false |
no |
| certificate_backends_enabled | Enable or disable writing to the secrets store. | bool |
true |
no |
| certificate_chain | When using ACM as a certificate backend, some certificates store a certificate chain from a CA. This CA will come from another resource. | object({ |
null |
no |
| context | Single object for setting entire context at once. See description of individual variables for details. Leave string and numeric variables as null to use default value.Individual variable settings (non-null) override settings in context object, except for attributes, tags, and additional_tag_map, which are merged. |
any |
{ |
no |
| delimiter | Delimiter to be used between ID elements. Defaults to - (hyphen). Set to "" to use no delimiter at all. |
string |
null |
no |
| descriptor_formats | Describe additional descriptors to be output in the descriptors output map.Map of maps. Keys are names of descriptors. Values are maps of the form {<br> format = string<br> labels = list(string)<br>}(Type is any so the map values can later be enhanced to provide additional options.)format is a Terraform format string to be passed to the format() function.labels is a list of labels, in order, to pass to format() function.Label values will be normalized before being passed to format() so they will beidentical to how they appear in id.Default is {} (descriptors output will be empty). |
any |
{} |
no |
| enabled | Set to false to prevent the module from creating any resources | bool |
null |
no |
| environment | ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT' | string |
null |
no |
| id_length_limit | Limit id to this many characters (minimum 6).Set to 0 for unlimited length.Set to null for keep the existing setting, which defaults to 0.Does not affect id_full. |
number |
null |
no |
| label_key_case | Controls the letter case of the tags keys (label names) for tags generated by this module.Does not affect keys of tags passed in via the tags input.Possible values: lower, title, upper.Default value: title. |
string |
null |
no |
| label_order | The order in which the labels (ID elements) appear in the id.Defaults to ["namespace", "environment", "stage", "name", "attributes"]. You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present. |
list(string) |
null |
no |
| label_value_case | Controls the letter case of ID elements (labels) as included in id,set as tag values, and output by this module individually. Does not affect values of tags passed in via the tags input.Possible values: lower, title, upper and none (no transformation).Set this to title and set delimiter to "" to yield Pascal Case IDs.Default value: lower. |
string |
null |
no |
| labels_as_tags | Set of labels (ID elements) to include as tags in the tags output.Default is to include all labels. Tags with empty values will not be included in the tags output.Set to [] to suppress all generated tags.Notes: The value of the name tag, if included, will be the id, not the name.Unlike other null-label inputs, the initial setting of labels_as_tags cannot bechanged in later chained modules. Attempts to change it will be silently ignored. |
set(string) |
[ |
no |
| name | ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'. This is the only ID element not also included as a tag.The "name" tag is set to the full id string. There is no tag with the value of the name input. |
string |
null |
no |
| namespace | ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique | string |
null |
no |
| private_key_algorithm | The name of the algorithm for the private key of the certificate. Currently only RSA and ECDSA are supported. If a preexisting private key is supplied via var.private_key_contents, this value must match that key's algorithm.Defaults to RSA as it is a more widely adopted algorithm, although ECDSA provides the same level of security and with shorter keys. |
string |
"RSA" |
no |
| private_key_contents | The contents of the private key to use for the certificate. If supplied, this module will not create a private key and use these contents instead for the private key. Defaults to null, which means a private key will be created. |
string |
null |
no |
| private_key_ecdsa_curve | When var.cert_key_algorithm is ECDSA, the name of the elliptic curve to use. May be any one of P224, P256, P384 or P521.Ignored if var.cert_key_algorithm is not ECDSA, or if a preexisting private key is supplied via var.private_key_contents.Defaults to the tls provider default. |
string |
"P224" |
no |
| private_key_rsa_bits | When var.cert_key_algorithm is RSA, the size of the generated RSA key in bits.Ignored if var.cert_key_algorithm is not RSA, or if a preexisting private key is supplied via var.private_key_contents.Defaults to the tls provider default. |
number |
2048 |
no |
| regex_replace_chars | Terraform regular expression (regex) string. Characters matching the regex will be removed from the ID elements. If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits. |
string |
null |
no |
| secret_extensions | The extensions use when writing secrets to the certificate backend. Please refer to var.secret_path_format for information on how secret paths are computed. |
object({ |
{ |
no |
| secret_path_format | The path format to use when writing secrets to the certificate backend. The certificate secret path will be computed as format(var.secret_path_format, var.name, var.secret_extensions.certificate)and the private key path as format(var.secret_path_format, var.name, var.secret_extensions.private_key).Thus by default, if var.name=example-self-signed-cert, then the resulting secret paths for the self-signed certificate'sPEM file and private key will be /example-self-signed-cert.pem and /example-self-signed-cert.key, respectively.This variable can be overridden in order to create more specific certificate backend paths. |
string |
"/%s.%s" |
no |
| skid_enabled | Whether or not the subject key identifier (SKID) should be included in the certificate. | bool |
false |
no |
| stage | ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release' | string |
null |
no |
| subject | The subject configuration for the certificate. This should be a map that is compatible with tls_cert_request.subject. If common_name is omitted, it will be set as module.this.id. |
any |
{} |
no |
| subject_alt_names | The subject alternative name (SAN) configuration for the certificate. This configuration consists of several lists, each of which can also be set to null or [].dns_names: List of DNS names for which a certificate is being requested.ip_addresses: List of IP addresses for which a certificate is being requested.uris: List of URIs for which a certificate is being requested.Defaults to no SANs. |
object({ |
{ |
no |
| tags | Additional tags (e.g. {'BusinessUnit': 'XYZ'}).Neither the tag keys nor the tag values will be modified by this module. |
map(string) |
{} |
no |
| tenant | ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for | string |
null |
no |
| use_locally_signed | Create a locally signed certificate/key pair instead of a self-signed one. This is useful it a previously created certificate chain is to be used to sign a certificate. | bool |
false |
no |
| validity | Validity settings for the issued certificate:duration_hours: The number of hours from issuing the certificate until it becomes invalid.early_renewal_hours: If set, the resource will consider the certificate to have expired the given number of hours before its actual expiry time (see: self_signed_cert.early_renewal_hours).Defaults to 10 years and no early renewal hours. |
object({ |
{ |
no |
| Name | Description |
|---|---|
| certificate_arn | ARN of certificate stored in ACM that other services may need to refer to. This is useful when the certificate is stored in ACM. |
| certificate_key_path | Secrets store path containing the certificate private key file. |
| certificate_pem | Contents of the certificate PEM. |
| certificate_pem_path | Secrets store path containing the certificate PEM file. |
Like this project? Please give it a ★ on our GitHub! (it helps us a lot)
Are you using this project or any of our other projects? Consider leaving a testimonial. =)
Check out these related projects.
- terraform-null-label - Terraform module designed to generate consistent names and tags for resources. Use terraform-null-label to implement a strict naming convention.
For additional context, refer to some of these links.
- Terraform Standard Module Structure - HashiCorp's standard module structure is a file and directory layout we recommend for reusable modules distributed in separate repositories.
- Terraform Module Requirements - HashiCorp's guidance on all the requirements for publishing a module. Meeting the requirements for publishing a module is extremely easy.
- Terraform
random_integerResource - The resource random_integer generates random values from a given range, described by the min and max attributes of a given resource. - Terraform Version Pinning - The required_version setting can be used to constrain which versions of the Terraform CLI can be used with your configuration
Got a question? We got answers.
File a GitHub issue, send us an email or join our Slack Community.
We are a DevOps Accelerator. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
- Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
- Release Engineering. You'll have end-to-end CI/CD with unlimited staging environments.
- Site Reliability Engineering. You'll have total visibility into your apps and microservices.
- Security Baseline. You'll have built-in governance with accountability and audit logs for all changes.
- GitOps. You'll be able to operate your infrastructure via Pull Requests.
- Training. You'll receive hands-on training so your team can operate what we build.
- Questions. You'll have a direct line of communication between our teams via a Shared Slack channel.
- Troubleshooting. You'll get help to triage when things aren't working.
- Code Reviews. You'll receive constructive feedback on Pull Requests.
- Bug Fixes. We'll rapidly work with you to fix any bugs in our projects.
Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.
Participate in our Discourse Forums. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
Sign up for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
Join us every Wednesday via Zoom for our weekly "Lunch & Learn" sessions. It's FREE for everyone!
Please use the issue tracker to report any bugs or file feature requests.
If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull Request so that we can review your changes
NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!
Copyright © 2020-2022 Cloud Posse, LLC
See LICENSE for full details.
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
All other trademarks referenced herein are the property of their respective owners.
This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!
We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.
We offer paid support on all of our projects.
Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.
 Yonatan Koren |
 RB |
|---|