Answers.Body: <p>This question is really more about S3 than about Craft. What you need for the assets is not the file path, but the url. And yes, S3 assets do have a url. <a href="http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html">This page</a> describes the format for the host:</p>
  
  <pre><code>&lt;bucket-name&gt;.s3-website-&lt;AWS-region&gt;.amazonaws.com
  </code></pre>
  
  <p>They give these examples:</p>
  
  <blockquote>
    <p>This URL requests the photo.jpg object, which is stored at the root level in the bucket.</p>
  </blockquote>
  
  <pre><code>http://examplebucket.s3-website-us-east-1.amazonaws.com/photo.jpg
  </code></pre>
  
  <blockquote>
    <p>This URL requests the docs/doc1.html object in your bucket.</p>
  </blockquote>
  
  <pre><code>http://examplebucket.s3-website-us-east-1.amazonaws.com/docs/doc1.html
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-23T18:28:09.903Z
Answers.Text: I feel silly having asked now. Thank you for clarifying that!
Answers.UserDisplayName: taylor
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-28T18:52:36.340Z
Answers.Text: I'd recommend setting setting up a CNAME in your DNS to point to S3 instead of grabbing it directly (basically mapping your bucket to something like ``cdn.whatever.com``). That gives you some flexibility if you ever need to cut AWS out of the picture or change datacenters within AWS.
Answers.UserDisplayName: RitterKnight
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-23T10:16:12.970Z
Answers.LastActivityDate: 2015-12-23T10:16:12.970Z
Answers.UserDisplayName: Marion Newlevant
Body: <p>New to remote assets, and can't seem to find any information on accessing remote assets via filepath in areas twig can't be used, such as CSS. I'd like to be able to use those same assets in CSS files but can't seem to find them.</p>
  
  <p>For example, if I named my remote Amazon S3 Asset Source handle to 'amazon', and it has sub folders <code>asset/images/template</code> for an example, would there be a way to reach the files in a file path such as <code>amazon/assets/images/template/filename.jpg</code> for use in CSS and whatnot?</p>
  
  <p>Any information would be greatly appreciated. Thanks!</p>
  
Tags: <assets><css><s3>
Title: Do Remote Assets (ie. S3) have file paths?
ThreadText: # Do Remote Assets (ie. S3) have file paths?
  
  (Asked by: username_0 on 2015-12-23)
  
  New to remote assets, and can't seem to find any information on accessing remote assets via filepath in areas twig can't be used, such as CSS. I'd like to be able to use those same assets in CSS files but can't seem to find them.
  
  For example, if I named my remote Amazon S3 Asset Source handle to 'amazon', and it has sub folders `asset/images/template` for an example, would there be a way to reach the files in a file path such as `amazon/assets/images/template/filename.jpg` for use in CSS and whatnot?
  
  Any information would be greatly appreciated. Thanks!
  
  **Tags:** assets, css, s3
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-12-23. Score: 5 | Accepted answer
  
  This question is really more about S3 than about Craft. What you need for the assets is not the file path, but the url. And yes, S3 assets do have a url. [This page](http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html) describes the format for the host:
  
  ```
  <bucket-name>.s3-website-<AWS-region>.amazonaws.com
  
  ```
  
  They give these examples:
  
  > This URL requests the photo.jpg object, which is stored at the root level in the bucket.
  
  ```
  http://examplebucket.s3-website-us-east-1.amazonaws.com/photo.jpg
  
  ```
  
  > This URL requests the docs/doc1.html object in your bucket.
  
  ```
  http://examplebucket.s3-website-us-east-1.amazonaws.com/docs/doc1.html
  
  ```
  
  > **Comments:**
  > **username_0**: I feel silly having asked now. Thank you for clarifying that!  
  > **username_2**: I'd recommend setting setting up a CNAME in your DNS to point to S3 instead of grabbing it directly (basically mapping your bucket to something like ``cdn.whatever.com``). That gives you some flexibility if you ever need to cut AWS out of the picture or change datacenters within AWS.  
  
  ---
  
  