Adding a new version of your container product on AWS Marketplace

Sign in to the AWS Marketplace Management Portal.

Select Server from the Build menu.

On the Server products tab, select the product you want to modify, and then choose Add repositories from the Request changes dropdown.

Enter a name for the repository. Repository names must be unique across all products in your seller account. To create more than one repository, choose Add new repository for each additional repository.

Select Submit.

Sign in to the AWS Marketplace Management Portal.

From the Build menu, choose Server.

On the Server products tab, select the product you want to modify.

Choose Add repositories from the Request changes dropdown.

Choose View existing repositories.

Select the repository to which you want to upload.

Select View push commands to open a list of instructions, including commands you can use to push Docker container images and Helm charts to that repository.

For general information about how to push container images and other artifacts to repositories, see Pushing an image in the Amazon Elastic Container Registry User Guide.

Use the commands listed to push any needed artifacts from your local repository to the AWS Marketplace repository for your product. The tag that you provide in the push command identifies the version of the artifact. Use a tag that matches the product version that the artifact belongs to.

Repeat for each container image or artifact that your version needs. Each delivery option can include up to 50 container images or artifacts. For all limits, see Limits for container product versions.

Sign in to the AWS Marketplace Management Portal.

Choose Server from the Build menu.

On the Server products tab, select the product you want to add a version to. Then choose Add new version from the Request changes dropdown.

On the Add new version page, enter the Version title and Release notes for your version.

After entering the version details, the next step is to add delivery options. Delivery options are sets of instructions and information that buyers can use to launch the software from your product version. Delivery options are known as fulfillment options to buyers. Create one delivery option for each way that buyers can set up your product, for example Kubernetes and Ubuntu deployments that use different container images. Each request can include up to four delivery options.

1. If the product already has delivery options in other versions, you can use the existing option as a template to add a delivery option to the new version. In Delivery options, choose the delivery option that you want to add from the list. You can edit the option using the instructions in the following steps.

2. To add a new delivery option, choose New delivery option. After adding an option, follow the instructions in the following steps to configure it.

Choose a delivery method for the delivery option. The delivery method determines how buyers will launch your software.

1. To add a Container image delivery option, perform the following steps:

   1. In Container images, add the Amazon ECR URL to the container images that contain the product version software.

   2. In Delivery option title and Deployment option description, enter a title and description for this delivery option.

   3. In Usage instructions, enter detailed information to help your buyers use your software after launching it.

   4. In Supported services, select the environments that buyers can launch the software in.

   5. In Deployment templates, add resources that buyers can use to launch the software. Enter a title and a URL to the resource for each template.

2. To add a Helm chart delivery option, perform the following steps:

   1. In Helm chart, add the Amazon ECR URL to the Helm chart that buyers will install in their deployment environment to launch your software.

   2. In Container images, add the Amazon ECR URL to the container images that contain the product version software.

   3. In Delivery option title and Deployment option description, enter a title and description for this delivery option.

   4. In Usage instructions, enter detailed information to help your buyers use your software after launching it.

   5. In Supported services, select the environments that buyers can launch the software in.

   6. Optional - In Helm release name, enter the name for the Helm release that the helm install command uses.

   7. In Helm installation namespace, enter the name of the Kubernetes namespace where the Helm chart is installed. This field is required for paid products and optional for free products.

   8. Optional - In Kubernetes service account name, enter the name of the Kubernetes service account that will be used to connect to AWS Identity and Access Management (IAM). The Kubernetes service account calls AWS services such as licensing or metering.

   9. In Override parameters, enter parameters that will be used in the Helm CLI commands that launch the software. These parameters allow buyers to override the provided default values. You can enter up to 15 parameters. For more information, see Adding a new version to a container-based product.

      Paid products must include these override parameters:

      • If the delivery option supports Amazon EKS Anywhere, include exactly one override parameter with a DefaultValue of "${AWSMP_LICENSE_SECRET}". The product must also use contract pricing.

      • If you leave Kubernetes service account name empty, include exactly one override parameter with a DefaultValue of "${AWSMP_SERVICE_ACCOUNT}".

   10. Choose Hide passwords and secrets to mask sensitive information in consoles, command line tools, and APIs. For more information, see the NoEcho parameter documentation in Parameters in the AWS CloudFormation User Guide.

3. To add an Amazon EKS console add-on delivery option, make sure that artifacts conform to Requirements for Amazon EKS add-on products, and then perform the following steps. Each request can include only one Amazon EKS add-on delivery option.

   1. In Helm chart, add the Amazon ECR URL to the Helm chart that buyers will install in their deployment environment to launch your software.

   2. In Container images, add the Amazon ECR URL to the container images that contain the product version software. Make sure that all images within the Helm chart are listed.

   3. In Delivery option title and Deployment option description, enter a title and description for this delivery option.

   4. In Visibility, keep the default value of Limited selected.

   5. In Add-on name, enter a unique name for this add-on. The add-on name that you enter will be appended with the seller’s name while being displayed in the Amazon EKS console.

   6. In Add-on version, enter the version of the add-on that will be visible when installing or upgrading this add-on. Follow the format major.minor.patch.

   7. In Add-on type, select a category for your add-on from the dropdown list.

   8. In Kubernetes Version, select all the Kubernetes versions that your add-on will support.

   9. In Architecture, select the platform architectures that your add-on supports. The options are AMD64 and ARM64. We recommend supporting both architectures to maximize compatibility. If your add-on doesn't support ARM64 devices, you must specify a planned date for adding support before your product can be published in all commercial AWS Regions.

   10. In Namespace, enter a unique Kubernetes namespace where your add-on will be installed. The default, kube-system, and kube-public namespaces aren't supported for installing third-party add-ons.

   11. In Environment Override parameters, you can select up to 2 environment parameters from the Amazon EKS add-on framework. You can map parameter names from your values.yaml to these environment variables, which are ${AWS_REGION} and ${AWS_EKS_CLUSTER_NAME}.

To add additional delivery options, choose New delivery option and repeat the instructions in the previous steps to configure them.

Choose Submit.

Sign in to the AWS Marketplace Management Portal.

Select Server from the Build menu.

On the Server products tab, select the product that you want to modify.

From the Request changes dropdown, choose Update version information.

On the Update version page, select the version that you want to update.

Make updates to the selected version. The fields that are available for updating depend on the status of the product version or delivery option.

1. For all versions, you can update the Release notes.

2. For versions that are not yet publicly available, you can update the Version title.

3. For delivery options that haven't been restricted, you can update the following fields:

   • Description

   • Usage instructions

   • Supported services

4. For delivery options in versions that are not yet publicly available, you can update the following fields:

   • Delivery option titles

   • Helm chart (for Helm chart delivery options only)

   • Container images

   • Deployment resources

   • AddOn Name

   • AddOn Version

   • AddOn Type

   • Helm Chart URI

   • CompatibleKubernetesVersions

   • SupportedArchitectures

   • Namespace

   • EnvironmentOverrideParameters

5. For delivery options in versions that are publicly available, you can update SupportedArchitectures.

Choose Submit.

Verify that the request appears on the Requests tab with the Under review status.