##Windows configuration
- Before starting you should have installed and configured correctly node and npm (versions more than 4.2.4 are supported), and DynamoDB on your computer requires the Java Runtime Engine (JRE) version 6.x or newer; it will not run on older JRE versions.
If You are on
Windows 7you need to have installedWindows SDKforWindows Server 2008and.NET Framework 3.5
- Before starting you should install Git Bash.
It launches a full featured console window running
Bash, so you can useGitas well as a set of common command line tools or Unix programs. Starting with Git version 2,Git Bashwill by default launch inMinTTY, a terminal emulator which comes withMSYS2, making it easily usable even for users not accustomed to a console experience.
2.1. Download [Git Bash](http://git-scm.com/) and launch installer for it.

2.2. Accept license agreement.

2.3. Select destination location.

2.4. Select components.

2.5. Select Start Menu Folder.

2.6. Select Use Git from Windows Command Prompt.

2.7. Select Checkout Windows-style, commit Unix-style line ending.

2.8. Select Use Windows' default console window (this option is required).

2.9. Disable experimental cache for `Windows`.

-
All commands should be run from
MinTTYas root/Administrator.
For using
symlinkfunctionality on Windows you should have admin privileges, because in Windows The default security policy allows only administrators to create symbolic links.Here you can find a little bit more details for know [node issue] (nodejs/node-v0.x-archive#6342).
We suggest always to run
git-bash.exeas Administrator due to different behavior for users:- In case when you are not in
Administratorsgroup you can just update [Local Group Policy] (http://superuser.com/questions/104845/permission-to-make-symbolic-links-in-windows-7), but in many Windows version gpedit.msc is not installed by default. - In case when you belong to the
Administratorsgroup you always have to run in an elevated environment (as Administrator).
Need to take into account that not only core
fs.symlink(target, path[, type], callback)will require symlink permissions. In some case it can befse.ensureSymlinkSync()from fse-extra module and so on, which ensures that the symlink exists. If the directory structure does not exist, it is created. - In case when you are not in
-
Optionally: you need to have the
AWS CLIinstalled and configured to your AWS account otherwise you will need to enter your credentials manually.