---
title: "Discussion on \"Is it possible to use a custom certificate issued by a private certificate authority with custom origin behind CloudFront?\" | Hashnode"
description: "Discussion on \"Is it possible to use a custom certificate issued by a private certificate authority with custom origin behind CloudFront?\". One day an engineer in my team came up with this question.\nThere was no quick answer available, so I started digging and here's what I found.\nCloudFront's docs on CNAMEs and HTTPS requirements say:\n\nCloudFront supports all types of certificates issue..."
url: "https://hashnode.com/posts/is-it-possible-to-use-a-custom-certificate-issued-by-a-private-certificate-authority-with-custom-origin-behind-cloudfront/66fda66a6ee172ff577332c2"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Is it possible to use a custom certificate issued by a private certificate authority with custom origin behind CloudFront?](https://tymik.me/is-it-possible-to-use-a-custom-certificate-issued-by-a-private-certificate-authority-with-custom-origin-behind-cloudfront?utm_source=hashnode&utm_medium=feed)

One day an engineer in my team came up with this question. There was no quick answer available, so I started digging and here's what I found. CloudFront's docs on CNAMEs and HTTPS requirements say: CloudFront supports all types of certificates issue...

Oct 2, 2024 · 2 min read · tymik.me  
Updated Nov 21, 2024  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#cloudfront](https://hashnode.com/tag/cloudfront)
-   [#certificate-authority](https://hashnode.com/tag/certificate-authority)
-   [#security](https://hashnode.com/tag/security)
-   [#cache](https://hashnode.com/tag/cache)

## Written by

[Jan Tymiński](https://hashnode.com/@tymik)

@tymik · Poland

  
[View profile](https://hashnode.com/@tymik)

♾️ DevOps ☁️ AWS 🐳 Docker, Terraform, Automation

I started my professional career in 2012 as Systems Administrator and continued it until 2018 to become DevOps Engineer. I work with AWS since 2016 and I am 5 times certified AWS Specialist.

## Responses 1

Markdown supported · ⌘↵ to post

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 5](https://hashnode.com/posts/is-it-possible-to-use-a-custom-certificate-issued-by-a-private-certificate-authority-with-custom-origin-behind-cloudfront/66fda66a6ee172ff577332c2/comment/6aec968c180e3e2272333d96)

Viewer TLS and origin TLS are separate trust domains on CloudFront: the distribution certificate faces clients, while the private-CA chain only matters on the Origin Protocol Policy path that talks to your origin. Place the private CA or intermediate into the origin trust store CloudFront will use, keep SNI and the origin hostname aligned with what the leaf presents, and avoid match-viewer unless every origin truly terminates with a chain that CloudFront trusts. Keep Authorization and Cookie out of the public cache key on hashed or long-TTL objects so a TLS or auth change does not explode cardinality.

Ops prove-out after attaching the private-CA trust material: hit a warm public path twice and confirm MISS then HIT with Age climbing under the stable host-path key; force an origin fetch on a cold path and confirm the edge completes the origin handshake without certificate errors in the distribution logs. If origin fetches fail only from some POPs, check whether a second origin or failover target still presents a public-CA leaf while the primary uses the private chain — mixed trust stores look like intermittent edge failures when the real issue is origin TLS config drift.
