1. To add a new delivery option without a template, choose Add delivery option. After adding an option, follow the instructions in the following steps to configure it.
2. Choose a delivery method for the delivery option. The delivery method determines how buyers will launch your software.
• For a Container image delivery option, provide paths to container images in an Amazon Elastic Container Registry (Amazon ECR) repository that was created in the AWS Marketplace console.
Buyers use the container image paths to launch the software by pulling the images directly into their environments.
• For a Helm chart delivery option, provide paths to Helm charts in an Amazon ECR repository that was created in the AWS Marketplace console. Buyers install the Helm charts in their deployment environment to launch the software.
3. To add a Container image delivery option, perform the following steps:
a. In Container images, add the Amazon ECR URL to the container images that contain the product version software.
b. In Delivery option title and Deployment option description, enter a title and description for this delivery option.
c. In Usage instructions, enter detailed information to help your buyers use your software after launching it.
Adding a new version of your product
d. In Supported services, select the environments that buyers can launch the software in.
e. 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.
4. To add a Helm chart delivery option, perform the following steps:
a. In Helm chart, add the Amazon ECR URL to the Helm chart that buyers will install in their deployment environment to launch your software.
b. In Container images, add the Amazon ECR URL to the container images that contain the product version software.
c. In Delivery option title and Deployment option description, enter a title and description for this delivery option.
d. In Usage instructions, enter detailed information to help your buyers use your software after launching it.
e. In Supported services, select the environments that buyers can launch the software in.
f. Optional - In Helm release name, enter the name of the Kubernetes namespace where the Helm chart will be installed.
g. Optional - In Helm installation namespace, enter the name for the Helm release that will be used by the helm install command.
h. 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.
i. Choose to enable QuickLaunch on this product version. QuickLaunch is a feature in AWS Marketplace. Buyers can use QuickLaunch to create an Amazon EKS cluster quickly and launch your software on it by using AWS CloudFormation. For more information, see QuickLaunch in AWS Marketplace.
j. In Override parameters, enter parameters that will be used in the Helm CLI commands that launch the software. Buyers can override the provided default values. If you have enabled QuickLaunch, also enter a parameter name and description for the CloudFormation form.
k. 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.
5. If needed, choose Add delivery option to add additional delivery options and perform the instructions in the previous steps to configure them.
6. Select Submit.
Step 3: Adding a new version to your container product
To add a new version to your container product 1. Sign in to the AWS Marketplace Management Portal.
2. Choose Server from the Products menu.
3. 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.
4. On the Add new version page, enter the Version title and Release notes for your version.
5. 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.
NoteYour product can support multiple platforms with different container images (for example, Kubernetes and Ubuntu deployments). You can create one delivery option for each way that customers can set up your product, up to four delivery options for a product.
Adding a new version of your product
a. 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.
b. To add a new delivery option without a template, choose Add delivery option. After adding an option, follow the instructions in the following steps to configure it.
6. Choose a delivery method for the delivery option. The delivery method determines how buyers will launch your software.
• For a Container image delivery option, provide paths to container images in an Amazon Elastic Container Registry (Amazon ECR) repository that was created in the AWS Marketplace console.
Buyers use the container image paths to launch the software by pulling the images directly into their environments.
• For a Helm chart delivery option, provide paths to Helm charts in an Amazon ECR repository that was created in the AWS Marketplace console. Buyers install the Helm charts in their deployment environment to launch the software.
7. To add a Container image delivery option, perform the following steps:
a. In Container images, add the Amazon ECR URL to the container images that contain the product version software.
b. In Delivery option title and Deployment option description, enter a title and description for this delivery option.
c. In Usage instructions, enter detailed information to help your buyers use your software after launching it.
d. In Supported services, select the environments that buyers can launch the software in.
e. 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.
8. To add a Helm chart delivery option, perform the following steps:
a. In Helm chart, add the Amazon ECR URL to the Helm chart that buyers will install in their deployment environment to launch your software.
b. In Container images, add the Amazon ECR URL to the container images that contain the product version software.
c. In Delivery option title and Deployment option description, enter a title and description for this delivery option.
d. In Usage instructions, enter detailed information to help your buyers use your software after launching it.
e. In Supported services, select the environments that buyers can launch the software in.
f. Optional - In Helm release name, enter the name of the Kubernetes namespace where the Helm chart will be installed.
g. Optional - In Helm installation namespace, enter the name for the Helm release that will be used by the helm install command.
h. 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.
i. Choose to enable QuickLaunch on this product version. QuickLaunch is a feature in AWS Marketplace. Buyers can use QuickLaunch to create an Amazon EKS cluster quickly and launch your software on it by using AWS CloudFormation. For more information, see QuickLaunch in AWS Marketplace.
j. In Override parameters, enter parameters that will be used in the Helm CLI commands that launch the software. Buyers can override the provided default values. If you have enabled QuickLaunch, also enter a parameter name and description for the CloudFormation form.
Updating version information
k. 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.
9. If needed, choose Add delivery option to add additional delivery options and perform the instructions in the previous steps to configure them.
10. Select Submit.
Your request for a new version is created and should complete within minutes. You can track the request from the Requests tab of the Server products page.
NoteYour new version is available to all of your buyers. If your product is currently set to limited availability, your version is available to the set of buyers that the product is available for. If your product is currently set to public availability, then your new version is available to all AWS Marketplace buyers.
If this was your first version set, your product is now ready to be published. For information about how to publish a product, see Publishing container products (p. 127).
Your request for a new version is created and should complete within minutes. You can track the request from the Requests tab of the Server products page.
NoteYour new version is available to all of your buyers. If your product is currently set to limited availability, your version is available to the set of buyers that the product is available for. If your product is currently set to public availability, then your new version is available to all AWS Marketplace buyers.
If this was your first version set, your product is now ready to be published. The next topic describes publishing your product.
If this was your first version set, your product is now ready to be published, see the section called
“Publishing container products” (p. 127).
Updating version information
After a version is created, it can be helpful to provide updated information to your buyers by modifying the information associated with the version. For example, if you plan to restrict version 1.0 after version 1.1 is released, you can update the description of version 1.0 to direct buyers to version 1.1. Provide the date that version 1.0 will be restricted. You update the version information from the AWS Marketplace Management Portal.
To update version information
1. Sign in to the AWS Marketplace Management Portal.
2. Select Server from the Products menu.
3. On the Server products tab, select the product that you want to modify.
4. From the Request changes dropdown, choose Update version information.
5. On the Update version page, select the version that you want to update and choose Submit.
6. Make updates to the selected version. The fields that are available for updating depend on the status of the product version or delivery option.
a. For all versions, you can update the Release notes.
b. For versions that are not yet publicly available, you can update the Version title.
Creating or updating product information for your container product
c. For delivery options that haven't been restricted, you can update the following fields:
• Description
• Usage instructions
• Supported services
d. 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 7. Choose Submit.
8. Verify that the request appears on the Requests tab with the Under review status.
You can check the status of your request at any time from the Requests tab of the Server Products page.