GridGain Developers Hub
GitHub logo GridGain iso GridGain.com
GridGain Software Documentation

AWS Deployment

This page describes how to use Apache Ignite AMI.

The GridGain AMI (Amazon Machine Image) allows you to quickly deploy a simple GridGain cluster using the Amazon Web Services EC2 Management Console.

  1. Select the region you want to use and click the corresponding link in the table:

    Region Image

    US-WEST

    ami-9cdbb3fc

    US-EAST

    ami-ce82caa4

    EU-CENTRAL

    ami-191b0775

    or launch the EC2 Management Console and, from the Launch Instance Wizard, search for the image in Community AMIs by using the keyword Apache Ignite:

    ami search
  2. Choose an Instance Type.

  3. Go to Configure Instance and expand the Advanced Details section.

  4. Add any of the following configuration parameters:

    Name Description Default Example

    CONFIG_URI

    URL to the Ignite configuration file (can also be relative to the META-INF folder on the class path). The downloaded config file will be saved to ./ignite-config.xml

    N/A

    https://raw.githubusercontent.com/apache/ignite/master/examples/config/example-cache.xml

    OPTION_LIBS

    Ignite optional libs which will be included in the class path.

    ignite-log4j, ignite-spring, ignite-indexing

    ignite-aws,ignite-aop

    JVM_OPTS

    Environment variables passed to the Ignite instance in your docker command.

    N/A

    -Xms1g -Xmx1g -server -XX:+AggressiveOpts -XX:MaxPermSize=256m

    EXTERNAL_LIBS

    List of URL’s to libs.

    N/A

    http://central.maven.org/maven2/io/undertow/undertow-servlet/1.3.10.Final/undertow-servlet-1.3.10.Final.jar,http://central.maven.org/maven2/io/undertow/undertow-build-config/1.0.0.Beta24/undertow-build-config-1.0.0.Beta24.jar

    IGNITE_VERSION

    Version of Apache Ignite

    'latest'

    2.7.5

    as shown here:

    ami advanced details
  5. On the Tag Instance, set the value for the Name tag. For example gg-node.

  6. Review and run instances.

  7. Connect to the instances: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstances.html.

  8. To access the execution progress, you need to know the container id. Use the following command:

    sudo docker ps
  9. Show the logs:

    sudo docker logs -f CONTAINER_ID
  10. Enter the docker container:

    sudo docker exec -it container_id /bin/bash