I am trying to deploy an Apache Ignite cluster in our AWS VPC. I have done the following:
• Created an S3 Bucket to store the ignite-config.xml file o Uploaded the config file to the bucket. Config file contents (just based on example in github): <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:util="http://www.springframework.org/schema/util"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util.xsd";> <bean id="grid.cfg" class="org.apache.ignite.configuration.IgniteConfiguration"> <property name="cacheConfiguration"> <list> <bean class="org.apache.ignite.configuration.CacheConfiguration"> <property name="name" value="IgniteCache"/> <property name="cacheMode" value="PARTITIONED"/> <property name="atomicWriteOrderMode" value="PRIMARY"/> <property name="writeSynchronizationMode" value="PRIMARY_SYNC"/> <property name="evictionPolicy"> <bean class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy"> <property name="maxSize" value="100000000"/> </bean> </property> <property name="swapEnabled" value="false"/> <property name="atomicityMode" value="ATOMIC" /> <property name="backups" value="1" /> </bean> </list> </property> <property name="discoverySpi"> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> <property name="ipFinder"> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder"> <property name="awsCredentials" ref="aws.creds"/> <property name="bucketName" value="S3BucketNAME-ignite-discovery"/> </bean> </property> </bean> </property> <property name="communicationSpi"> <bean class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> <property name="slowClientQueueLimit" value="1000"/> </bean> </property> </bean> <bean id="aws.creds" class="com.amazonaws.auth.BasicAWSCredentials"> <constructor-arg value="ABCDEFGHIJKLMNOPRST" /> <constructor-arg value="A1B2C3D4E5F6G7H8I9J1A1B2C3D4E5F6G7H8" /> </bean> </beans> • Created an S3 bucket for S3 Discovery • Created an IAM role for Ignite-S3-Access with the AmazoneS3FullAccess policy attached and ec2.amazonaws.com as a trusted entity • Launched an EC2 instance from the Apache Ignite AMI for the us-east-1 region o In my VPC private subnet o With IAM role created above for S3 Access o User Data: CONFIG_URI=https://s3.amazonaws.com/S3BucketName-ignite-config/ignite-config.xml When I log into the instance, the docker container is NOT running. I can verify that the IAM role for S3 is working by typing aws s3 ls and getting a list of all s3 buckets. If I try to manually start the docker container with the command: sudo docker run -it --net=host -e "CONFIG_URI=https://s3.amazonaws.com/S3BucketName-ignite-config/test-cluster.xml"; apacheignite/ignite I get a 403 which makes since as the S3Bucket is not public: o class org.apache.ignite.IgniteException: Failed to instantiate Spring XML application context [springUrl=https://s3.amazonaws.com/S3BucketName-ignite-config/test-cluster.xml, err=IOException parsing XML document from URL [https://s3.amazonaws.com/S3BucketName-ignite-config/test-cluster.xml]; nested exception is java.io.IOException: Server returned HTTP response code: 403 for URL: https://s3.amazonaws.com/S3BucketName-ignite-config/test-cluster.xml] If I try running it like this: sudo docker run -it --net=host -e "CONFIG_URI=$CONFIG_URI" apacheignite/ignite it seems to start but does not register it’s ip with the S3 Discovery bucket. I'm a newbie and would appreciate this groups assistance! Please help me see what I'm missing. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
