ManagedCertificateRequest
¶
Used by
Source code in docs_src/capo_cloudfront/types/managed_certificate_request.py
certificate_transparency_logging_preference
instance-attribute
¶
certificate_transparency_logging_preference: NotRequired[
CertificateTransparencyLoggingPreference
]
You can opt out of certificate transparency logging by specifying the disabled option. Opt in by specifying enabled. For more information, see Certificate Transparency Logging in the Certificate Manager User Guide.
primary_domain_name
instance-attribute
¶
primary_domain_name: NotRequired[string]
The primary domain name associated with the CloudFront managed ACM certificate.
validation_token_host
instance-attribute
¶
validation_token_host: ValidationTokenHost
Specify how the HTTP validation token will be served when requesting the CloudFront managed ACM certificate.
-
For
cloudfront, CloudFront will automatically serve the validation token. Choose this mode if you can point the domain's DNS to CloudFront immediately. -
For
self-hosted, you serve the validation token from your existing infrastructure. Choose this mode when you need to maintain current traffic flow while your certificate is being issued. You can place the validation token at the well-known path on your existing web server, wait for ACM to validate and issue the certificate, and then update your DNS to point to CloudFront.