{"id":"data-transfers.s3-bucket-could-not-be-found","url":"/faq/data-transfers/s3-bucket-could-not-be-found","category":{"id":"data-transfers","title":"Data Transfers"},"subcategory":{"id":"problems","title":"Problems and messages"},"question":"Why did my transfer fail with “the S3 bucket couldn't be found”?","alt_questions":["S3 bucket couldn't be found","NoSuchBucket error mac","S3 transfer fails bucket not found","wrong bucket name transfer","Bucket field S3 account"],"short_answer":"The path didn't start with a bucket that exists on that account. Edit the account under More → Connect Accounts…, set its Bucket field to your real bucket name, and run the transfer again.","answer_markdown":"On a bucket account, the first part of the destination path has to be the bucket's name. The transfer was sent to a bucket that doesn't exist on that account — usually because the path didn't start with the bucket, or the name is spelled differently (bucket names are lower-case).\n\nThe message shows the name it tried. To fix it, open the account's settings under **More → Connect Accounts…**, choose **Edit**, set the **Bucket** field to your real bucket name, and run the transfer again; Storage Studio then adds the bucket to every path for you.\n\nRelated: [Transfer to an Amazon S3 bucket](/faq/data-transfers/transfer-to-amazon-s3-bucket) · [Cloud accounts](/faq/cloud-accounts/)","answer_html":"

On a bucket account, the first part of the destination path has to be the bucket's name. The transfer was sent to a bucket that doesn't exist on that account — usually because the path didn't start with the bucket, or the name is spelled differently (bucket names are lower-case).

\n

The message shows the name it tried. To fix it, open the account's settings under More → Connect Accounts…, choose Edit, set the Bucket field to your real bucket name, and run the transfer again; Storage Studio then adds the bucket to every path for you.

\n

Related: Transfer to an Amazon S3 bucket · Cloud accounts

","answer_text":"On a bucket account, the first part of the destination path has to be the bucket's name. The transfer was sent to a bucket that doesn't exist on that account — usually because the path didn't start with the bucket, or the name is spelled differently (bucket names are lower-case).\n\nThe message shows the name it tried. To fix it, open the account's settings under More → Connect Accounts…, choose Edit, set the Bucket field to your real bucket name, and run the transfer again; Storage Studio then adds the bucket to every path for you.\n\nRelated: Transfer to an Amazon S3 bucket · Cloud accounts","tags":["amazon s3","bucket","error message"],"related":[{"id":"data-transfers.transfer-to-amazon-s3-bucket","question":"How do I transfer files to an Amazon S3 bucket?","url":"/faq/data-transfers/transfer-to-amazon-s3-bucket"},{"id":"data-transfers.a-transfer-failed-what-now","question":"A transfer failed — how do I find out why and try again?","url":"/faq/data-transfers/a-transfer-failed-what-now"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"Why did my transfer fail with “the S3 bucket couldn't be found”? — Storage Studio FAQ","description":"The path didn't start with a bucket that exists on that account. Edit the account under More → Connect Accounts…, set its Bucket field to your real bucket name, and run the transfer again.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Data Transfers","path":"/faq/data-transfers/"},{"name":"Why did my transfer fail with “the S3 bucket couldn't be found”?","path":"/faq/data-transfers/s3-bucket-could-not-be-found"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/data-transfers/s3-bucket-could-not-be-found","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"Why did my transfer fail with “the S3 bucket couldn't be found”?","alternateName":["S3 bucket couldn't be found","NoSuchBucket error mac","S3 transfer fails bucket not found","wrong bucket name transfer","Bucket field S3 account"],"acceptedAnswer":{"@type":"Answer","text":"On a bucket account, the first part of the destination path has to be the bucket's name. The transfer was sent to a bucket that doesn't exist on that account — usually because the path didn't start with the bucket, or the name is spelled differently (bucket names are lower-case).\n\nThe message shows the name it tried. To fix it, open the account's settings under More → Connect Accounts…, choose Edit, set the Bucket field to your real bucket name, and run the transfer again; Storage Studio then adds the bucket to every path for you.\n\nRelated: Transfer to an Amazon S3 bucket · Cloud accounts","url":"https://storagestudio.us/faq/data-transfers/s3-bucket-could-not-be-found"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Data Transfers · Problems and messages

\n

Why did my transfer fail with “the S3 bucket couldn't be found”?

\n

Short answer: The path didn't start with a bucket that exists on that account. Edit the account under More → Connect Accounts…, set its Bucket field to your real bucket name, and run the transfer again.

\n

On a bucket account, the first part of the destination path has to be the bucket's name. The transfer was sent to a bucket that doesn't exist on that account — usually because the path didn't start with the bucket, or the name is spelled differently (bucket names are lower-case).

\n

The message shows the name it tried. To fix it, open the account's settings under More → Connect Accounts…, choose Edit, set the Bucket field to your real bucket name, and run the transfer again; Storage Studio then adds the bucket to every path for you.

\n

Related: Transfer to an Amazon S3 bucket · Cloud accounts

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}