AWS Marketplace Quick Launch configuration capabilities
Hi, related to the Quick Launch configuration
- Are there any limitation o restrictions that the partner should be aware when defining the CloudFormation template?
- Can be used to provision the required resources in multiple customer accounts? and not only in the account used to buy the SaaS product?
- トピック
- AWS Marketplace
- 言語
- English
- 新しい順
- 投票が多い順
- コメントが多い順
Regarding AWS Marketplace Quick Launch configuration capabilities:
- There are some considerations and potential limitations that partners should be aware of when defining CloudFormation templates for Quick Launch:
-
It's recommended to minimize the number of templates associated with the configuration process. Ideally, you should aim for one template that deploys all the necessary resources for using the product. This simplifies the launch process for customers.
-
The CloudFormation templates need to adhere to AWS security best practices and include the minimum resources required for the SaaS product to operate on AWS.
-
Partners should work closely with their AWS Marketplace business development partner or the AWS Marketplace Seller Operations team for any questions or guidance related to their CloudFormation template.
- As for provisioning resources in multiple customer accounts:
The Quick Launch feature is primarily designed to deploy resources in the customer's AWS account that is used to subscribe to the SaaS product. The documentation doesn't explicitly mention the ability to provision resources across multiple customer accounts.
Quick Launch uses an integrated AWS CloudFormation stack creation to deploy resources in the customer's account. It's focused on simplifying the onboarding experience for customers by deploying necessary AWS resources like IAM roles, databases, or agents in the account used for subscription.
If your SaaS product requires resources to be deployed across multiple accounts, you may need to handle that aspect separately from the initial Quick Launch process. You might consider providing additional guidance or automation for customers who need to extend the deployment to other accounts after the initial Quick Launch setup.
It's always best to consult directly with your AWS Marketplace representative for specific requirements or advanced scenarios that may not be covered in the general documentation.
Sources
Choosing the right fulfillment option for your SaaS product in AWS Marketplace | AWS Marketplace
Configuring SaaS product settings in AWS Marketplace - AWS Marketplace
