You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on IT policies, it may not be possible to use an S3 bucket for DVC remote storage because it may not be possible to obtain bucket-level access permissions. In these situations, S3 access points for DVC remote provide a possible alternative because access policies can be attached to access points that grant access permissions at the "subdirectory" level.
One way to add support for S3 access points would be allow the DVC remote storage URLs to be AWS ARN identifiers. Unfortunately, the current URL processing implementation is unable to handle ARN identifiers because it attempts to interpret the portion of the ARN after the first colon as a port:
Port could not be cast to integer value as 'aws:s3:us-west-2:123456789012:accesspoint'
The text was updated successfully, but these errors were encountered:
Depending on IT policies, it may not be possible to use an S3 bucket for DVC remote storage because it may not be possible to obtain bucket-level access permissions. In these situations, S3 access points for DVC remote provide a possible alternative because access policies can be attached to access points that grant access permissions at the "subdirectory" level.
One way to add support for S3 access points would be allow the DVC remote storage URLs to be AWS ARN identifiers. Unfortunately, the current URL processing implementation is unable to handle ARN identifiers because it attempts to interpret the portion of the ARN after the first colon as a port:
Port could not be cast to integer value as 'aws:s3:us-west-2:123456789012:accesspoint'
The text was updated successfully, but these errors were encountered: