Hi Guys. I can confirm now that your suggested approach did work well and we now have a grid running in AWS using S3 as IP facilitator. The only obstacle we had was with S3Finder supplied with Ignite. It assumes the access to the root of the file structure in S3. This is not always the case (not in our set up where particular development group has access only to a dedicated node somewhere down the tree) and required overriding S3Finder with a custom one allowing configurable initial path to be defined. I suggest you consider extending Ignite's S3Finder to allow this (just a new attribute etc).
However, we've got a problem in setting up a node within a JBOSS container as part of a hybrid topology we are trying to build. I am listing this as a separate problem: "Setting up Ignite node inside JBOSS 6 container". Many thanks for your help. Cheers, Alex -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/AWS-Integration-tp495p994.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
