INV-393 - Restrict size of batch query result from Dynamo

As per Matthew we need max 500 results at a time. This is a stop gap fix to make sure that places where we have too many results coming back do not crash cause of the payload size.

Signed-off-by: Tajinder Singh <tajinder.singh@clicktravel.com>
Updated collection mapper to be more generic e.g. allow Sets/Lists to be used as well as Collection
INV-393 - Restrict size of batch query result from Dynamo

Return only 500 results

Signed-off-by: Tajinder Singh <tajinder.singh@clicktravel.com>
Merge branch 'master' of https://github.com/ClickTravel/Cheddar
INV-393 - Restrict size of batch query result from Dynamo

magic number is now static, comments on code review.

Signed-off-by: Tajinder Singh <tajinder.singh@clicktravel.com>
INV-393 - Restrict size of batch query result from Dynamo

comments in review

Signed-off-by: Tajinder Singh <tajinder.singh@clicktravel.com>
[FC-68] Updated CloudSearch infrastructure manager to not any specific policy on newly created CloudSearch domains.
Reverting changes for CollectionMapper
Upgraded version of AWS SDK
INV-393 - Restrict size of batch query result from Dynamo

use sublist()

Signed-off-by: Tajinder Singh <tajinder.singh@clicktravel.com>
refactor

Signed-off-by: Tajinder Singh <tajinder.singh@clicktravel.com>
refactor

Signed-off-by: Tajinder Singh <tajinder.singh@clicktravel.com>
Merge pull request #20 from clicktravel-tajinder/master

INV-393 - Restrict size of batch query result from Dynamo
Merge pull request #21 from clicktravel-basharat/master

Updated CloudSearch creation process not to open it to the world.