Setting Up NetApp Data Availability Services with the Launch Portal Edit on GitHub Request doc changes

Contributors netapp-forry netapp-aherbin

The Launch Portal provides a simple way for you to deploy NetApp Data Availability Services (NDAS).

Before you begin

You must have completed the following tasks:

  • Verified ONTAP cluster and SnapMirror requirements

  • Verified networking requirements

  • Verified AWS requirements and completed the configuration worksheet

  • Visited the NDAS product page and selected 90-Day Free Evaluation to register for the free trial

Chrome and Firefox are the supported browsers for using the NDAS Launch Portal.

Steps
  1. Navigate to the Launch Portal URL that you received during the registration process.
    You see a series of NDAS setup screens.

  2. In the AWS Credentials screen, enter your values:

    • AWS Access ID

    • AWS Secret Key
      Check the box for the End User License Agreement and click Continue.

  3. In the Instance Setup screen, select the values that you collected in the configuration worksheet for the following fields.
    Note: Choose the correct value for deployment as per your worksheet. The launch portal filters for eligible VPCs and subnets based on the AWS region.

    • Region

    • VPC

      The Launch Portal only displays VPCs in the region you selected.
      If more than one VPC is displayed, you must select which to use for this NetApp Data Availability Services instance.

    • Subnet #1 and Availability Zone
      Subnets in the VPC selected that meet the criteria are displayed.

    • Subnet #2 and Availability Zone
      Once Subnet #1 is selected, choices displayed for subnet #2 do not include those in Availability Zone #1.

    • Key Pair

    • Configuration
      Select Small (10 TB), Medium (50 TB), or Medium (200 TB).

    • Certificate ARN (optional)

  4. In the Security Group screen, select an existing Security Group from your worksheet (recommended) or optionally create a new one.
    Only security groups that allow HTTP, HTTPS, and SSH protocols are shown.

    Click Launch Instances to continue.

  5. When the Deploying NDAS screen appears, be sure to keep it open until you are automatically redirected to the Launcher screens.

  6. When you see the warning about the self signed certificate, click Continue.
    The web address then changes to the IP address of the NDAS EC2 instance and you see a message for each deployment task as it completes.

    If a task fails, double-click the failure message to see more information about the cause. After correcting the error you can re-execute the launch sequence.

  7. When you see the Success message, click the link to log into the NDAS app.
    This is the URL that the NDAS app administrator will use to manage data protection workflows. You should bookmark this URL so you can connect to the app later.

  8. When the login dialog appears, click the Sign Up link.
    Enter your registration values:

    1. Username – This will be used by app administrator.

    2. Email address

    3. Password – The password must comply with the policy displayed during password entry.
      Be sure to save the password in a secure place.

  9. Click on Save, a green banner displaying Administrator added Successfully should be displayed at the top of Sign Up page.

  10. If you are not automatically returned to the NetApp Data Availability Services login page, click the NetApp Data Availability Services logo

  11. Verify access by entering your username and password and click on Sign In.
    The NDAS app displays the Dashboard window.

This completes the NetApp Data Availability Services deployment. After activating support entitlement, you can provide the NDAS app URL to the app administrator, who can then create data protection workflows.

Note: AWS resources created by NDAS configuration — such EC2, SQS, and Load Balancer — are visible using standard AWS tools and can be identified by tags of either “NDAS” or “CRO”. Backup objects in the S3 bucket can also be browsed. Nonetheless, you should only use the NDAS app to manage these objects. Do not delete any backup objects or resources created by NetApp Data Availability Services outside of the app itself.