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
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
AWS supports multiple container images or artifacts within a delivery option, so you don't necessarily need a separate repository for every image.
Does every container image need its own repository?
No. Multiple images can be stored in the same repository using different tags.
Your Helm chart or other deployment configuration should reference the appropriate repository and image tag for each component.
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.
Learn more: [AWS Container-Based Product Requirements](AWS REQUIREMENTS LINK)
Do I need a separate repository for every component of my product?
No. AWS supports multiple images or artifacts in a delivery option, so your repository structure can include multiple component images. The appropriate structure depends on how your product is packaged and deployed.
Can I validate my Helm chart before submitting it?
Yes, for EKS add-on products. AWS provides validation guidance using standard Helm commands such as:
helm linthelm template
The chart must pass the required validation before submission.
Learn more: [AWS Container Product Requirements](AWS REQUIREMENTS LINK)
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.
Learn more: [AWS Security Requirements](AWS SECURITY REQUIREMENTS LINK)