Refer to GridGain documentation: https://www.gridgain.com/docs/8.7.6//installation-guide/manual-install-on-ec2
Just swap GridGain with Ignite artifacts, the rest is identical. - Denis On Tue, Oct 15, 2019 at 8:23 AM sri hari kali charan Tummala < [email protected]> wrote: > documentation is not covering step by step it's not that helpful. > > On Tue, Oct 15, 2019 at 10:35 AM Ilya Kasnacheev < > [email protected]> wrote: > >> Hello! >> >> Please refer to the docs: >> >> >> https://apacheignite.readme.io/docs/tcpip-discovery#section-static-ip-finder >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пн, 30 сент. 2019 г. в 17:57, sri hari kali charan Tummala < >> [email protected]>: >> >>> thanks for replying but sorry not getting it please dumb it down, below >>> are my questions. >>> >>> Statically giving the public IP list in the IP configuration section in >>> ignite config file. >>> Question:- wherein the config file should I give the IP address, imagine >>> I launch 3 ec2 instances with public IP should I create a file in S3 bucket >>> with file containing IP address of ec2 instance? >>> >>> Use s3 bucket to configure the IP, and it will automatically discover >>> the related nodes from s3 bucket. >>> Question:- ok I will give the s3 bucket name does the bucket need to >>> have a file containing IP address or just empty bucket? >>> >>> T >>> <https://github.com/aws-samples/aws-big-data-blog/blob/master/aws-blog-real-time-in-memory-oltp-and-analytics-with-apache-ignite/cloudformation/configignite.json> >>> hanks >>> Sri >>> >>> On Mon, Sep 30, 2019 at 1:28 AM Muhammed Favas < >>> [email protected]> wrote: >>> >>>> Hi Sri, >>>> >>>> >>>> >>>> If your nodes created in EC2, it is very simple to start the ignite >>>> cluster. You have two option to configure the IP for all nodes auto >>>> discover the IP. >>>> >>>> 1. Statically giving the public IP list in the IP configuration >>>> section in ignite config file. >>>> 2. Use s3 bucket to configure the IP, and it will automatically >>>> discover the related nodes from s3 bucket. >>>> >>>> >>>> >>>> I am using the 2nd method, and below is the configuration I have given >>>> for my cluster >>>> >>>> >>>> >>>> <!-- Discover IP using Amazon s3. --> >>>> >>>> <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="bucketName" value="yours3bucketname"/> >>>> >>>> <property name="awsCredentials"> >>>> >>>> <bean >>>> class="com.amazonaws.auth.BasicAWSCredentials"> >>>> >>>> <constructor-arg value="YOUR_ACCESS_KEY_ID"/> >>>> >>>> <constructor-arg value="YOUR_SECRET_ACCESS_KEY"/> >>>> >>>> </bean> >>>> >>>> </property> >>>> >>>> </bean> >>>> >>>> </property> >>>> >>>> </bean> >>>> >>>> </property> >>>> >>>> >>>> >>>> >>>> >>>> *Regards,* >>>> >>>> *Favas * >>>> >>>> >>>> >>>> *From:* sri hari kali charan Tummala <[email protected]> >>>> *Sent:* Friday, September 27, 2019 10:02 PM >>>> *To:* [email protected] >>>> *Subject:* Does any one have working Ignite cluster on AWS >>>> >>>> >>>> >>>> Hi All, >>>> >>>> >>>> >>>> can someone help me run a working ignite cuter on AWS , did anyone able >>>> to figure out steps required for setting up working ignite cluster on AWS. >>>> >>>> >>>> >>>> Ignite documentation doesnt make sense it's just launching a docker >>>> instance on Ec2. >>>> >>>> >>>> >>>> -- >>>> >>>> Thanks & Regards >>>> >>>> Sri Tummala >>>> >>>> >>>> >>> >>> >>> -- >>> Thanks & Regards >>> Sri Tummala >>> >>> > > -- > Thanks & Regards > Sri Tummala > >
