Qumulo, the leader in data storage for hybrid cloud data management that runs anywhere at any scale, is proud to announce integration with AWS IAM Temporary Delegation. Integration with this new IAM feature removes key friction points for customers by enabling them to streamline deployments of their Cloud Native Qumulo storage solutions on AWS. This integration reduces deployment setup steps, saves time, ensures accuracy/consistency, and removes access concerns. It also makes running a Proof of Concept much easier for those who would like to try the solution before buying.
When customers purchase Cloud Native Qumulo on the AWS Marketplace, they can now immediately deploy and start using the solution with less effort and complication. Previously, buyers had to follow a detailed workflow to delegate a long-lived IAM role to Qumulo’s control plane service, which involved moving between the AWS Marketplace purchase experience, into Qumulo’s management and reporting application: Nexus, then back into the AWS Console to deploy CloudFormation stacks, back to the marketplace, and then finally back into Nexus.. They also had to request/verify access level and privileges to purchase Cloud Native Qumulo, create new IAM roles, and add new clusters to their Nexus organization. Oftentimes, customers would get stuck in the process and end up having to reach out to Qumulo support. It was a less-than-ideal solution for deployment.
AWS IAM Temporary Delegation now enables customers to temporarily delegate a subset of their IAM permissions to Qumulo Nexus with a single click, allowing it to perform one-time infrastructure deployment tasks within their AWS accounts. In the updated deployment process, the customer initiates the deployment in the AWS Marketplace and is presented with a dialogue box. Acceptance via this dialogue box enables them to quickly grant the Qumulo installation process limited access to their AWS account, facilitating the deployment of necessary compute, storage, and other services.
Once a few short questions are answered, Qumulo Nexus deploys the required EC2 instances, S3 buckets, as well as other supporting infrastructure, such as security groups, CloudWatch metrics, and SSM configurations, into the VPC and subnets of the customer’s choice, running the Cloud Native Qumulo software solution on top of it. This process is fully automated, requiring no intervention from the customer or Qumulo support. When the installation process is complete, the new storage solution is ready to use.
Please note that this is temporary (with a limited duration to complete the process) and one-time access. Customers can review the access policy before granting access. With this new Temporary Delegation feature, customers can rest assured that their AWS account remains secure after the deployment is complete and the temporary access has expired.
Note that Cloud Native Qumulo requires running EC2 instances with attached EBS volumes inside the customer’s account, and data stored on Cloud Native Qumulo will consume S3 object storage. As such, upon deployment, customers will begin being billed for all AWS infrastructure consumed until they choose to tear down any deployed clusters. Use of the Cloud Native Qumulo platform is metered via the AWS Marketplace. It will appear as a separate line item on the customer’s AWS bill after completion of any proof-of-concept period, if applicable.
The AWS IAM Temporary Delegation feature provides a smoother, more straightforward, and lower-friction deployment experience for customers. It allows Qumulo to offer a product that does not require a specialist cloud team to help customers deploy, opening the door for organic discovery and growth inside the AWS Marketplace.
This feature is critical for any ISV deploying a SaaS product that needs to perform tasks within the customer’s AWS account to complete the deployment.
