AWS Marketplace Prerequisites and Requirements for Container Products

In this article, you will find the key points to consider to ensure your Container Product meets AWS Marketplace listing requirements.

Launching your container product on AWS Marketplace can unlock numerous opportunities. By adhering to these guidelines and carefully planning your integration, you can position yourself for success in the competitive world of cloud-based container services. So, what are you waiting for? Dive in and start building your presence on AWS Marketplace today!

✅  Prerequisites

Before you can list your Container product on AWS Marketplace, complete the following steps:

1. Access the AWS Marketplace Management Portal: This portal is your main tool for registering as a seller and managing your products. Refer to AWS Marketplace Management Portal for more information.
2. Register as a Seller: Submit your tax and banking information through the seller registration process. Details are available in the Seller Registration Process.
3. Create a Container: Use Amazon ECS, Amazon EKS, or AWS Fargate to create at least one container. Ensure you have links for the associated images.
4. Plan Integration: Plan how you'll create and integrate your container product in AWS Marketplace, including pricing, entitlement, and metering strategies. Continue reading for more details, or visit Container-based Product Requirements for the full list of AWS Marketplace requirements.

🗃️  Creating a Container Product

Follow these steps to create your container product:

1. Create the Product ID and Code: Start by generating a unique product ID and code.
   
2. Initial Listing: Create an initial listing of your product.
   
3. Add Initial Version: Upload the initial version of your product.
   
4. Integrate Metering: For paid products, ensure metering is integrated.
   
5. Update Visibility: Adjust product visibility settings as needed.
   

📋  Container Product Requirements

AWS Marketplace maintains strict requirements to ensure security and reliability:

➡️  Security Requirements

• Malware-Free: Docker container images must be free from known malware, viruses, or vulnerabilities. New versions are scanned upon submission.
  
• IAM Roles: Access to manage AWS resources must be through IAM roles, not user access keys. Use IAM roles for service accounts (Amazon EKS) or IAM roles for tasks (Amazon ECS).
  
• Least Privilege Principle: Container-based products should only require minimal privileges to run. Refer to ECS Security and EKS Security.
  
• Non-Root Privileges: Containers should be configured to run with non-root privileges by default.

➡️  Access Requirements

• Randomized Initial Passwords: Use initial randomized passwords, not fixed or blank passwords, for administrative access.
  
• Explicit External Access: Customers must explicitly agree to and enable any external access to the application.
  

➡️  Customer Information Requirements

• Data Collection Transparency: Software must not collect or export customer data without explicit consent. If data collection is necessary, clearly state what data is collected, where it will be stored, and how it will be used in the product description.
  
• No Payment Information Collection: Payment information must not be collected.
  

➡️  Product Usage Requirements

• Fully Functioning Products: Only list fully functional products. Beta or prerelease products for evaluation are not allowed. Developer, community, and BYOL editions are supported if a paid version is available within 90 days.
  
• Comprehensive Usage Instructions: Provide complete deployment instructions, including all steps and commands necessary for using the container images on AWS Marketplace.
  
• Self-Service Deployment: Ensure that containers and their software are deployable in a self-service manner without additional payment methods or costs.
  
• External Dependencies: Any requirement for external dependencies must be disclosed in the product description. Ensure the availability and security of these dependencies.
  
• Avoid Redirection: Do not include language that redirects users to other platforms, products, or services outside AWS Marketplace.
  

➡️  Architecture Requirements

• Amazon ECR Repository: Source container images must be pushed to Amazon ECR repositories managed by AWS Marketplace.
  
• Linux-Based Images: Container images must be based on Linux.
  
• Deployment on AWS Services: Paid products must be deployable on Amazon ECS, Amazon EKS, or AWS Fargate. Products with contract pricing and AWS License Manager integration can deploy on various platforms, including Amazon ECS Anywhere and Red Hat OpenShift Service on AWS.
  

➡️  Product Visibility and Compatibility

• EKS Add-On Requirements: To publish as an AWS Marketplace add-on, your product must be compatible with AMD64 and ARM64 architectures and must not use the BYOL model. Ensure all images and Helm charts are in AWS Marketplace-managed Amazon ECR repositories. Follow guidelines for creating a Helm chart and the required configurations.