FAQs - AWS Marketplace Container Listing

This FAQ covers common questions about container products on AWS Marketplace. For detailed technical requirements, see AWS Marketplace: Container-Based Product Requirements.

Table of Contents

• Container Repositories
   
• Publishing & Product Configuration
   
• Delivery Options & Helm Charts
   
• PRM & Partner Requirements
   
• Deployment Architecture & Customer Environment
   
• Security & Compliance

Container Repositories

Can I use multiple container images in the same repository?

Yes. Multiple container images or artifacts can be stored in the same Amazon ECR repository using different tags.

For example:

optura_platform:intent-v2.9.0optura_platform:ontology-v0.6.2optura_platform:documents-v1.4.0

Does every container image need its own repository?

Not necessarily from a container registry perspective. Multiple images can technically be stored in the same repository using different tags.

However, for AWS Marketplace container products, separate repositories may be required for distinct product components or artifacts depending on the delivery configuration.

If your product contains multiple independently delivered components, confirm the required repository structure before creating your AWS Marketplace repositories. If AWS Marketplace requires separate repositories for your components, maintain one repository per component.

Publishing & Product Configuration

Can I publish a container listing before uploading the container images?

Yes. A container product can be published to Limited status without uploading the container images or creating a product version.

However, to move the listing to Public status, you must complete the product version requirements, including pushing the required Helm chart and container images to the appropriate AWS Marketplace-hosted repositories and creating a version with the appropriate delivery option.

If you are using an existing product record, the product information, contract dimensions, and offer configuration may need to be configured or recreated on that product.

Can a repository created under one product be attached to a second product in the same seller account?

No. An AWS Marketplace-hosted repository is created and associated with a specific product record. A repository created for one product cannot be attached to a different product in the same seller account.

If you need the same container images for another product, plan to create the required repositories for that product separately.

If I delete a product, can I reuse its repository names?

No. Once an AWS Marketplace-hosted repository is created, its name cannot be updated or reused for another product.

If you are considering deleting a product that has already created repositories, we recommend contacting AWS Support before proceeding. AWS can confirm the exact behavior for the repositories associated with the product and whether the names remain permanently unavailable at the seller-account level after deletion.

Can multiple component images live in a single repository under different tags?

Technically, yes. A container registry can store multiple images using different tags, for example:

optura_platform:intent-v2.9.0
optura_platform:ontology-v0.6.2

However, the AWS Marketplace delivery model may require separate repository configuration for distinct product components or artifacts.

For products with multiple separately delivered components, confirm the required repository structure for your specific product before consolidating components into a single repository.

Can I publish a product that currently has only a placeholder delivery option?

Yes, to Limited status. A newly created container product initially uses a placeholder version and delivery configuration.

The actual product version and delivery option are configured after the product reaches Limited visibility. If your product requires a Helm delivery option, use the Add new version workflow to create the actual version and configure the required delivery option rather than attempting to modify the placeholder version.

How long does AWS Marketplace review take before a listing can become Public?

AWS Marketplace review can take up to approximately two weeks, although many listings complete review sooner.

The actual timeline depends on the product, the completeness of the submission, and whether AWS identifies issues that require changes or additional review.

Plan for additional time if AWS requests changes and the product needs to be resubmitted.

Delivery Options & Helm Charts

Can I use a Helm chart to deploy multiple container images?

Yes. A Helm chart can reference multiple container images that make up your product.

Your Helm chart must follow the AWS Marketplace requirements for image references and deployment configuration.

Do I need a separate repository for every component of my product?

It depends on the AWS Marketplace delivery requirements for your product. While a container registry can technically store multiple images in a single repository using different tags, AWS Marketplace may require distinct repositories for separately delivered product components.

For products with multiple independent components, we recommend confirming the required repository structure before creating the product repositories.

Can I validate my Helm chart before submitting it?

Yes. You can perform basic validation locally before submitting a product version.

For example:

helm lint
helm template --no-hooks

These commands can help identify chart rendering and configuration issues before submission. However, they do not replace AWS Marketplace's own validation.

AWS Marketplace has restrictions around features such as Helm hooks, lookup functions, and certain Release object properties. Review the current AWS Marketplace requirements before submitting your chart.

PRM & Partner Requirements

What resources need to be tagged for PRM, and in which AWS account?

PRM resource tagging is handled as part of the AWS Partner onboarding and funding process.

Labra will guide your team through the required resource tagging once the Marketplace listing is complete. The required resource, AWS account, and tagging steps depend on your partner setup and the specific PRM requirement being completed.

If you are completing PRM requirements as part of your onboarding, wait for the Labra team to provide the specific tagging instructions rather than applying an arbitrary tag to an AWS resource.

Does PRM resource tagging block FTR submission or listing publication?

PRM resource tagging and Marketplace listing publication are separate processes. PRM requirements are related to AWS Partner funding and partner program processes and should not generally be treated as a prerequisite for creating or publishing the Marketplace listing.

Labra will guide you on the appropriate PRM steps and timing during the onboarding process.

Deployment Architecture & Customer Environment

Can I keep customer data and source code private when using an AWS Marketplace container listing?

Yes. An AWS Marketplace container listing can support a private execution model where the customer’s data and source code remain within the customer’s own AWS environment.

The product runs within the customer’s AWS account and VPC, so the software provider does not need direct access to the customer’s data. This allows you to maintain a private execution model while using AWS Marketplace for procurement and deployment.

However, the product’s data and control planes must run within AWS. The environment remains owned and controlled by the customer, but it is still an AWS environment.

Does an AWS Marketplace container listing work if my customer is entirely on-premises or on another cloud?

No. AWS Marketplace container listings are designed for deployment into supported AWS environments, such as Amazon EKS, Amazon ECS, or AWS Fargate.

If a customer has no AWS infrastructure and wants to run the product entirely on-premises or in another cloud, an AWS Marketplace container listing would not meet that deployment requirement.

Customers purchasing and deploying a container product through AWS Marketplace should therefore have an appropriate AWS environment available for the product.

Does using AWS Marketplace mean I have to give up my private execution model?

Not necessarily. You can preserve a private execution model where the customer’s data remains within their own AWS environment and is not accessible to the software provider.

The key consideration is that the execution environment itself must be AWS-based. The customer can retain control of their AWS account and VPC, while the product runs within that environment.

In other words, AWS Marketplace does not inherently require the provider to access or process the customer’s data. However, it does require the product’s required data and control planes to operate within AWS.

Security & Compliance

Does AWS scan my container images?

Yes. AWS scans container images for security vulnerabilities when new product versions are submitted.

We recommend scanning your images before submission to identify potential issues early.

Can I include credentials or secrets in my container image?

No. Container images must not contain hardcoded passwords, private keys, AWS credentials, or other secrets.

Use appropriate AWS identity and access mechanisms, such as IAM roles, instead.

Can my container run as root?

AWS requires container products to follow the principle of least privilege and recommends that containers run with non-root privileges by default.