Repository navigation
feat: Add mTLS and connection function support - #163
Merged
Andriy Knysh (aknysh) merged 1 commit intoJun 17, 2026
Merged
Andriy Knysh (aknysh) merged 1 commit into
Andriy Knysh (aknysh) merged 1 commit into
Conversation
Nick Hawkins (nickhawkins-proof)
requested review from
Joe Niland (joe-niland) and
Kevin (kevcube)
June 11, 2026 17:08
Member
|
/terratest |
Andriy Knysh (aknysh)
approved these changes
Jun 17, 2026
|
These changes were released in v1.8.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what
viewer_mtls_configvariable and dynamic block to enable mutual TLS (mTLS) authentication on the distributionconnection_function_idvariable and dynamic block to associate a CloudFront connection function with the distributionexamples/mtls— a self-contained example that provisions a self-signed test CA (via thetlsprovider), an S3-backedaws_cloudfront_trust_store, and two module instances (one with mTLS required, one without) to demonstrate the feature and verify the null default is a no-opwhy
aws_cloudfront_distributionresourcesnull, existing configurations see zero plan diff, and the existing terratest fixtures are unchangedexamples/mtls, confirmed via the CloudFront API that the distribution carriesMode: requiredwith the trust store attached, confirmed requests without a client certificate are rejected while requests presenting a certificate issued by the trust-store CA reach the origin, and confirmed a distribution created with the current module code showsNo changeswhen re-planned with this branchaws >= 6.13.0constraint already supports both blocks — no provider bump neededreferences