Subscribe and deploy Cloud Volumes ONTAP standalone offering from AWS Marketplace
Subscribe to the standalone Cloud Volumes ONTAP offering in AWS Marketplace, deploy a Console agent, and create your first system.
Before you begin, make sure you have:
-
A NetApp Console account, or the information needed to create one.
-
Ensured that the Console agent network meets the requirements. Learn about Console agent networking requirements
-
An AWS account and identity with permission to subscribe to AWS Marketplace and accept the offering terms.
If you choose Create role for me, the AWS identity that submits the CloudFormation Quick Create stack needs the permissions below. To use the same identity for subscribing and submitting the stack, attach these permissions before starting. If you use a different identity to submit the stack, attach them to that identity instead. These permissions let CloudFormation create the deployment role; they are not the permissions used by the running agent.
Minimum permissions for CloudFormation Quick Create{ "Version": "2012-10-17", "Statement": [ { "Sid": "CloudFormationStack", "Effect": "Allow", "Action": [ "cloudformation:CreateStack", "cloudformation:DeleteStack", "cloudformation:DescribeStacks", "cloudformation:DescribeStackEvents", "cloudformation:GetTemplateSummary", "iam:CreateRole", "iam:DeleteRole", "iam:GetRole", "iam:PutRolePolicy", "iam:DeleteRolePolicy", "iam:GetRolePolicy", "iam:PassRole", "lambda:CreateFunction", "lambda:DeleteFunction", "lambda:GetFunction", "lambda:InvokeFunction" ] } ] }
Subscribe to the standalone Cloud Volumes ONTAP offering in AWS Marketplace
Locate the standalone Cloud Volumes ONTAP offering in AWS Marketplace.
-
Go to AWS Marketplace using your AWS account with the required permissions.
-
Locate the NetApp Cloud Volumes ONTAP standalone offering. AWS Marketplace provides two offerings for Cloud Volumes ONTAP:
-
The standalone offering for Cloud Volumes ONTAP annual subscription
-
The NetApp Intelligent Service combined offering for NetApp data services and Cloud Volumes ONTAP subscriptions.
-
-
Choose the standalone offering. These steps guide you through subscribing to the standalone offering.
-
Review listing details and pricing terms.
-
Subscribe and complete the checkout.
-
After you subscribe, select Set up product to be redirected to the NetApp Console to complete your deployment.
Sign up or sign in to NetApp Console
Continue setup in NetApp Console after you complete the Marketplace subscription.
-
On the Console page, select one:
-
Sign up if you are a new user.
-
Sign in to NetApp Console if you already have an account.
-
-
If you select Sign up, complete the following:
-
Enter the required fields.
-
Select Next.
-
Optional: Enter contact details such as address, city, state, postal code, and phone number.
-
Select Sign up.
-
Accept the license terms.
-
Verify your email address using the message from service@console.netapp.com.
-
-
Sign in to the Console and complete authentication.
Create your organization
Create an organization only if you are a first-time user or do not already belong to one. If you already belong to an organization, skip this section and continue to Deploy a Console agent in AWS.
An organization helps you manage users, roles, permissions, licenses, and systems.
-
Enter an organization name.
-
Optional: associate a NetApp Support Site (NSS) account.
-
Select Create.
Deploy a Console agent in AWS
After your subscription is associated with NetApp Console, deploy a Console agent to manage AWS resources and Cloud Volumes ONTAP systems.
Review the AWS authorization and networking requirements before you deploy the agent.
-
Decide how to authorize the Console to deploy the agent.
-
For Create role for me, the AWS identity that submits the CloudFormation Quick Create stack needs AWS administrator permissions or the minimum permissions in the JSON example above.
-
For Assume role or AWS keys, see AWS permissions for deploying an agent.
-
-
Set up networking according to the Console agent networking requirements.
-
On the Welcome page, select Resume setup.
The Console tries to associate your marketplace subscription with your organization. If automatic association fails, manually associate your subscription. Learn how to manage subscriptions.
After your subscription is associated, the Console directs you to deploy a Console agent.
-
Choose how to authorize the Console to deploy the agent:
The deployment credentials authorize the Console to deploy the agent. The running agent uses a separate IAM role attached to its EC2 instance. The Console can create that role or use an existing role with the required permissions. See AWS permissions for the Console agent.
-
Select Create role for me to have CloudFormation create a role that the Console can assume.
-
Select Assume role and provide the ARN of an existing IAM role whose trust policy allows the Console to assume it and that has the required deployment permissions.
-
Select AWS keys and provide access keys for an IAM user with the required deployment permissions.
Create role for me (recommended)To have the Console create the role with CloudFormation Quick Create, the AWS identity that submits the stack needs administrator permissions or the minimum permissions in the JSON example above.
-
Select Create role for me.
-
Add the AWS account ID and optionally, the external ID. The Console sets a default role name.
-
Select Open CloudFormation Quick Create.
-
Within the AWS CloudFormation Quick Create page, acknowledge the terms and select Create stack.

-
When AWS configures the IAM role and generates the ARN, confirm and save the role.
Assume roleIf you already have a role with the required AWS permissions, provide its ARN so the Console can assume it to deploy the agent. Learn about creating a role.
-
Select Assume role.
Console creates a name for the assumed role that you can change if you want.
-
Enter the ARN of the existing role.
-
Select Validate credentials.
AWS keysIf you want to use access keys to authorize agent deployment, provide your AWS access key and secret key. Learn about creating a role for a user.
-
Select AWS keys.
-
Enter the access key and secret for the role you want to use.
-
Select Validate credentials.
-
-
-
Configure the agent deployment details, including the agent instance name and whether the Console should create the IAM role for the running agent or use an existing role.
When the Console creates the Console agent, it creates an IAM role and a profile for the agent or uses a role that you provide. This role includes permissions that enable the agent to manage AWS resources. Ensure the role is updated as new permissions are added in future releases. Learn more about the IAM policy for the Console agent.
-
Configure networking by selecting a VPC, subnet, key pair, public IP behavior, and proxy settings, if needed.
-
Configure your security group rules to allow inbound HTTP (80), HTTPS (443), and SSH (22) for troubleshooting access to the agent VM.
-
Review the section summaries and select Add to deploy the Console agent.
Track the deployment progress until it completes. You can expand the event logs to review detailed activity.
For full networking and permissions requirements for the Console agent, see:
Add your first Cloud Volumes ONTAP system
After the Console deploys the agent, follow the steps in Deploy Cloud Volumes ONTAP with Quick create in AWS to create your first system.
If you aren't ready to create your Cloud Volumes ONTAP system, you can return to the Systems page at any time to create your system later.
Troubleshooting and recovery
Resume onboarding where you left off or retry agent deployment after a failure.
Resume setup
If you leave before onboarding is complete, continue from the last completed step.
-
Go to the NetApp Console home page.
-
Select Resume setup to continue onboarding.
Recover from deployment failure
If the Console can't deploy the agent, use these steps to retry:
-
Download the deployment report.
-
Review your configuration and logs.
-
Select Start over to retry the deployment.
For help with agent deployment, AWS subscriptions, or Cloud Volumes ONTAP tasks, see: