Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated with note about HTTPS enforcement #23106

Merged
merged 3 commits into from
May 10, 2024
Merged

Updated with note about HTTPS enforcement #23106

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fda4545
Update tls_ciphers_deprecation.md
michaelcretzman May 9, 2024
a1e5861
Update content/en/data_security/guide/tls_ciphers_deprecation.md
michaelcretzman May 10, 2024
8b1643b
updating TLS requirement
michaelcretzman May 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion content/en/data_security/guide/tls_ciphers_deprecation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,9 @@

As part of its ongoing commitment to the security and protection of its customer's data, Datadog is rolling out a more modern cryptographic engine across its systems which imposes some changes to the configurations it can accept.

Beginning **April 1st, 2024**, Datadog is disabling support for the following cipher suites across its public-facing applications. If you use unsupported clients to connect to Datadog after the older protocols are disabled, you will receive connection error messages.
Beginning **April 1st, 2024**, Datadog disabled support for the following cipher suites across its public-facing applications. If you use unsupported clients to connect to Datadog after the older protocols are disabled, you will receive connection error messages.

Starting **July 1st, 2024**, Datadog will force HTTP to HTTPS redirection for all intake endpoints, using an HTTP 308 response code. This change is necessary as some intake endpoints still accept plain HTTP payloads to maintain compatibility with older API clients. Ensure that your application clients can follow these redirection codes, or update their configuration to utilize HTTPS. Otherwise, you might receive connection error messages.

## Disabled Cipher Suites

Expand Down
2 changes: 1 addition & 1 deletion content/en/integrations/fluentbit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Before you begin, you need to have a [Datadog account][3], a [Datadog API key][4
| Key | Description | Default |
| -------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- |
| Host | _Required_ - The Datadog server where you are sending your logs. | {{< region-param key="http_endpoint" code="true" >}} |
| TLS | _Required_ - End-to-end security communications security protocol. Datadog recommends setting this to `on`. | `off` |
| TLS | _Required_ - End-to-end security communications security protocol. This setting must be set to `on`. | `off` |
| apikey | _Required_ - Your [Datadog API key][4]. | |
| compress | _Recommended_ - compresses the payload in GZIP format, Datadog supports and recommends setting this to `gzip`. | |
| dd_service | _Recommended_ - The human readable name for your service generating the logs - the name of your application or database. | |
Expand Down
Loading