AWS S3 Deploy: success but not uploading anything
Asked by Amirull Yusuf Zulkarnain:

Hello everyone, i need help about this issue.

i got a situation when usiong aws s3 deploy,

the pipeline build was successfull, the log can see bellow

![Screenshot 2023-04-29 151154.png](https://community.atlassian.com/t5/image/serverpage/image-id/254559i6B6FD73054F7652E/image-size/large?v=v2&px=999 "Screenshot 2023-04-29 151154.png")  

*** ** * ** ***

But when i check the S3 Bucket, there is nothing. the bucket are still empy

![Screenshot 2023-04-29 151328.png](https://community.atlassian.com/t5/image/serverpage/image-id/254562iC28010538C9B0C71/image-size/large?v=v2&px=999 "Screenshot 2023-04-29 151328.png")

Whats wrong, do i missing something?

*** ** * ** ***

and this is my Bitbucket pipelines,

my apps using Vue/Nuxt3 to be deploy on S3 and Cloud front, this is the full pipelines yml

```
image: node:16


pipelines:

  default:

    - parallel:

      - step:

          name: Build and Test

          caches:

            - node

          script:

            - npm install

      - step:

          name: Lint the node package

          script:

            - npm install eslint

          caches:

            - node

  branches:

    development:

      - parallel:

        - step:

            name: Build and Test

            caches:

              - node

            script:

              - npm install

              - npm run build

            artifacts:

              - .output

        - step:

            name: Security Scan

            script:

              - pipe: atlassian/git-secrets-scan:1.2.1

      - step:

          name: Deploy to Production

          deployment: Development

          clone:

            enabled: false

          script:

            # sync your files to S3

            - pipe: atlassian/aws-s3-deploy:1.2.0

              variables:

                AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID

                AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY

                AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION

                S3_BUCKET: $S3_BUCKET

                ACL: 'public-read'

                LOCAL_PATH: '$(pwd)'

            # triggering a distribution invalidation to refresh the CDN caches

            - pipe: atlassian/aws-cloudfront-invalidate:0.7.0

              variables:

                AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID

                AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY

                AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION

                DISTRIBUTION_ID: $DISTRIBUTION_ID


```


Answers:
author: Erez Maadani
body: Hi [@Amirull Yusuf Zulkarnain](/t5/user/viewprofilepage/user-id/5207622)

Try adding the DEBUG variable to get more info. You can also try and add the PRE_EXECUTION_SCRIPT to list the files in your \`pwd\` and make sure they exist where you think they should.

Have a look here: <https://bitbucket.org/atlassian/aws-s3-deploy/src/master/> for more details.

comments: author: Igor Stoyanov
body: [@Amirull Yusuf Zulkarnain](/t5/user/viewprofilepage/user-id/5207622) hi.  
To update previous answer.  
Seems like the folder that you want to upload is empty.  
Maybe you need to upload with artifacts.  
Check [this article](https://support.atlassian.com/bitbucket-cloud/docs/use-artifacts-in-steps/) for more info.  

Regards, Igor


Tags: aws

bitbucket-cloud

cloud