title: Can I just include a script in ebextensions instead of having to build one?
body: <p>I have seen examples like this for creating and running a script via ebextensions config:</p>
  
  <pre><code>files:
    "C:\\scripts\\whoami.ps1":
      content: |
        date       | out-file -append c:\scripts\whoami.log
        whoami     | out-file -append c:\scripts\whoami.log
        hostname   | out-file -append c:\scripts\whoami.log
        get-module | out-file -append c:\scripts\whoami.log
  
  commands:
    whoami:
      command: powershell.exe -ExecutionPolicy Bypass -Command "C:\\scripts\\whoami.ps1"
      ignoreErrors: false
      waitAfterCompletion: 5
  </code></pre>
  
  <p>That's fine, but can I just include a script in ebextensions and refer to it instead of having to define its content in a config?</p>
  
  <p>for example I would have</p>
  
  <pre><code>myapp
  --.ebextensions
  ----myconfig.config
  ----myscript.ps1
  </code></pre>
  
  <p>And then "myconfig.config" would copy "myscript.ps1" somewhere and run it.</p>
  
  <p>How can I do this?</p>
  
  <p>Edit:
  So I put this command in a config to see what the current path is:</p>
  
  <pre><code>commands:
    whereami:
      command: dir &gt; c:\whereami.log
      ignoreErrors: false
      waitAfterCompletion: 5
  </code></pre>
  
  <p>Its <code>c:\windows\system32</code> which makes sense because it runs in the context of SYSTEM.</p>
  
  <p>Is there no self referential method/keyword I can use to point to a script I have located in the beanstalk project I upload?</p>