Java*C#/.NETC++SQLIntegrationsIgnite for SparkTools
Home
JavadocExamplesAsk a Question
Start typing to search…

AWS Deployment

Deploy Ignite within AMI images

❗️

This is a legacy Apache Ignite documentation

The new documentation is hosted here: http://ignite.apache.org/docs/latest/

The Apache Ignite AMI (Amazon Machine Image) allows you to set up and quickly deploy a simple Apache Ignite cluster using the Amazon Web Services EC2 Management Console.

Amazon EC2 Deployment

  1. Choose the required region and click on the link in the table below

Region

Image

US-WEST

ami-9cdbb3fc

US-EAST

ami-ce82caa4

EU-CENTRAL

ami-191b0775

or search the image in Community AMIs by using Apache Ignite keyword:

816
  1. Choose an Instance Type.
  2. Go to Configure Instance and expand the Advanced Details section.
  3. 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

http://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.1.0

as shown in the image below:

882
👍

Preferred Ignite Version

The IGNITE_VERSION attribute can vary depending on the Apache Ignite version of interest.

  1. On the Tag Instance, set the value for Name tag. For example ignite-node.
  2. Review and run instances.
  3. Connect to the instances http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstances.html.
  4. To access the execution progress, you need to know the container id. Use the following command:
sudo docker ps
  1. Show logs:
sudo docker logs -f CONTAINER_ID
  1. Enter the docker container:
sudo docker exec -it container_id /bin/bash

Updated 9 months ago