Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws s3 cp command not working #4160

Closed
jackyenbioinfo opened this issue May 17, 2019 · 2 comments
Closed

aws s3 cp command not working #4160

jackyenbioinfo opened this issue May 17, 2019 · 2 comments
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made.

Comments

@jackyenbioinfo
Copy link

Hi,

my aws s3 cp command is not working for some reason. The command looks like this

aws s3 cp --profile user1 --acl bucket-owner-full-control --sse AES256 "file.coverage.csv" "s3://h3bioinf-share-cgi/22916002/NGS/20190516_data/file.coverage.csv"

It shows the following without error,
upload: ./file.coverage.csv to s3://h3bioinf-share-cgi/22916002/NGS/20190516_data/file.coverage.csv

however, when I do the aws ls command. I could not see the file, any thoughts? It was working for a while and it stopped all of a sudden....Thanks

aws s3 ls --profile usera s3://h3bioinf-share-cgi/22916002/NGS/20190516_data/ --recursive --human-readable --summarize

@kyleknap
Copy link
Contributor

kyleknap commented Sep 4, 2019

I ran the commands provided and I was not able to reproduce:

$ echo hello > file.coverage.csv

$ aws s3 cp --acl bucket-owner-full-control --sse AES256 "file.coverage.csv" "s3://mybucketfoo/22916002/NGS/20190516_data/file.coverage.csv"
upload: ./file.coverage.csv to s3://mybucketfoo/22916002/NGS/20190516_data/file.coverage.csv

$ aws s3 ls  s3://mybucketfoo/22916002/NGS/20190516_data/ --recursive --human-readable --summarize
2019-09-04 13:44:15    6 Bytes 22916002/NGS/20190516_data/file.coverage.csv

Total Objects: 1
   Total Size: 6 Bytes

Could you share the debug logs when running the ls command? You can do so by appending --debug to the command you ran.

@kyleknap kyleknap added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Sep 4, 2019
@no-response
Copy link

no-response bot commented Sep 11, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Sep 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made.
Projects
None yet
Development

No branches or pull requests

2 participants