Amazon Snowball implements restricted S3 APIs.
New release of mc automatically detects if its a snowball endpoint and turns-on legacy APIs.
Before we begin get the snowball credentials as mentioned here https://docs.aws.amazon.com/snowball/latest/developer-guide/using-client-commands.html#client-credentials
Before you configure to use HTTPS endpoint make sure to obtain the current Snowball Edge certificate following this document https://docs.aws.amazon.com/snowball/latest/developer-guide/using-client-commands.html#snowball-edge-certificates-cli, once obtained same the certificate as shown below
~ mkdir -p ${HOME}/.mc/certs/CAs
~ snowballEdge get-certificate --certificate-arn arn:aws:snowball-device:::certificate/78EXAMPLE516EXAMPLEf538EXAMPLEa7 > ${HOME}/.mc/certs/CAs
Once certificate has been saved you can proceed to creating the alias with the obtained credentials.
~ mc config host add snowball https://<IP address for the S3 Adapter>:8443 AKIAIOSFODNN7EXAMPLE wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Snowball also exposes an insecure endpoint, without the certificate.
~ mc config host add snowball http://<IP address for the S3 Adapter>:8080 AKIAIOSFODNN7EXAMPLE wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Assuming you have a local MinIO setup running configure mc to talk to this cluster
~ mc config host add myminio http://<IP address or Hostname for the MinIO deployment>:9000 Q3AM3UQ867SPQQA43P2F zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG
Start mirror to copy all the buckets and all objects on Amazon Snowball to MinIO.
~ mc mirror snowball/ myminio/