# Dvc push to public S3 bucket

**URL:** <https://discuss.dvc.org/t/dvc-push-to-public-s3-bucket/457>\
**Category:** Questions\
**Created:** [July 28, 2020, 5:32am UTC](https://discuss.dvc.org/t/dvc-push-to-public-s3-bucket/457 "2020-07-28T05:32:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![braaannigan](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@braaannigan](https://discuss.dvc.org/u/braaannigan)\
**Post date:** [July 28, 2020, 1:47pm UTC](https://discuss.dvc.org/t/dvc-push-to-public-s3-bucket/457/2 "2020-07-28T13:47:42Z")

</div>

I’m having a similar issue with pushing to a private bucket. It might be related to IAM roles.

In my case I also get a 404 when I do `dvc push`. I get the same error if I just run `aws s3 ls s3://bucket-name`.

However, if I add my work profile name it works: `aws s3 ls s3://bucket-name --profile work-profile`

I’ve tried setting the AWS\_PROFILE env variable to `work-profile`, but nothing changes. Any idea how I force it to see the right profile?

---

_[View the full topic](https://discuss.dvc.org/t/dvc-push-to-public-s3-bucket/457)._