2.3. Verifying that Red Hat Gluster Storage Instance is Running
- Navigate to the Amazon Web Services home page at http://aws.amazon.com. The Amazon Web Services home page appears.
- Log in to Amazon Web Services. The AWS Management Console screen is displayed.
- Click the EC2 option. The EC2 Management Console is displayed.
- Click the Instances link from the Instances section on the left. The screen displays your current instances.
- Check the Instance Status column and verify that the instance is running. A yellow circle indicates a status as pending, while a green circle indicates that the instance is running.Select the instance and verify the details displayed in the Description tab.
- Note the domain name in the Public DNS field. You can use this domain to perform a remote login to the instance.
- Log in to the Red Hat Amazon Machine Image instance using the domain from the previous step in the following command:
# ssh -i Kay_Pair_File Public_DNS # sudo su
NoteYou must use the key pair that was selected or created when launching the instance.For example, the key pair file name is
rhs-aws.pem, and the Public DNS is
# ssh -i rhs-aws.pem firstname.lastname@example.org # sudo su
- Verify that the
glusterddaemon is running on the instance using the following command:
# service glusterd status
NoteSamba and NFS-Ganesha channels are disabled by default. To use standalone Samba and NFS-Ganesha, refer the following:
- For enabling and installing the Red Hat Gluster Storage Samba repository, see Deploying Samba on Red Hat Gluster Storage in Red Hat Gluster Storage 3.4 Installation Guide.
- For enabling and installing the Red Hat Gluster Storage NFS-Ganesha repository, see Deploying NFS-Ganesha on Red Hat Gluster Storage in Red Hat Gluster Storage 3.4 Installation Guide.
yum updateto update the Amazon EC2 Red Hat Gluster Storage AMI, follow the steps listed in https://access.redhat.com/solutions/1556793 Knowledgebase article.