From 02ec89d5ff4e8e2d007ca6502c3d3ba37a37a6e6 Mon Sep 17 00:00:00 2001 From: juweins Date: Thu, 2 Feb 2023 19:05:33 +0100 Subject: [PATCH] Fixed: Header for S3 Destination Source S3: Wrong header on Step 1 #22331 --- docs/integrations/destinations/s3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/destinations/s3.md b/docs/integrations/destinations/s3.md index faaff76ca4cb..6818fe235338 100644 --- a/docs/integrations/destinations/s3.md +++ b/docs/integrations/destinations/s3.md @@ -27,7 +27,7 @@ Prepare S3 bucket that will be used as destination, see [this](https://docs.aws. NOTE: If the S3 cluster is not configured to use TLS, the connection to Amazon S3 silently reverts to an unencrypted connection. Airbyte recommends all connections be configured to use TLS/SSL as support for AWS's [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) -## Step 2: Set up the S3 destination connector in Airbyte +### Step 2: Set up the S3 destination connector in Airbyte **For Airbyte Cloud:**