S3 Uploads reporting success but not showing in S3

jbruett's Avatar


17 May, 2017 11:40 AM

I have a project that runs successfully, and includes an S3 deployment, but that file is not showing in S3. Log and config attached.

  1. 1 Posted by jbruett on 17 May, 2017 11:40 AM

    jbruett's Avatar

    I thought i had posted this yesterday, so sorry if this is somehow duplicated

  2. Support Staff 2 Posted by Ilya Finkelshte... on 17 May, 2017 03:47 PM

    Ilya Finkelshteyn's Avatar

    Please try to remove this line. You upload the same artifact twice and you uploading it from script without setting artifact deployment name (zip in your case). Though you use his name when you upload it from YAML, it seems it does not take any effect because the same file is already uploaded. Your deployment depends deployment name ('zip' in your case) and because of this does not happen.


  3. 3 Posted by jbruett on 17 May, 2017 06:23 PM

    jbruett's Avatar

    Thanks Illya, i removed that line and re-ran the app. I'm getting an error that I had gotten before but haven't found the fix.

    Deploying using S3 provider
    Uploading artifact "DomainMof.zip" (625,627 bytes) to S3 bucket "jb2w-powershell-dsc-mofs" as "DomainMof.zip"
    The request signature we calculated does not match the signature you provided. Check your key and signing method.
  4. Support Staff 4 Posted by Ilya Finkelshte... on 17 May, 2017 06:33 PM

    Ilya Finkelshteyn's Avatar

    This error comes from AWS API and probably means wrong access key. Could it be that you double-encrypted your AWS keys, by entering them into https://ci.appveyor.com/tools/encrypt, and then to AWS deployment provider UI? In any case if you re-enter your keys, with ensuring that no double-encryption happens and no leading/trailing spaces when you encrypt them, i should start working.

  5. 5 Posted by jbruett on 17 May, 2017 06:59 PM

    jbruett's Avatar

    So i guess I'm confused about that. I took the real keys (from the csv file) and encrypted them using the appveyor encrypt page. i then put that encrypted string in as the value for the deployment provider, is that not right? I have them written as follows:

        secure: qWXc5bw/IvA59IACTLx0HUn5M8cUuOKLQ3JEczfyDY0=

    the text after secure: is from the encrypt page

  6. Support Staff 6 Posted by Ilya Finkelshte... on 17 May, 2017 07:28 PM

    Ilya Finkelshteyn's Avatar

    If you put encrypted values into UI and then export configuration to YAML, values will be double-encrypted. If you simple put encrypted values directly to YAML, it is correct.

    But error from AWS API is still related to wrong key, maybe you need to repeat that operation to ensure you included all characters and no unneeded spaces.

  7. 7 Posted by jbruett on 17 May, 2017 08:20 PM

    jbruett's Avatar

    that was it...i switched them out once previously and it still didn't work, created a new set of keys and encrypted them and it's all working now! Thanks Ilya

  8. jbruett closed this discussion on 17 May, 2017 08:20 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac