Using GridGain 9 AMI
GridGain provides an AMI with the latest version of GridGain 9 preinstalled.
Prerequisites
-
An existing AWS account
Considerations
Choose the right type of instances that suit your needs. The following instance types are supported:
| Instance type family | Instance type |
|---|---|
M6i |
m6i.xlarge m6i.2xlarge m6i.4xlarge m6i.8xlarge m6i.12xlarge m6i.16xlarge m6i.24xlarge m6i.32xlarge m6i.metal |
T3 |
t3.large t3.xlarge t3.2xlarge |
C5 |
c5.large c5.xlarge c5.2xlarge c5.4xlarge c5.9xlarge c5.12xlarge c5.18xlarge c5.24xlarge c5.metal |
C5d |
c5d.large c5d.xlarge c5d.2xlarge c5d.4xlarge c5d.9xlarge c5d.12xlarge c5d.18xlarge c5d.24xlarge c5d.metal |
R5 |
r5.large r5.xlarge r5.2xlarge r5.4xlarge r5.8xlarge r5.12xlarge r5.16xlarge r5.24xlarge r5.metal |
R5d |
r5d.large r5d.xlarge r5d.2xlarge r5d.4xlarge r5d.8xlarge r5d.12xlarge r5d.16xlarge r5d.24xlarge r5d.metal |
R6i |
r6i.large r6i.xlarge r6i.2xlarge r6i.4xlarge r6i.8xlarge r6i.12xlarge r6i.16xlarge r6i.24xlarge r6i.32xlarge r6i.metal |
Consider the following points:
-
RAM: If you are going to use GridGain as an in-memory storage, make sure to select an instance with enough RAM to fit all your data.
-
Disk space: If you are launching a cluster with a persistent storage, provide enough size to accommodate all your data when configuring the instance’s volume.
-
Networking: GridGain nodes discover and communicate with each other by TCP/IP. A number of ports must be open for this communication. See Configuring Security Group.
Obtaining GridGain AMI
Visit the GridGain 9 product page corresponding to the edition you need, and launch the AMI from there.
Providing a license
GridGain 9 AMI image comes with free license. No additional actions are required to start the cluster.
Configuring IAM Role and Instance Profile
Optionally, you can attach IAM role to instances via Instance Profile. These are recomended policies to attach to this role:
-
arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore- to allow Amazon Systems Manager to manage the instance and to allow connections from Amazon Session Manager; -
arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy- to allow CloudWatch Agent on the instance write logs to CloudWatch Logs.
Configuring Security Group
When configuring the instances, you will be asked to specify a security group. The security group must allow connection to the following ports:
| Protocol | Port | Description |
|---|---|---|
SSH |
22 |
Used for SSH connection. |
TCP |
3344 |
Communication port for clustering. |
TCP |
10300 |
Cluster management ports. |
TCP |
10800 |
REST API request ports. |
These are the default ports that GridGain nodes use for discovery and communication purposes. If you want to use values other than the default ones, open them.
This is what our security group should look like:
In the security group settings above, we opened connection from any source. Use more secure settings in your production environment!
Launching GridGain Nodes
You can use GridGain 9 Terraform AWS Module to create EC2 instances and all supplementary resources (VPC, EIPs, S3 bucket, ELB, etc). Please refer to GridGain 9 Terraform AWS Module documentation.
Connect to the EC2 instance via ssh as per the AWS documentation. Make sure to provide the same credentials that were used to launch the EC2 instance.
The default user name is gg_rw_user. The ssh command would look like (change the IP address with the actual public IP of your image):
ssh -i your_key.pem gg_rw_user@@54.173.158.228
You can change the user name after first login, if needed. For information on how to create a custom user name, see AWS documentation for Linux user accounts.
GridGain is installed as RPM. It provides systemd service gridgain9db which can be managed using systemctl. Because the service is enabled by default, it should start automatically and be up and running soon after the instance launch.
Configuring Discovery
Cluster nodes launched in different EC2 instances must be able to connect to each other. Please refer to Network Configuration to let cluster nodes discover each other.
Troubleshooting Your AWS Deployment
If you provided CloudWatch Agent policy, instances will publish logs to CloudWatch Logs. Agent on the instances is already pre-configured to publish GridGain node logs. Pre-configured log location is gridgain9-db-9.0.17\log.
© 2025 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.