Launching a single ONTAP Cloud instance in AWS

If you want to launch an ONTAP Cloud instance in AWS, you need to create an ONTAP Cloud working environment in Cloud Manager.

Before you begin

About this task

Immediately after you create the working environment, Cloud Manager launches a test instance in the specified VPC to verify connectivity. If successful, Cloud Manager immediately terminates the instance and then starts deploying the ONTAP Cloud system. If Cloud Manager cannot verify connectivity, creation of the working environment fails. The test instance is either a t2.nano (for default VPC tenancy) or m3.medium (for dedicated VPC tenancy).

Steps

  1. On the Working Environments page, click Add environment.
  2. Under Create, select ONTAP Cloud.
  3. On the Details and Credentials page, enter a name for the working environment, add AWS tags if needed, enter a password, and then click Continue.
    Some of the fields in this page are self-explanatory. The following table describes fields for which you might need guidance:
    Field Description
    Credentials These are the credentials for the ONTAP Cloud cluster admin account. You can use these credentials to connect to ONTAP Cloud through OnCommand System Manager or its CLI.
    Name Cloud Manager uses the working environment name to name both the ONTAP Cloud system and the Amazon EC2 instance. It also uses the name as the prefix for the predefined security group, if you select that option.
    AWS tags AWS tags are metadata for your AWS resources. Cloud Manager adds the tags to the ONTAP Cloud instance and each AWS resource associated with the instance.

    AWS Documentation: Tagging your Amazon EC2 Resources

    Note: If AWS keys were not specified for your Cloud Manager account, you are prompted to enter them after you click Continue. You need to enter them before you can proceed.
  4. On the VPC page, enter the network information that you recorded in the AWS worksheet, select the checkbox to confirm network connectivity, and then click Continue.
    The following image shows the VPC page filled out:

    Screen shot: Shows the VPC page filled out for a new Cloud ONTAP instance.

  5. On the Data Security page, choose no data encryption, ONTAP Cloud-managed encryption, or AWS-managed encryption.
    For AWS-managed encryption, you can choose a different master key if more than one key is available in your account.
    Note: If Cloud Manager was not set up for encryption, the Cloud Manager Admin must set it up.

    Setting up Cloud Manager for ONTAP Cloud encryption in AWS

  6. If you chose ONTAP Cloud encryption, select one to four key managers, select the certificate of the CA that signed the server certificate for each key manager, and then click Continue.
    Note: The key manager CA certificate is for all selected key managers, which means the same certificate authority (CA) must have signed the server certificate for each key manager.
  7. On the Licensing page, change the ONTAP Cloud version as needed, select a license, an instance type, the instance tenancy, and then click Continue.
    If your needs change after you launch the instance, you can modify the license or instance type later. See Changing the configuration of ONTAP Cloud instances.
  8. If the NetApp Support Site credentials page is displayed, enter your NetApp Support Site credentials.
    Credentials are required for BYOL instances.
  9. On the ONTAP Cloud Settings page, select the underlying AWS disk type and size, and the write speed:
    Field Description
    Underlying AWS Disk For guidance on choosing a disk type, see Choosing a disk type.

    For guidance on choosing a disk size, see Choosing disk size.

    Note the following:

    • The underlying AWS disk type is for the initial volume. You can choose a different disk type for subsequent volumes.
    • The disk size is the default size for all disks in the initial aggregate and for any additional aggregates that Cloud Manager creates when you use the simple provisioning option.
    • You can create aggregates that use a different disk size by using the advanced allocation option.
    Write Speed For guidance on choosing a write speed, see Choosing a write speed.
  10. On the Create Volume page, enter details for the new volume, and then click Continue.
    You might skip this step if you want to create a volume for iSCSI. Cloud Manager sets up volumes for NFS and CIFS only.
    Some of the fields in this page are self-explanatory. The following table describes fields for which you might need guidance:
    Field Description

    Size

    The maximum size that you can enter largely depends on whether you enable thin provisioning, which enables you to create a volume that is bigger than the physical storage currently available to it.

    Access control (for NFS only)

    An export policy defines the clients in the subnet that can access the volume. By default, Cloud Manager enters a value that provides access to all instances in the subnet.

    Permissions and Users / Groups (for CIFS only)

    These fields enable you to control the level of access to a share for users and groups (also called access control lists or ACLs). You can specify local or domain Windows users or groups, or UNIX users or groups. If you specify a domain Windows user name, you must include the user's domain using the format domain\username.

    Usage Profile

    Usage profiles define the NetApp storage efficiency features that are enabled for a volume.

    For more information, see Understanding volume usage profiles.

    Protection

    A Snapshot copy policy specifies the frequency and number of automatically created NetApp Snapshot copies. A NetApp Snapshot copy is a point-in-time file system image that has no performance impact and requires minimal storage. You can choose the default policy or none. You might choose none for transient data: for example, tempdb for Microsoft SQL Server.

    The following image shows the Volume page filled out for the CIFS protocol:

    Screen shot: Shows the Volume page filled out for a Cloud ONTAP instance.

  11. If you chose the CIFS protocol, set up a CIFS server on the ONTAP Cloud CIFS Setup page:
    Field Description
    DNS Primary and Secondary IP Address The IP addresses of the DNS servers that provide name resolution for the CIFS server.

    The listed DNS servers must contain the service location records (SRV) needed to locate the Active Directory LDAP servers and domain controllers for the domain that the CIFS server will join.

    Active Directory Domain to join The FQDN of the Active Directory (AD) domain that you want the CIFS server to join.
    Credentials authorized to join the domain The name and password of a Windows account with sufficient privileges to add computers to the specified Organizational Unit (OU) within the AD domain.
    CIFS server NetBIOS name A CIFS server name that is unique in the AD domain.
    Organizational Unit The organizational unit within the AD domain to associate with the CIFS server. The default is CN=Computers.
    DNS Domain The DNS domain for the ONTAP Cloud Storage Virtual Machine (SVM). In most cases, the domain is the same as the AD domain.
  12. On the Review & Approve page, review and confirm your selections:
    1. Review details about the configuration.
    2. Click More information to review details about support and the AWS resources that Cloud Manager will purchase.
    3. Select the I understand... check boxes.
    4. Click Go.

Result

Cloud Manager launches the ONTAP Cloud instance. The working environment should be ready in approximately 25 minutes. You can track the progress in the timeline.

If you experience any issues launching the ONTAP Cloud instance, review the failure message. You can also select the working environment and click Re-create environment.

For additional help, go to NetApp ONTAP Cloud Support.

After you finish