moomindani opened a new issue, #63621: URL: https://github.com/apache/airflow/issues/63621
### Description AWS recently announced [account-regional namespaces for Amazon S3 general purpose buckets](https://aws.amazon.com/blogs/aws/introducing-account-regional-namespaces-for-amazon-s3-general-purpose-buckets/) (March 12, 2026). This feature allows creating S3 buckets in an account-regional namespace (e.g., `mybucket-123456789012-us-east-1-an`) instead of the global namespace, eliminating the need for globally unique bucket names. `S3Hook.create_bucket()` and `S3CreateBucketOperator` should support creating buckets in the account-regional namespace. The underlying boto3 `create_bucket` API now accepts a `BucketInfo` parameter with `Type` and `DataRedundancy` fields for this purpose. ### Use case/motivation Users who want to create S3 buckets in their account-regional namespace using Airflow DAGs currently have no way to pass the required `BucketInfo` parameter through `S3Hook.create_bucket()` or `S3CreateBucketOperator`. With the new S3 account-regional namespace, organizations can: - Create buckets without worrying about global name uniqueness - Use IAM policies and SCPs with the `s3:x-amz-bucket-namespace` condition key to enforce that buckets are only created in the account-regional namespace - Build workloads that use a bucket per customer, team, or dataset with predictable naming ### Related issues - AWS announcement: https://aws.amazon.com/about-aws/whats-new/2026/03/amazon-s3-account-regional-namespaces/ - AWS blog post: https://aws.amazon.com/blogs/aws/introducing-account-regional-namespaces-for-amazon-s3-general-purpose-buckets/ - Terraform AWS provider tracking issue: https://github.com/hashicorp/terraform-provider-aws/issues/46902 ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
