Sure, from an ssh session run the following:-
wget http://www.kernel.org/pub/linux/bluetooth/bluez-5.50.tar.xz
tar xvf bluez-5.50.tar.xz
cd bluez-5.50
sudo apt-get install -y libusb-dev libdbus-1-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev
sudo apt install build-essential
./configure
make
sudo make install
Then reboot your Vero. Pairing the remote is a bit strange, you need to use run bluetoothctl. Then put the Amazon remote into pairing mode then in bluetoothctl do the following:-
scan on
Put the Amazon remote into pairing mode by holding Home and Select until the orange light flashes in the top right corner of the remote. Look for the address of your Amazon remote it will be labeled as AR, if it’s not there type devices and press return and it should pop up.
Then do the following command replacing with your remotes address from above (bluetoothctl supports tab completion so you can type the first few characters of the address and then press tab to auto complete). After issuing each command wait for a response, don’t just go mad and type everything as fast as you can 
pair <address>
trust <address>
connect <address>
Now check if the remote works in kodi, if it doesn’t then do the following:-
disconnect <address>
Put the remote back in to pairing mode by holding Home and Select, then:-
connect <address>
Now it should work, then do:
scan off
exit
Here’s my complete bluetoothctl session for reference:-
osmc@osmc:~$ bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 10:D0:7A:B2:6E:C1 Discovering: yes
[NEW] Device C0:28:8D:DA:12:42 C0-28-8D-DA-12-42
[NEW] Device B0:FC:0D:05:A7:C5 AR
[CHG] Device 58:BC:5A:F3:18:D4 RSSI: -65
[CHG] Device 40:CB:C0:E2:20:2A RSSI: -57
[bluetooth]# devices
Device 0D:B1:69:10:B0:F5 0D-B1-69-10-B0-F5
Device 40:CB:C0:E2:20:2A 40-CB-C0-E2-20-2A
Device 58:BC:5A:F3:18:D4 58-BC-5A-F3-18-D4
Device C0:28:8D:DA:12:42 C0-28-8D-DA-12-42
Device B0:FC:0D:05:A7:C5 AR
[bluetooth]# pair B0:FC:0D:05:A7:C5
Attempting to pair with B0:FC:0D:05:A7:C5
[CHG] Device B0:FC:0D:05:A7:C5 Connected: yes
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 00001813-0000-1000-8000-00805f9b34fb
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: 5de20000-5e8d-11e6-8b77-86f30ca893d3
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: cfbfa000-762c-4912-a043-20e3ecde0a2d
[CHG] Device B0:FC:0D:05:A7:C5 UUIDs: fe151500-5e8d-11e6-8b77-86f30ca893d3
[CHG] Device B0:FC:0D:05:A7:C5 ServicesResolved: yes
[CHG] Device B0:FC:0D:05:A7:C5 Paired: yes
[NEW] Primary Service
/org/bluez/hci0/dev_B0_FC_0D_05_A7_C5/service0001
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
[NEW] Characteristic
/org/bluez/hci0/dev_B0_FC_0D_05_A7_C5/servicefe02/charfe0b
cfbfa004-762c-4912-a043-20e3ecde0a2d
Vendor specific
Pairing successful
[CHG] Device B0:FC:0D:05:A7:C5 Appearance: 0x03c0
[CHG] Device B0:FC:0D:05:A7:C5 Modalias: usb:v0171p0413d0000
[CHG] Device C0:28:8D:DA:12:42 RSSI: -86
[CHG] Device 0D:B1:69:10:B0:F5 RSSI: -53
[AR]# trust B0:FC:0D:05:A7:C5
[CHG] Device B0:FC:0D:05:A7:C5 Trusted: yes
Changing B0:FC:0D:05:A7:C5 trust succeeded
[AR]# connect B0:FC:0D:05:A7:C5
Attempting to connect to B0:FC:0D:05:A7:C5
Connection successful
[AR]# scan off
Discovery stopped
[CHG] Controller 10:D0:7A:B2:6E:C1 Discovering: no
[CHG] Device B0:FC:0D:05:A7:C5 RSSI is nil
[CHG] Device C0:28:8D:DA:12:42 RSSI is nil
[CHG] Device 58:BC:5A:F3:18:D4 RSSI is nil
[CHG] Device 40:CB:C0:E2:20:2A RSSI is nil
[CHG] Device 0D:B1:69:10:B0:F5 RSSI is nil
[AR]# exit