AWS S3

  • 31 Jan

    AWS S3 MD5 digest with multipart uploads

    AWS S3 MD5 digest with multipart uploads

    In version v2023.1.31.0 we added Verify support for multipart uploads. Some very interesting information can be found here:

    So ..

    1. If an object is created by a Multipart Upload operation, the ETag is not an MD5 digest, regardless of the method of encryption.
    2. For multipart uploads the ETag is the MD5 hexdigest of each part’s MD5 digest concatenated together, followed by the number of parts separated by a dash.

    We added code to recalculate the MD5 hex digest using the Filesize of the download and the ETag ‘stripped number of parts’ we received from the S3 object. This way we could calculate the size and MD5 checksum for each part. This information was used to calculate the MD5 hex digest of the concatenated checksums.

    By default ‘Verify File after Copy / Move’ is enabled which uses the ETag of the S3 object (File) as MD5 hash to compare the download result.

    Limagito File Mover AWS S3 MD5 digest

    #FileTransfer #awss3

    If you need any info about this ‘AWS S3 compatible storage providers’ option, please let us know.

    Best regards,

    Limagito Team

     

    By Limagito-Team AWS S3
  • 29 Jan

    AWS S3 compatible storage providers

    In version v2023.1.27.0 we made some code changes to make it work with AWS S3 compatible storage providers.

    In the AWS S3 setup select ‘Custom’ as Region. Next set the URL and Region ID of your custom storage provider.

    Limagito File Mover S3 compatible storage providers

    #FileTransfer #awss3

    If you need any info about this ‘AWS S3 compatible storage providers’ option, please let us know.

    Best regards,

    Limagito Team

  • 05 Sep

    AWS connection failed with code 403

    AWS connection failed with code 403

    In case you are getting error messages like:

    GetBucketLocation AWSS3, SB Bucket XYZ-XYZ-XYZ Exists Exception: HTTP request failed with code 403 (Forbidden). Error code: AccessDenied

    or

    <Error>

        <Code>PermanentRedirect</Code>

        <Message>The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.</Message>

        <Endpoint>XYZ-XYZ-XYZ.s3-eu-west-1.amazonaws.com</Endpoint>

        <Bucket>XYZ-XYZ-XYZa</Bucket>

        <RequestId>…</RequestId>

        <HostId>…</HostId>

    </Error>

    , Code: 301

    This could mean that you are trying to connect to a wrong endpoint. In this case please adjust in andpoint in the AWS S3 setup:

    Limagito File Mover AWS S3 endpoint

    We prefer as API Vendor: Vendor 2 – CK. So please first check if this Vendor is selected.

    Limagito File Mover AWS S3 second API Vendor

    If you want the maximum of log information, please enable ‘Add Control Information to Log’.

    Limagito File Mover AWS S3 setup

    If you need any help with this ‘AWS connection failed with code 403’ , please let us know.

    Best Regards,

    Limagito Team

    #filetransfer #filemanagement

    By Limagito-Team AWS S3 ,
1 2
SEARCH