Video | Tableau | Data prep | Tool strategy

Connect to AWS S3 with Tableau Connector | New in tableau 2023.2

The new S3 connector in 2023.2 is genuinely handy, but it's still beta — and the Cloud version is zippier than my Mac, bar that final mile.

Part ofWhat's new in Tableau 2023.2
Watch on YouTube
  • The S3 connector isn't installed by default, so you download the TACO file from the Tableau Exchange and drop it into the connectors folder of your Tableau Desktop or Prep repository, then restart Tableau.
  • As a beta there's no auto-update mechanism, so you have to manually check the version on the Exchange against the one you're running, or have IT push the file in enterprise setups.
  • The connector needs four things to authenticate: bucket region, bucket name, access key ID and secret access key; it reads data live from S3 and can pull every CSV in a bucket directory.
  • It connects to CSV and Excel files but not hyper files, and metadata detection is weak, so everything comes through as text and geographic fields aren't reliably recognised.
  • The Tableau Cloud experience felt faster and smoother than Mac Desktop, but feature parity isn't complete, with some map and null-handling behaviours not working the same way.

Tim tries out Tableau's new S3 connector while it's still in beta, showing how to install it, connect live to files in a bucket, and where it currently falls short — useful if you want to evaluate it before relying on it in production.

The connector shipped in beta with 2023.2 and isn't bundled with Tableau, so it has to be fetched separately. Tim tests it in both Tableau Desktop (on a Mac) and Tableau Cloud, connecting to CSV files sitting in an Amazon S3 bucket.

The Breakdown
  1. Install the TACO file first 0:09

    Because the connector isn't installed by default, you must download its TACO file from the Tableau Exchange and place it in the connectors folder of your Tableau Desktop or Prep repository, then restart Tableau — this step is a prerequisite before the connector appears in your data source list.

  2. Manage beta updates yourself 2:12

    As a beta release there's no auto-update mechanism, so you need to periodically check the Exchange version against what you've installed and manually replace the file; in an enterprise setting, IT can push the file centrally instead.

  3. Authenticate with four details 3:00

    To connect you need the bucket region, bucket name, access key ID and secret access key — have these ready beforehand, since the connector can't proceed without them. Watch out for the initial connection opening a web window that can slip behind your main Tableau window, making it look stuck.

  4. Reading files from the bucket 4:58

    Once authenticated it scans the whole bucket directory; selecting a CSV pulls in every CSV across the directory structure, which is handy if a bucket is a dumping ground for regularly-added files, though there's no option to write custom SQL against it or to keep it continuously scanning for new files. It reads CSV and Excel, not hyper files, and the connection is live rather than an extract.

  5. Build visuals as normal off the live connection 9:20

    Once fields are in, you can build charts and maps exactly as with any other data source — assigning geographic roles, sizing and colouring marks — treating the S3 data as though it were any live-connected table.

  6. Same setup, different experience in Cloud 11:54

    The connector works the same way in Tableau Cloud — same four credentials, same web window — but the connection and rendering felt noticeably faster since traffic stays within the cloud provider's backbone rather than crossing the open internet to a desktop machine.

  7. Feature parity isn't complete 17:37

    Some behaviours differed between Desktop and Cloud, such as geographic role handling and null-value indicators not rendering the same way, so don't assume identical results across platforms while it's in beta.

Worth Knowing
  • It can't read hyper files, so it's not a way to store and refresh hyper extracts via S3.
  • Excel file connections were buggy for Tim, though this may be tied to his unsupported Mac OS version rather than the connector itself.
  • There's no way to write custom SQL against the bucket, and no built-in option to continuously watch the bucket for new files.
  • Geographic fields often aren't recognised automatically, so postcodes or similar may default to the wrong country and need manual correction.
Use It When

Reach for this when you need Tableau to read CSV or Excel files sitting directly in an S3 bucket without a separate ETL step, but treat it as exploratory rather than production-ready while it remains in beta.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.