Credentials for download link

#1

I was able to generate a zip archive and get zip state. Now how do I gain access to the url? when navigating to my new generated zip stream “https://api.s3zipper.com/streamv2?u=blah-blah-blah” I get
{
“message”: “Credentials Error found.”,
“error”: “Access Denied”
}

#2

So, this is a valid error from S3 - Access Denied.
You can get a better error by running zipstart instead(to test).
Let me know what you find out.

#3

Does the user I setup need write permissions to my bucket? The user I setup does not. I was under the assumption that stream zip streams directly to the browser from your service at https://api.s3zipper.com

#4

I am now using “zip start”. I did not give it “zipTo” or any of the “destAws…” parameters. since your docs state that it would default to “{{awsBucket}}/zipped”. The AWS user does not have write permission so I would think that an error would be thrown when it attempted to place the zip file in my bucket it does not.

results from the api calls are:

zipstart returns “STARTED” & taskUUID streams3v2 zipper_s3_58ea9b9b-6660-4891-b658-7a096f969ca4

zipstate returns:
TaskUUID “zipper_web_eda768d1-e21e-4174-be18-7cb75391ceed”
taskname “idurlv2”
state “success”
results (array) value: https://api.s3zipper.com/streamv2?u=5fddd564-8fc3-4411-ba27-c32544de3a3c

#5

I am looking into it now.

#6

I just added permissions to write to my bucket and i can now see a file called filename_o.zip. so permissions were an issue. the file name I gave it was “/filename.zip” but it created the file as “/filename_0.zip” not sure if that is normal.

so now I can create and access the file when using zip start. still though the issue I would like to resolve is zipStream.

#7

I would have mentioned checking if you can access the zipstart URL too. Chances are that you would get the same error.
“/filename_0.zip” is normal because you can do zip splitting in cases where you want chunks of it, or is too big to download.
I think it is read/write error. See https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_s3_rw-bucket.html

#8

I can access zip start. that is what I cam currently calling to create the zip archive in my bucket. what I really need is zip stream. Isn’t “https://api.s3zipper.com/streamv2?u=5fddd564-8fc3-4411-ba27-c32544de3a3c” a call to your service? why would your service respond with “{
“message”: “Credentials Error found.”,
“error”: “Access Denied”
}”

#9

I will check the logs to see what else is going on. I will run a few tests too

#10

It looks like we use two different methods to check for credential validity on both API calls.
I will get streamzip updated to use the newer method that is less intrusive.

For now make sure your credentials can ListBuckets. That should solve that.
I should probably get this done by weekend end.

#11

I added the following to the aim user but it still doesn’t work for steamship,
{
“Effect”:“Allow”,
“Action”:[“s3:ListBucket”,“s3:GetBucketLocation”],
“Resource”:“arn:aws:s3:::my bucket”
}

#12

The good news is that the new fix works. The bad news is that the code-base is mid-update and would be breaking if updated now. So expect a fix by this weekend.

#13

Sounds good. I opened an unlimited account and will open another once this works. Thank you.

#14

If you really need to fix that till the update, run listbuckets on your credentials with python, Php, or your programming language. Just a simple function.

#15

It can wait till Monday. thanks

#16

The new update is up and running.
It was tested enough but this was a big update.
Please report any bugs or errors that you find.