Answers.Body: <p>I did end up opening a support ticket with Craft- they immediately suggested that this could be caused by a firewall. To which I scoffed! But after talking with some other folks in the office, this seems to be the case.</p>
  
  <p>Unfortunately we never found a firewall solution to this problem. What <em>did</em> work was to assign a static IP to my computer that bypasses the http-proxy packet filter.</p>
  
  <p>So yeah. Firewall. Dang.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-11-24T08:34:52.180Z
Answers.Text: Could you elaborate on this solution? I'm having the same problem now, and can't figure out how to get around it. There doesn't seem to be a firewall solution to this problem as S3 doesn't have a static IP that you can rely on hitting every time. I can upload when I try it on the remote server, but not on my local machine. So I'm guessing that setting a fixed IP on my machine as you said would be the solution. So what exactly did you do to bypass the http-proxy packet filter?
Answers.UserDisplayName: peirix
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-16T21:19:28.877Z
Answers.LastActivityDate: 2016-06-16T21:19:28.877Z
Answers.UserDisplayName: plaintxt
Body: <p>I'm a total S3 noob but would like to get it set up so that I can store Assets there. So far, I've:</p>
  
  <ul>
  <li>created an AWS account (zing!)</li>
  <li>created a bucket named <code>mybucket</code></li>
  <li>created a user in IAM <code>myuser</code></li>
  <li>assigned the <code>AdministratorAccess</code> policy to <code>myuser</code>*</li>
  <li>created a new Asset source called <code>s3</code></li>
  <li>entered the user Access Key ID and Secret Access Key, which correctly shows me the <code>mybucket</code> destination</li>
  <li>URL Prefix is auto-filled with <code>http://s3.amazonaws.com/mybucket</code></li>
  </ul>
  
  <p>OK! When I go to upload a file to the S3 source, I see the upload stripe go all the way across the page and the loading spinner happening at the top right of the page. But this process hangs and the file is never uploaded.</p>
  
  <p>This is a tiny image, so I don't think it's a file size issue. No errors / warnings are produced. I don't see anything obvious in the logs.</p>
  
  <p>Any help is appreciated! Thanks!</p>
  
  <p>--</p>
  
  <p>*I know that I'll eventually want a more restrictive policy but for the time being, just trying to get a Hello World working.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-04T14:37:01.693Z
Comments.Text: Sounds like an excellent opportunity to open a support ticket with us, providing logfiles in the process!
Comments.UserDisplayName: Andris Sevcenko
Tags: <assets><s3>
Title: Basic Amazon S3 Setup
ThreadText: # Basic Amazon S3 Setup
  
  (Asked by: username_0 on 2016-03-02)
  
  I'm a total S3 noob but would like to get it set up so that I can store Assets there. So far, I've:
  
  * created an AWS account (zing!)
  * created a bucket named `mybucket`
  * created a user in IAM `myuser`
  * assigned the `AdministratorAccess` policy to `myuser`\*
  * created a new Asset source called `s3`
  * entered the user Access Key ID and Secret Access Key, which correctly shows me the `mybucket` destination
  * URL Prefix is auto-filled with `http://s3.amazonaws.com/mybucket`
  
  OK! When I go to upload a file to the S3 source, I see the upload stripe go all the way across the page and the loading spinner happening at the top right of the page. But this process hangs and the file is never uploaded.
  
  This is a tiny image, so I don't think it's a file size issue. No errors / warnings are produced. I don't see anything obvious in the logs.
  
  Any help is appreciated! Thanks!
  
  --
  
  \*I know that I'll eventually want a more restrictive policy but for the time being, just trying to get a Hello World working.
  
  **Tags:** assets, s3
  
  > **Comments:**
  > **username_1**: Sounds like an excellent opportunity to open a support ticket with us, providing logfiles in the process!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-06-16. Score: 3
  
  I did end up opening a support ticket with Craft- they immediately suggested that this could be caused by a firewall. To which I scoffed! But after talking with some other folks in the office, this seems to be the case.
  
  Unfortunately we never found a firewall solution to this problem. What *did* work was to assign a static IP to my computer that bypasses the http-proxy packet filter.
  
  So yeah. Firewall. Dang.
  
  > **Comments:**
  > **username_2**: Could you elaborate on this solution? I'm having the same problem now, and can't figure out how to get around it. There doesn't seem to be a firewall solution to this problem as S3 doesn't have a static IP that you can rely on hitting every time. I can upload when I try it on the remote server, but not on my local machine. So I'm guessing that setting a fixed IP on my machine as you said would be the solution. So what exactly did you do to bypass the http-proxy packet filter?  
  
  ---
  
  