AWS Deploy: Launch an Instance and Configure a Host

Document created by RSA Information Design and Development on Feb 6, 2018Last modified by RSA Information Design and Development on Sep 12, 2018
Version 5Show Document
  • View in full screen mode
 

Note: For additional instructions Refer to the AWS "Launching an Instance" documentation (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/usingsharedamis-finding.htmlhttp://docs.aws.amazon.com/AWSEC2/latest/UserGuide/launching-instance.html).

  1. Select an instance from the grid (for example, RSA-NW-Concentrator-11.2.0.0-01) and click Launch.

  1. Choose the RAM and CPUs by selecting instance type.
    Refer to AWS Instance Configuration Recommendations for guidelines on how to configure the EC2 Instance based on the requirements of the NetWitness Platform component (that is, service) for which you are launching an instance. The following example has the m4.2xlarge instance type selected with 8 CPUs and 32 GB of RAM.

  1. Click Next: Configure Instance Details at the bottom right of the Step 2: Choose an Instance Type page.
    The Step 3. Configure Instance Details page is displayed.

    For NetWitness Platform, the subnet and VPC are defaulted to the values in the following example.

  2. Click Next: Add Storage at the bottom right of the Step 3: Configure Instance Details page.
    The Step 4. Add Storage page is displayed.

    Refer to AWS Instance Configuration Recommendations for guidelines on how to configure storage based on based on the requirements of the NetWitness Platform component (that is, service) for which you are launching an instance.

  3. Click Next: Add Tags at the bottom right of the Step 4: Add Storage page.
    The Step 5. Add Tags page is displayed. Enter the name of your Instance.
  4. Click Next: Configure Security Group at the bottom right of the Step 5: Add Tags page.
    The Step 6. Configure Security Group page is displayed.
    1. Select the Create a new security group option.
    2. Create a rule that opens all the firewall for the NetWitness Platform component.
      You must configure the security group correctly to configure the instance (host) from the NetWitness Platform) User Interface and SSH to it.

      Note: See the "Network Architecture and Ports" documentation in RSA Link (https://community.rsa.com/docs/DOC-83050) for a comprehensive list of the ports you must set up for all NetWitness Platform components..

    Note: After you configure a Security Group, you can change it at any time.

  5. Click Review and Launch at the bottom right of the Step 6: Configure Security Group page.
    The Step 7. Review Instance Launch page is displayed.
  6. Click Launch at the bottom right of the Step 7. Review Instance Launch page.
    The Select an existing key pair or create a new key pair dialog is displayed.
  7. Choose Proceed without key pair.
  8. Click Launch Instance.
    AWS displays the following information as it builds the instance.

  9. Click View Instances.
  10. Select Instances in the left navigation panel to review all instances that AWS is initializing (for example, the NW-Concentrator) .

    The IP Address for the new RSA-NW-Concentrator-11.2.0.0-01 host is sample-ip-address.

  11. SSH to newly-created instance using the default NetWitness Platform credentials.
  12. Create the recommended partitions. For more informaiton, see Partition Recommendations.

  13. Go to Configure Hosts (Instances) in NetWitness Platform.

Partition Recommendations

This topic contains the recommended AWS partition.

Admin Server, ESA Primary, ESA Secondary and Malware Analysis

For an extension of /var/netwitness/ partition, attach an external volume.

Run lsblk to get the physical volume name.

If you attach 2 TB disk, run the following commands:

  1. pvcreate <pv_name> (for example, pv_name is /dev/sdc)
  2. vgextend netwitness_vg00 /dev/sdc
  3. lvextend –L 1.9T /dev/netwitness_vg00/nwhome

RSA recommends the following partition. However, you can change these values based on the retention days.

                  
LVM Folder EBS
/dev/netwitness_vg00/nwhome /var/netwitness/Refer to the EBS Volume (storage) tables.

Log Collector

For an extension of /var/netwitness/ partition, attach an external volume

Run lsblk to get the physical volume name.

If you attach one 500 GB volume, run the following commands:

  1. pvcreate <pv_name> (for example, pv_name is dev/sdc)
  2. vgextend netwitness_vg00 /dev/sdc
  3. lvextend –L 600G /dev/netwitness_vg00/nwhome

RSA recommends the following partition. However, you can change these values based on the retention days.

                  
LVM Folder EBS
/dev/netwitness_vg00/nwhome /var/netwitness/ Refer to the EBS Volume (storage) tables.

Decoder

For an extension of /var/netwitness/ partition, attach an external volume and other external volumes for the Decoder database partitions.

Note: No other partition should reside on this Decoder partition and should be used only for /var/netwitness/ partition.

Run lsblk to get the physical volume name.

If you attach 2 TB disk, run the following commands:

  1. pvcreate <pv_name> (for example, pv_name is dev/sdc)
  2. vgextend netwitness_vg00 /dev/sdc
  3. lvextend –L 1.9T /dev/netwitness_vg00/nwhome

Other Partition Required

The following partition should be on the volume group decodersmall.

                                 
Folder LVM Volume Group
/var/netwitness/decoder decorootdecodersmall
/var/netwitness/decoder/indexindexdecodersmall

/var/netwitness/decoder/metadb

metadb

decodersmall

/var/netwitness/decoder/sessiondbsessiondb decodersmall

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md0
  2. vgcreate –s 32 decodersmall /dev/md0
  3. lvcreate –L <disk_size> -n <lvm_name> decodersmall
  4. mkfs.xfs /dev/decodersmall/<lvm_name>
  5. Repeat the above steps for all the LVMs mentioned above.

The following partition should be on the volume group decoder.

                  
Folder LVM Volume Group
/var/netwitness/decoder/packetdbpacketdb decoder

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md1
  2. vgcreate –s 32 decoder /dev/md1
  3. lvcreate –L <disk_size> -n packetdb decoder
  4. mkfs.xfs /dev/decoder/packetdb

RSA recommends the following partition. However, you can change these values based on the retention days.

                                           
LVM Folder EBS
/dev/netwitness_vg00/nwhome /var/netwitness/ Refer to the EBS Volume (storage) tables.
/dev/decodersmall/decoroot /var/netwitness/decoderRefer to the EBS Volume (storage) tables.

/dev/decodersmall/index

/var/netwitness/decoder/index

Refer to the EBS Volume (storage) tables.
/dev/decodersmall/metadb /var/netwitness/decoder/metadbRefer to the EBS Volume (storage) tables.

/dev/decodersmall/sessiondb

/var/netwitness/decoder/sessiondb

Refer to the EBS Volume (storage) tables.
/dev/decoder/packetdb /var/netwitness/decoder/packetdbRefer to the EBS Volume (storage) tables.

Create each directory and mount the LVM on it in a serial manner, except /var/netwitness, which is already created.

After mounting the directory, add the following entries in /etc/fstab in the same order:

  1. /dev/decodersmall/decoroot /var/netwitness/decoder xfs noatime,nosuid 1 2
  2. /dev/decodersmall/index /var/netwitness/decoder/index xfs noatime,nosuid 1 2
  3. /dev/decodersmall/metadb /var/netwitness/decoder/metadb xfs noatime,nosuid 1 2
  4. /dev/decodersmall/sessiondb /var/netwitness/decoder/sessiondb xfs noatime,nosuid 1 2
  5. /dev/decoder/packetdb /var/netwitness/decoder/packetdb xfs noatime,nosuid 1 2

Log Decoder

For an extension of /var/netwitness/ partition, attach an external volume and other external volumes for the Log Decoder database partitions.

Note: No other partition should reside on this Log Decoder partition and should be used only for /var/netwitness/ partition.

Run lsblk to get the physical volume name.

If you attach 2 TB disk, run the following commands:

  1. pvcreate <pv_name> (for example, pv_name is dev/sdc)
  2. vgextend netwitness_vg00 /dev/sdc
  3. lvextend –L 1.9T /dev/netwitness_vg00/nwhome

Other Partition Required

The following partition should be on the volume group logdecodersmall.

                                 
Folder LVM Volume Group
/var/netwitness/logdecoder decorootlogdecodersmall
/var/netwitness/logdecoder/indexindexlogdecodersmall

/var/netwitness/logdecoder/metadb

metadb

logdecodersmall

/var/netwitness/logdecoder/sessiondbsessiondb logdecodersmall

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md0
  2. vgcreate –s 32 logdecodersmall /dev/md0
  3. lvcreate –L <disk_size> -n <lvm_name> logdecodersmall
  4. mkfs.xfs /dev/logdecodersmall/<lvm_name>
  5. Repeat the above steps for all the LVMs mentioned above.

The following partition should be on the volume group logdecoder.

                  
Folder LVM Volume Group
/var/netwitness/logdecoder/packetdbpacketdb logdecoder

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md1
  2. vgcreate –s 32 logdecoder /dev/md1
  3. lvcreate –L <disk_size> -n packetdb logdecoder
  4. mkfs.xfs /dev/logdecoder/packetdb

RSA recommends the following partition. However, you can change these values based on the retention days.

                                           
LVM Folder EBS
/dev/netwitness_vg00/nwhome /var/netwitness/ Refer to the EBS Volume (storage) tables.
/dev/logdecodersmall/decoroot /var/netwitness/logdecoderRefer to the EBS Volume (storage) tables.

/dev/logdecodersmall/index

/var/netwitness/logdecoder/index

Refer to the EBS Volume (storage) tables.
/dev/logdecodersmall/metadb /var/netwitness/logdecoder/metadbRefer to the EBS Volume (storage) tables.

/dev/logdecodersmall/sessiondb

/var/netwitness/logdecoder/sessiondb

Refer to the EBS Volume (storage) tables.
/dev/logdecoder/packetdb /var/netwitness/logdecoder/packetdbRefer to the EBS Volume (storage) tables.

Create each directory and mount the LVM on it in a serial manner, except /var/netwitness, which is already created.

After mounting the directory, add the following entries in /etc/fstab in the same order:

  1. /dev/logdecodersmall/decoroot /var/netwitness/logdecoder xfs noatime,nosuid 1 2
  2. /dev/logdecodersmall/index /var/netwitness/logdecoder/index xfs noatime,nosuid 1 2
  3. /dev/logdecodersmall/metadb /var/netwitness/logdecoder/metadb xfs noatime,nosuid 1 2
  4. /dev/logdecodersmall/sessiondb /var/netwitness/logdecoder/sessiondb xfs noatime,nosuid 1 2
  5. /dev/logdecoder/packetdb /var/netwitness/logdecoder/packetdb xfs noatime,nosuid 1 2

Concentrator

For an extension of /var/netwitness/ partition, attach an external disk and other external disks for the Concentrator database partitions.

Note: No other partition should reside on this Concentrator partition and should be used only for /var/netwitness/ partition.

Run lsblk to get the physical volume name.

If you attach 2 TB disk, run the following commands:

  1. pvcreate <pv_name> (for example, pv_name is dev/sdc)
  2. vgextend netwitness_vg00 /dev/sdc
  3. lvextend –L 1.9T /dev/netwitness_vg00/nwhome

Other Partition Required

The following partition should be on the volume group concentrator.

                            
Folder LVM Volume Group
/var/netwitness/concentratorroot concentrator
/var/netwitness/concentrator /sessiondbindex concentrator

/var/netwitness/concentrator /metadb

metadb

concentrator

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md0
  2. vgcreate –s 32 logdecodersmall /dev/md0
  3. lvcreate –L <disk_size> -n <lvm_name> logdecodersmall
  4. mkfs.xfs /dev/logdecodersmall/<lvm_name>
  5. Repeat the above steps all the LVMs mentioned

The following partition should be on volume group index.

                  
Folder LVM Volume Group
/var/netwitness/concentrator/indexindex index

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md1
  2. vgcreate –s 32 lindex /dev/md1
  3. lvcreate –L <disk_size> -n index index
  4. mkfs.xfs /dev/index/index

RSA recommends the following partition. However, you can change these values based on the retention days.

                                      
LVM Folder EBS
/dev/netwitness_vg00/nwhome /var/netwitness/Refer to the EBS Volume (storage) tables.
/dev/concentrator/decoroot /var/netwitness/concentratorRefer to the EBS Volume (storage) tables.
/dev/concentrator/metadb/var/netwitness/concentrator/metadbRefer to the EBS Volume (storage) tables.
/dev/concentrator/sessiondb /var/netwitness/concentrator/sessiondbRefer to the EBS Volume (storage) tables.
/dev/index/index /var/netwitness/concentrator/index Refer to the EBS Volume (storage) tables.

Create each directory and mount the LVM on it in a serial manner, except /var/netwitness, which is already created.

After mounting the directory, add the following entries in /etc/fstab in the same order:

  1. /dev/concentrator/root /var/netwitness/concentrator xfs noatime,nosuid 1 2
  2. /dev/concentrator/sessiondb /var/netwitness/concentrator/sessiondb xfs noatime,nosuid 1 2
  3. /dev/concentrator/metadb /var/netwitness/concentrator/metadb xfs noatime,nosuid 1 2 2
  4. /dev/index/index /var/netwitness/concentrator/index xfs noatime,nosuid 1 2

Archiver

For an extension of /var/netwitness/ partition, attach an external volume and other external disks for the Archiver database partitions.

Note: No other partition should reside on this Archiver partition and should be used only for /var/netwitness/partition.

Run lsblk to get the physical volume name.

If you attach 2 TB disk, run the following commands:

  1. pvcreate <pv_name> (for example, pv_name is dev/sdc)
  2. vgextend netwitness_vg00 /dev/sdc
  3. lvextend –L 1.9T /dev/netwitness_vg00/nwhome

Other Partition Required

The following partition should be on the volume group archiver.

                  
Folder LVM Volume Group
/var/netwitness/archiverarchiver archiver

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md0
  2. vgcreate –s 32 archiver /dev/md0
  3. lvcreate –L <disk_size> -n archiver archiver
  4. mkfs.xfs /dev/archiver/archiver

RSA recommends the following partition. However, you can change these values based on the retention days.

                       
LVM Folder  
/dev/netwitness_vg00/nwhome/var/netwitness/ 
/dev/archiver/archiver /var/netwitness/archiver  

Create each directory and mount the LVM on it in a serial manner, except /var/netwitness, which is already created.

After mounting the directory, add the following entries in /etc/fstab in the same order:

  1. /dev/archiver/archiver /var/netwitness/archiver xfs noatime,nosuid 1 2

Endpoint Hybrid or Endpoint Log Hybrid

For an extension of /var/netwitness/ partition, attach an additional volume,

and make sure that no other partition resides on this Endpoint Hybrid or Endpoint Log Hybrid. Also, attach

other additional volumes for the endpoint database partitions

Run lsblk to get the physical volume name.

If you attach 1 TB disk, run the following commands:

1. pvcreate <pv_name> (for example, pv_name is dev/sdc)

2. vgextend netwitness_vg00 /dev/sdc

3. lvextend –L 1T /dev/netwitness_vg00/nwhome

4. xfs_growfs /dev/netwitness_vg00/nwhome

Other Partition Required

The following partition should be on the volume group endpoint and should be in a single RAID 0 array.

                                 
Folder LVM Volume Group
/var/netwitness/mongo hybrid-mongoendpoint
/var/netwitness/concentrator concentrator-concroot

endpoint

/var/netwitness/concentrator/index

hybrid-concinde

endpoint

/var/netwitness/logdecoderhybrid-ldecroot endpoint

Run lsblk to get the physical volume name and run the following commands:

  1. pvcreate /dev/md0
  2. vgcreate –s 32 endpoint /dev/md0
  3. lvcreate –L <disk_size> -n <lvm_name> endpoint
  4. mkfs.xfs /dev/ endpoint /<lvm_name>
  5. Repeat the above steps for all the LVMs mentioned.

RSA recommends the following partition. However, you can change these values based on the retention

days.

                                      
LVM Folder EBS
/dev/netwitness_vg00/nwhome/var/netwitness/Refer to the EBS Volume (storage) tables.

/dev/endpoint/hybridmongo

/var/netwitness/mongoRefer to the EBS Volume (storage) tables.
/dev/endpoint/concentratorconcroot/var/netwitness/concentratorRefer to the EBS Volume (storage) tables.
/dev/endpoint/hybridconcinde/var/netwitness/concentrator/indexRefer to the EBS Volume (storage) tables.
/dev/endpoint/hybridldecroot/var/netwitness/logdecoder Refer to the EBS Volume (storage) tables.

Installation Tasks

Task 1 - Install 11.2.0.0 on the NetWitness Server (NW Server) Host

Note: You can perform this task for RSANW-11.2.0.0.1245-Full-01 instance.

    1. Run the nwsetup-tui command to set up the host.

    This initiates the Setup program and the EULA is displayed.

    Note: 1.) When you navigate through the Setup program prompts, use the down and up arrows to move among fields, use Tab key to move to and from commands (such as <Yes>, <No>, <OK>, and <Cancel>. Press Enter to register your command response and move to the next prompt.
    2.) The Setup program adopts the color scheme of the desktop or console you use access the host.
    3.) If you specify DNS servers during Setup program (nwsetup-tui) execution, they MUST be valid (valid in this context means valid during setup) and accessible for the nwsetup-tui to proceed. Any misconfigured DNS servers cause the Setup to fail. If you need to reach DNS server after setup that unreachable during setup, (for example, to relocate a host after setup that would have a different set of DNS Servers), see the "Post Installation Tasks" topic in the Physical Host Installation Guide.
    If you do not specify DNS Servers during setup (nwsetup-tui), you must select 1 The Local Repo (on the NW Server) in the NetWitness Platform Update Repository prompt in step 12 (the DNS servers are not defined so the system cannot access the external repo).

    1. Tab to Accept and press Enter.
      The Is this the host you want for your 11.2 NW Server prompt is displayed.
    2. Tab to Yes and press Enter.
      Choose No if you already installed 11.2 on the NW Server.

      Caution: If you choose the wrong host for the NW Server and complete the Setup, you must restart the Setup Program (step 2) and complete all the subsequent steps to correct this error.

      The Install or Upgrade prompt is displayed. (Recover does not apply to the installation. It is for 11.2 Disater Recovery.).

    3. Press Enter. Install (Fresh Install) is selected by default.
      The Host Name prompt is displayed.

      Caution: If you include "." in a host name, the host name must also include a valid domain name.

    4. Press Enter if want to keep this name. If not edit the host name, tab to OK, and press Enter to change it.
      The Master Password prompt is displayed.
      The following list of characters are supported for Master Password and Deployment Password:
      • Symbols : ! @ # % ^ + ,
      • Numbers :0-9
      • Lowercase Characters : a-z
      • Uppercase Characters : A-Z
        No ambiguous characters are supported for Master Password and Deployment Password (for example: space { } [ ] ( ) / \ ' " ` ~ ; : . < > -.

    5. Type in the Password, down arrow to Verify, retype the password, tab to OK, and press Enter.
      The Deployment Password prompt is displayed.

    6.  

      Type in the Password, down arrow to Verify, retype the password, tab to OK, and press Enter.
      If:

      • The Setup program finds a valid IP address for this host, the following prompt is displayed.
      • Press Enter if you want to use this IP and avoid changing your network settings. Tab to Yes and press Enter if you want to change the IP configuration found on the host.
      • If you are using an SSH connection, the following warning is displayed. Press Enter to close warning prompt.


      • Note: If you connect directly from the host console, the following warning will not be displayed.

        If the Setup Program found an IP configuration and you chose to use it, the Update Repository prompt is displayed. Go to step 10 to and complete the installation.
      • If the Setup Program did not find an IP configuration or if you chose to change the existing IP configuration, the Network Configuration prompt is displayed.

       
    7. Tab to OK and press Enter to use Static IP.
      If you want to use DHCP, down arrow to 2 Use DHCP and press Enter.
      The Network Configuration prompt is displayed.
    8. Down arrow to the network interface you want, tab to OK, and press Enter. If you do not want to continue, tab to Exit.
      The Static IP Configuration prompt is displayed.
    9. Type the configuration values (using the down arrow to move from field to field), tab to OK, and press Enter.
      If you do not complete all the required fields, an All fields are required error message is displayed (Primary DNS Server, Secondary DNS Server, and Local Domain Name fields are not required.)
      If you use the wrong syntax or character length for any of the fields, an Invalid field-name error message is displayed.

    Caution: If you select DNS Server, make sure that the DNS Server is correct and the host can access it before proceeding with the install.

    The Update Repository prompt is displayed.

    1. Apply the standard firewall configuration, press Enter.
      • Disable the standard configuration, tab to Yes and press Enter.
        The Disable firewall prompt is displayed.

        The disable firewall configuration confirmation prompt is displayed.
      • Tab to Yes and press Enter to confirm (press Enter to use standard firewall configuration).
    2. Press Enter to install 11.2 on the NW Server.
      The Start Install prompt is displayed.

      When Installation complete is displayed, you have installed the 11.2 NW Server on this host.

      Note: Ignore the hash code errors similar to the errors shown in the following screen shot that are displayed when you initiate the nwsetup-tui command. Yum does not use MD5 for any security operations so they do not affect the system security.

  • Task 2 - Install 11.2 on Other Component Hosts

    Note: You can perform this task for RSANW-11.2 1245-Lite-01 instance.

    1. Run the nwsetup-tui command to set up the host.

    This initiates the Setup program and the EULA is displayed.

    Note: 1.) When you navigate through the Setup program prompts, use the down and up arrows to move among fields, use Tab key to move to and from commands (such as <Yes>, <No>, <OK>, and <Cancel>. Press Enter to register your command response and move to the next prompt.
    2.) The Setup program adopts the color scheme of the desktop or console you use access the host.
    3.) If you specify DNS servers during Setup program (nwsetup-tui) execution, they MUST be valid (valid in this context means valid during setup) and accessible for the nwsetup-tui to proceed. Any misconfigured DNS servers cause the Setup to fail. If you need to reach DNS server after setup that unreachable during setup, (for example, to relocate a host after setup that would have a different set of DNS Servers), see the "Post Installation Tasks" topic in the Physical Host Installation Guide..
    If you do not specify DNS Servers during setup (nwsetup-tui), you must select 1 The Local Repo (on the NW Server) in the NetWitness Platform Update Repository prompt in step 12 (the DNS servers are not defined so the system cannot access the external repo).

    1. Tab to Accept and press Enter.
      The Is this the host you want for your 11.2 NW Server prompt is displayed.

      Caution: If you choose the wrong host for the NW Server and complete the Setup, you must restart the Setup Program (step 2) and complete all the subsequent steps to correct this error.

    2. Press Enter(No).
    3. Press Enter. Install (Fresh Install) is selected by default.
      The Host Name prompt is displayed.

      Caution: If you include "." in a host name, the host name must also include a valid domain name.

    1. If want to keep this name, press Enter. If you want to change this name, edit it, tab to OK, and press Enter.

      The Deployment Password prompt is displayed.

    1. Type in the Password, down arrow to Verify, retype the password, tab to OK, and press Enter.
      • If the Setup program finds a valid IP address for this host, the following prompt is displayed.
      • Press Enter if you want to use this IP and avoid changing your network settings.
      • Tab to Yes and press Enter if you want to change the IP configuration found on the host.
        If you are using an SSH connection, the following warning is displayed. Press Enter to close warning prompt.

        The Setup Program found an IP configuration and you chose to use it, the Update Repository prompt is displayed. Go to step 10 to and complete the installation.
    2. The Setup Program did not find an IP configuration or if you chose to change the existing IP configuration, the Network Configuration prompt is displayed.

    3. Tab to OK and press Enter to use Static IP.
      If you want to use DHCP, down arrow to 2 Use DHCP and press Enter.
      The Network Configuration prompt is displayed.

    4. Down arrow to the network interface you want, tab to OK, and press Enter. If you do not want to continue, tab to Exit.
      The Static IP Configuration prompt is displayed.

    5. Type the configuration values (using the down arrow to move from field to field), tab to OK, and press Enter.
      If you do not complete all the required fields, an All fields are required error message is displayed (Primary DNS Server, Secondary DNS Server, and Local Domain Name fields are not required.)
      If you use the wrong syntax or character length for any of the fields, an Invalid field-name error message is displayed.

      Caution: If you select DNS Server, make sure that the DNS Server is correct and the host can access it before proceeding with the install.

    6. The Update Repository prompt is displayed. Press Enter to choose the Local Repo on the NW Server.

    7. To:
      • Apply the standard firewall configuration, press Enter.
      • Disable the standard configuration, tab to Yes and press Enter.
        The Disable firewall prompt is displayed.

        The disable firewall configuration confirmation prompt is displayed.
      • Tab to Yes and press Enter to confirm (press Enter to use standard firewall configuration).
    8. The Start Install prompt is displayed.

    9. Press Enter to install 11.2 on the NW Server.
      When Installation Complete is displayed, you have installed the 11.2 NW Server on this host.

      Note: Ignore the hash code errors similar to the errors shown in the following screen shot that are displayed when you initiate the nwsetup-tui command. Yum does not use MD5 for any security operations so they do not affect the system security.

    You are here
    Table of Contents > AWS Deployment > Step 3.  Launch an Instance and Configure a Host

    Attachments

      Outcomes