Skip to content

Conversation

@ngayerie
Copy link
Contributor

Summary

Clarifying ACM vs SaaS for the cipher suites configuration

@ngayerie ngayerie requested review from a team and RebeccaTamachiro as code owners April 30, 2025 16:09
@github-actions github-actions bot added the product:ssl Related to SSL label Apr 30, 2025
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Apr 30, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Clarified the differences between Advanced Certificate Manager and Cloudflare for SaaS regarding cipher suites configuration.

  • Updated the description of cipher suites configuration for Advanced Certificate Manager.
  • Added information about cipher suites configuration for Cloudflare for SaaS.
  • Clarified the context for restricting cipher suites in relation to custom hostnames.

Modified Files

  • src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.


With an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription, you can restrict connections between Cloudflare and clients — such as your visitor's browser — to specific [cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/).
With an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription, you can restrict connections between clients — such as your visitor's browser — and Cloudflare to specific [cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/).
With a [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) subscription, you can configure cipher suites for the connection between clients and [Custom Hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR, @ngayerie! I would like to suggest making it a blue box NOTE instead of a paragraph, since it's a guide for the Advanced Certificate subscription. This way, we can redirect people who start reading it and are looking for the Custom Hostname guide.

:::note
If you are a SaaS provider looking to restrict cipher suites for connections to [Custom Hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/), this can be configured with a [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) subscription. Refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites) instead.
:::

And after that, we can delete the ### Cloudflare for SaaS part from this page entirely, as it caused confusion in the first place.

@RebeccaTamachiro
Copy link
Contributor

Thank you, @ngayerie and @kurumar
Updated via #22268

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants