{"action":"created","issue":{"url":"https://api.github.com/repos/docker/distribution/issues/1562","repository_url":"https://api.github.com/repos/docker/distribution","labels_url":"https://api.github.com/repos/docker/distribution/issues/1562/labels{/name}","comments_url":"https://api.github.com/repos/docker/distribution/issues/1562/comments","events_url":"https://api.github.com/repos/docker/distribution/issues/1562/events","html_url":"https://github.com/docker/distribution/issues/1562","id":143636698,"number":1562,"title":"s3 write layer not working in v2.4.0-rc.0","user":{"login":"drewrobb","id":140935,"avatar_url":"https://avatars.githubusercontent.com/u/140935?v=3","gravatar_id":"","url":"https://api.github.com/users/drewrobb","html_url":"https://github.com/drewrobb","followers_url":"https://api.github.com/users/drewrobb/followers","following_url":"https://api.github.com/users/drewrobb/following{/other_user}","gists_url":"https://api.github.com/users/drewrobb/gists{/gist_id}","starred_url":"https://api.github.com/users/drewrobb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drewrobb/subscriptions","organizations_url":"https://api.github.com/users/drewrobb/orgs","repos_url":"https://api.github.com/users/drewrobb/repos","events_url":"https://api.github.com/users/drewrobb/events{/privacy}","received_events_url":"https://api.github.com/users/drewrobb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-03-26T00:30:19Z","updated_at":"2016-03-30T17:12:32Z","closed_at":null,"body":"Using 2.3.1 I'm able to push layers to s3 fine. Using 2.4.0-rc.0 however this pushing layers fails. Pulling layers and getting layer information is fine. Failure seems to occur using storage driver s3, s3aws, and s3goamz. I'm relying on IAM roles for s3 access credentials. Some of the s3 requests are succeeding, just not the ones when a write operation is needed.\r\n\r\nError message is: `error resolving upload: s3aws: AccessDenied: Access Denied\\n\\tstatus code: 403`\r\n\r\nI can add more details about my configuration and reproducing this if necessary"},"comment":{"url":"https://api.github.com/repos/docker/distribution/issues/comments/203533661","html_url":"https://github.com/docker/distribution/issues/1562#issuecomment-203533661","issue_url":"https://api.github.com/repos/docker/distribution/issues/1562","id":203533661,"user":{"login":"RichardScothern","id":922018,"avatar_url":"https://avatars.githubusercontent.com/u/922018?v=3","gravatar_id":"","url":"https://api.github.com/users/RichardScothern","html_url":"https://github.com/RichardScothern","followers_url":"https://api.github.com/users/RichardScothern/followers","following_url":"https://api.github.com/users/RichardScothern/following{/other_user}","gists_url":"https://api.github.com/users/RichardScothern/gists{/gist_id}","starred_url":"https://api.github.com/users/RichardScothern/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RichardScothern/subscriptions","organizations_url":"https://api.github.com/users/RichardScothern/orgs","repos_url":"https://api.github.com/users/RichardScothern/repos","events_url":"https://api.github.com/users/RichardScothern/events{/privacy}","received_events_url":"https://api.github.com/users/RichardScothern/received_events","type":"User","site_admin":false},"created_at":"2016-03-30T17:12:32Z","updated_at":"2016-03-30T17:12:32Z","body":"@drewrobb : I expect the registry IAM permissions to align more closely with official AWS tools since we are using their API now.  With the recent refactor of driver code I suspect that more of the S3 API is being used with regards to multipart uploads.  "}}