[
https://issues.apache.org/jira/browse/HDDS-13032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hsu Han Wen updated HDDS-13032:
-------------------------------
Description:
This issue is a follow-up from the discussion in [GitHub PR
#8315|https://github.com/apache/ozone/pull/8315#discussion_r2055076240],
specifically regarding how {{S3OwnerId}} is currently represented in s3g.
At the moment, {{S3OwnerId}} is set to the volume owner's username. However,
according to the [AWS account identifier
documentation|https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-identifiers.html],
the {{OwnerId}} in S3 should be a unique, 64-character identifier that
represents the AWS account—not a human-readable name. This misalignment may
lead to incompatibilities with S3 clients or services expecting a standardized
ID format.
We should:
* Refactor the logic to support proper {{S3OwnerId}} generation and
representation.
* Review other usages of {{S3Owner}} in the codebase to ensure consistency
with expected S3 behavior.
A similar issue has been addressed in MinIO, which can serve as a reference:
[https://github.com/minio/minio/issues/4553]
was:
This issue is a follow-up from the discussion in [GitHub PR
#8315|https://github.com/apache/ozone/pull/8315], specifically regarding how
{{S3OwnerId}} is currently represented in s3g.
At the moment, {{S3OwnerId}} is set to the volume owner's username. However,
according to the [AWS account identifier
documentation|https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-identifiers.html],
the {{OwnerId}} in S3 should be a unique, 64-character identifier that
represents the AWS account—not a human-readable name. This misalignment may
lead to incompatibilities with S3 clients or services expecting a standardized
ID format.
We should:
* Refactor the logic to support proper {{S3OwnerId}} generation and
representation.
* Review other usages of {{S3Owner}} in the codebase to ensure consistency
with expected S3 behavior.
A similar issue has been addressed in MinIO, which can serve as a reference:
[https://github.com/minio/minio/issues/4553]
> Support proper S3OwnerId representation in Ozone
> ------------------------------------------------
>
> Key: HDDS-13032
> URL: https://issues.apache.org/jira/browse/HDDS-13032
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: s3gateway
> Reporter: Hsu Han Wen
> Priority: Major
>
> This issue is a follow-up from the discussion in [GitHub PR
> #8315|https://github.com/apache/ozone/pull/8315#discussion_r2055076240],
> specifically regarding how {{S3OwnerId}} is currently represented in s3g.
> At the moment, {{S3OwnerId}} is set to the volume owner's username. However,
> according to the [AWS account identifier
> documentation|https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-identifiers.html],
> the {{OwnerId}} in S3 should be a unique, 64-character identifier that
> represents the AWS account—not a human-readable name. This misalignment may
> lead to incompatibilities with S3 clients or services expecting a
> standardized ID format.
> We should:
> * Refactor the logic to support proper {{S3OwnerId}} generation and
> representation.
> * Review other usages of {{S3Owner}} in the codebase to ensure consistency
> with expected S3 behavior.
> A similar issue has been addressed in MinIO, which can serve as a reference:
> [https://github.com/minio/minio/issues/4553]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
