Versions Compared

Old Version 21

changes.mady.by.user Jyothi KP

Saved on

compared with

New Version 22

changes.mady.by.user Shwetha S

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This topic describes the procedure that you can use to launch and provision an Infoblox vNIOS for AWS instance for your AWS VPC in the AWS console. This procedure supports users who want to provision Infoblox vNIOS for AWS using the BYOL (Bring Your Own Licensing) model. It provides the complete sequence of procedures that you must perform to manually provision a new Infoblox vNIOS for AWS instance in AWS.

...

  1. On the Launch an instance page, expand Application and OS Images (Amazon Machine Image) and click Browse more AMIs.

  2. On the Choose an Amazon Machine Image (AMI) page, click the AWS Marketplace AMIs tab.

  3. Search for the AMI by entering the strings NIOS or Infoblox in the search box. The Infoblox AMI listing appears in the search results.

  4. In the appropriate vNIOS for AWS AMI row, click Select.

  5. Expand Instance type, and select an appropriate shape from the Instance type drop-down list. See Infoblox vNIOS for AWS AMI Shapes and Regions for the available options.

  6. Expand Key pair (login) and configure a key pair to securely connect to your instance. When you configure a key pair in AWS, the public key will be uploaded to NIOS.
    Note that the Infoblox standard configuration for vNIOS for AWS deployment requires use of a VPN connection or a direct connection to the Amazon VPC(s) on which you are deploying and operating vNIOS for AWS instances. This connection does not require an Internet-connected IP address or a secure key pair. All AWS Proxy API operations require use of an assigned and regularly rotated AWS-generated key pair assigned to the cloud-api-only account in Grid Manager. For information, see Assigning AWS User Credentials to the NIOS Cloud Admin Accountsee Assigning AWS User Credentials to the NIOS Cloud Admin Account.
    Do one of the following:

    • In the Key pair name drop-down list, choose an existing key pair.

    • Click Create new key pair and complete the following in the Create key pair window:

      1. Key pair-name: Enter a name for the key pair.

      2. Key pair type: Select the required type.

      3. Private key file format: Select the format to use for the private key.

      4. Click Create key pair.

    • (Not recommended) If you want to perform a simple deployment, proceed without configuring a key pair.

  7. Proceed to configure the network settings as defined in the Defining Network Settings for the vNIOS for AWS Instance section.

...

Infoblox vNIOS virtual appliances require two network interfaces (MGMT and LAN1) for proper Grid communications. These interfaces must be assigned to separate subnets within the same VPC.
Note that the NIOS GUI communicates through the MGMT port. If for any reason you must make changes to the MGMT port, such as swapping NICs or changing the MGMT IP address from static to dynamic, ensure that you use the same IP address for the MGMT port before and after the changes. Otherwise, you might not be able to access the NIOS GUI.

...

  1. Expand Advanced Details and scroll down to the User data field.

    When you start the vNIOS for AWS instance, to access the NIOS GUI, you must install the vNIOS license by setting the value "temp_license:vnios" in the User data settings. You can also use the NIOS CLI to set temporary or permanent licenses.

  2. IDefine Define the following plain-text values in the User data field:

    1. remote_console_enabled: Enables or disables the remote SSH CLI console for a new instance (syntax: y or n).

    2. default_admin_password: Sets the password for the NIOS admin user during the first boot. This value does not have to be a default; it can be the password of any administrator who initializes the new instance. The minimum password length is four characters. If an invalid password is passed by this method, it will be ignored, and the default "infoblox" password remains in effect for the instance. Note that if you want to include a symbol character at the beginning of the password, ensure that you put the password in quotes ('') to avoid login issues. Example: '!Infoblox'.

      • In NIOS 8.5.2 or later, for a Grid Master or a standalone vNIOS for AWS instance, the default NIOS password must be reset on the first login in the NIOS UI. Otherwise, you can configure the new password in the User data field and log in to the NIOS UI using that password. The minimum password length is four characters. It must consist of at least one uppercase character, one lowercase character, one numeric character, and one symbol character. Example: Infoblox1!
        Consider the following points for defining a password:

        • If the symbol character is at the beginning of the password, then include the password within quotes (''). Example: '@Infoblox123'.

        • If you enter an invalid password, you will be prompted to reset the password in the NIOS UI on the first login.

        • The password that you set for the Grid Master is propagated to all its members.

      • To access the NIOS CLI, you must either use the key pair or key pair + password authentication that is configured in NIOS, because access to the CLI by using only the NIOS UI password is blocked.

    3. temp_license: Defines the NIOS feature licenses for the new instance. You can list a collection of temporary license names that apply to the instance during the initial boot. Using this directive allows you to quickly provision the new instance with temporary licenses without having to open a NIOS CLI session to do the same task. To access the NIOS GUI, you must provision the vNIOS license before you start the vNIOS instance. Infoblox recommends that you also provision the Grid and cloud licenses at the same time as follows: temp_license:grid cloud vnios. All text entries must be in all lower case.
      - When you use temp_license in the User data field to install a NIOS license, the Use AWS SSH authentication key option, is enabled by default.
      - For a IB-V4025 appliance, if you use the User data field to install the IB-V4025 license, the Use AWS SSH authentication key option will not be enabled by default. Therefore, Infoblox recommends that you first deploy the vNIOS instance without specifying the IB-V4025 license, and then install the license from the NIOS CLI.
      Valid license names include the following:

      • Infoblox vNIOS for AWS instances (IB-V825, IB-V1425 and IB-V2225):

        • grid

        • dns

        • enterprise

        • cloud

      • NIOS license for DDI (IB-V825, IB-V1425 and IB-V2225):

        • nios IB-Vxxxx
          where "xxxx" is the license number.

      • Cloud Platform Infoblox vNIOS for AWS instances (CP-V805, CP-V1405 and CP-V2205):

        • grid

        • dns

        • enterprise

        • cloud_api

Note

Note

  • When you use temp_license in the User data field to install a NIOS license, the Use AWS SSH authentication key option that is needed to enable the CLI access to AWS instances, is enabled by default. For more information see Creating Local Admins in the Infoblox NIOS Documentation. However, for the IB-V4025 appliances, the Use AWS SSH authentication key option is not enabled with this user data configuration. Therefore, Infoblox recommends that you install the IB-V4025 license after deploying the vNIOS instance.

  • Only In NIOS versions prior to 9.0.1, only the V1 and V2 (token optional) value is supported in the Metadata version field. The Starting from NIOS 9.0.1, the values of both V1 and V2 (token optional) and V2 (token required) value is not supported are supported.

  • For more information about licensing in NIOS 9.0.1, refer to the topic Managing Licenses in NIOS 9.0.1 in the Infoblox NIOS Documentation.

The following figure shows an example:
Defining User Data Settings for Provisioning an Instance without Elastic Scaling

...