Getting started with container products - AWS Marketplace
PrerequisitesCreating a container productProduct lifecycleUpdating a container product (legacy)Updating product visibilityUpdating the allowlist of AWS account IDsAdding a pricing dimensionUpdating dimension informationUpdating pricing terms Updating availability by countryUpdating end-user license agreementUpdating the refund policy of a productCreating the product ID and product code for your container productCreating an initial listingCreating or updating pricing details for container products (legacy)Integrating AWS Marketplace Metering Service for your container productIntegrating AWS License Manager for your container productAdding a new version of your productTesting and releasing your productUpdating version informationRestricting a version of your Amazon EKS add-onCreating or updating product information for your container productPublishing container products (legacy)Container product scans for security issues

Getting started with container products

This topic describes all the steps related to creating, testing, and publishing your first container product for AWS Marketplace.

Prerequisites

Before you get started, you must complete the following prerequisites:

  1. Access and use the AWS Marketplace Management Portal. This is the tool that you use to register as a seller and manage the products that you sell on AWS Marketplace. For more information, see AWS Marketplace Management Portal.

  2. Register as a seller, and submit your tax and banking information. For more information, see Seller registration process.

  3. Create at least one container in Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Kubernetes Service (Amazon EKS), or AWS Fargate. Make sure that you have links for the associated images.

  4. Plan how you'll create and integrate your container product in AWS Marketplace.

    We recommend that you plan your pricing, entitlement, and metering strategy well in advance of publicly publishing your product.

Creating a container product

Creating a container product involves the following steps:

  1. Create the product ID and code.

  2. Creating an initial listing.

  3. Add an initial version of your product.

  4. For paid products, integrate metering into your product.

  5. Updating product visibility.

Note

For information on the product lifecycle, see Product lifecycle.

Product lifecycle

When you create a product in AWS Marketplace, it's initially published with limited visibility so that accounts on the allow list can see it, including the account that created the product. When you're ready, you can publish it to the AWS Marketplace catalog to allow buyers to subscribe and purchase your product.

On the Server product page, you can view the list of your products. Depending on what stage it is at, the product will have one of the following statuses.

  • Staging – An incomplete product for which you're still adding information. At the first Save and exit from the self-service experience, the successful change request creates an unpublished product with information from the completed steps that you submitted. From this status, you can continue adding information to the product or change already submitted details through change requests.

  • Limited – A product is complete after it is submitted to the system and passes all validation in the system. Then the product is released to a Limited status. At this point, the product has a detail page that's only accessible to your account and whoever you have allowlisted. You can test your product through the detail page. For more information or help, contact the AWS Marketplace Seller Operations team.

  • Public – When you're ready to publish the product so that buyers can view and subscribe to the product, you use the Update visibility change request. This request initiates a workflow for the AWS Marketplace Seller Operations team to review and audit your product against AWS policies. After the product is approved and the change request is processed, the product is moved from a status of Limited to Public. For information about AWS guidelines, see Container-based product requirements.

  • Restricted – If you want to stop new users from subscribing to your product, you can restrict the product by using the Update visibility change request. A Restricted status means that existing allowlisted users can continue to use the product. However, the product will no longer be visible to the public or be available to new users.

Note

You can update your product when it's in the Staging, Limited, or Public status. For more information, see Updating a container product.

Updating a container product (legacy)

Updating a container product involves the following steps:

  1. Add a new version of your product, including:

    1. Add repositories for your containers.

    2. Upload the final containers into the repositories.

    3. Create the first version of the product with your first container images.

  2. Update the product version information.

  3. Publish the product for buyers.

Updating product visibility

To change which buyers can view your product in AWS Marketplace, you can use Update visibility.

To update visibility

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/, and then sign in to your seller account.

  2. Go to the Server products page, on the Current server product tab, select the container-based product that you want to modify.

  3. From the Request changes dropdown, choose Update visibility.

    Note

    You can request that the product be moved from a Limited status to a Public status by using this change request. However, the change request must go through an AWS Marketplace Seller Operations team approval process to be moved to Public.

  4. Choose Submit to submit your request for review.

  5. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status becomes Succeeded.

Updating the allowlist of AWS account IDs

You can change the list of AWS account IDs that can view your product in a limited state. Allow-listed accounts display a Limited badge alongside the product version on the product detail page.

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/ and sign in to your seller account.

  2. From the Server Products page, select the container product that you want to modify.

  3. From the Request changes dropdown list, select Update allowlist. The current list of accounts that are allowlisted is shown.

  4. In the Allowlisted AWS accounts field, enter the AWS account IDs and separate them using a comma.

  5. Choose Submit to submit your request for review.

  6. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status will update to Succeeded or Failed.

Adding a pricing dimension

You can add a pricing dimension to the pricing model that you use for your product billing. For more information about pricing models, see Container pricing models.

Note

Adding a pricing dimension for a contract with consumption pricing (for example, pay-as-you-go pricing for additional usage) isn't available on the AWS Marketplace Management Portal.

You can't change your pricing model between contract, usage, and contract with consumption pricing. Contact the AWS Marketplace Seller Operations team for assistance.

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/ and sign in to your seller account.

  2. From the Server Products page, select the container product that you want to modify.

  3. From the Request changes dropdown list, select Update pricing dimensions, and then select Add pricing dimensions.

  4. Depending on the pricing model, you can add contract dimensions or usage dimensions by providing information for API identifier, Display name, and Description.

  5. Choose Next, and enter your contract dimension pricing.

  6. Choose Submit to submit your request for review.

  7. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status will update to Succeeded or Failed.

Updating dimension information

You can change the dimensions information for your product. For more information about pricing models, see Container pricing models.

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/ and sign in to your seller account.

  2. From the Server Products page, select the container product that you want to modify.

  3. From the Request changes dropdown list, select Update pricing dimensions, and then select Update dimension information.

  4. You can add dimension information by providing information for Display name and Description of the dimension you want to update.

  5. Choose Submit to submit your request for review.

  6. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status will update to Succeeded or Failed.

Updating pricing terms

You can change the pricing terms for your product. Pricing terms might need updating if you change the countries in which your product is offered.

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/ and sign in to your seller account.

  2. From the Server Products page, select the container product that you want to modify.

  3. From the Request changes dropdown list, select Update public offer, and then select Update pricing terms.

  4. Current pricing is prepopulated for you to edit. You can delete the current pricing and add your new price. We recommend that you review the prices you’re requesting before submitting your request for review.

  5. Choose Submit to submit your request for review.

  6. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status will update to Succeeded or Failed.

Note

If you increase the price of a dimension using Update pricing terms, you won't be able to update pricing for 90 days. A price increase locks the price for 90 days from the day you initiate the change. This price lock is only in effect for a price increase not a price decrease.

Updating availability by country

You can change the countries in which your product can be offered and subscribed to. For more information, see Countries.

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/ and sign in to your seller account.

  2. From the Server Products page, select the container product that you want to modify.

  3. From the Request changes dropdown list, select Update public offer, and then select Update availability by country.

  4. Select one of the following options:

    • All countries – Available in all supported countries.

    • All countries with exclusions – Available in all supported countries except in selected countries.

    • Allowlisted countries only – Available for buyers to purchase only in the countries you specify.

  5. Choose Submit to submit your request for review.

  6. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status will update to Succeeded or Failed.

Updating end-user license agreement

You can update the end-user license agreement (EULA) to use either the Standard Contract for AWS Marketplace or a custom EULA. Updates made to the EULA take effect for new users subscribing to your product and product renewals.

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/ and sign in to your seller account.

  2. From the Server Products page, select the container product that you want to modify.

  3. From the Request changes dropdown list, select Update public offer, and then select Update EULA.

  4. Select Standard Contract for AWS Marketplace or submit your custom EULA. For a custom EULA, you must provide the contract from an Amazon S3 bucket.

  5. Choose Submit to submit your request for review.

  6. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status will update to Succeeded or Failed.

Updating the refund policy of a product

You can update the refund policy for your product. Updates to the refund policy take effect for all users. For more information, see Product refunds in AWS Marketplace.

  1. Open the AWS Marketplace Management Portal at https://aws.amazon.com/marketplace/management/tour/ and sign in to your seller account.

  2. From the Server Products page, select the container product that you want to modify.

  3. From the Request changes dropdown list, select Update public offer, and then select Update refund policy.

  4. Current refund policy is prepopulated for you to edit. You can delete the current refund policy and add your new refund policy. We recommend that you review the refund policy you’re requesting before submitting your request for review. Submitting the request overwrites the current refund policy.

  5. Choose Submit to submit your request for review.

  6. Verify that the Requests tab shows the Request status as Under review. When the request completes, the status will update to Succeeded or Failed.

Creating the product ID and product code for your container product

To get started with a container product, you must create a product ID and product code record in AWS Marketplace. The product ID is used to track your product throughout its lifecycle.

Use the following procedure to create a new container product in the AWS Marketplace Management Portal, and generate the product ID.

Note

This process also creates a public key for your container that pairs with your product.

To create the container product ID

  1. Open a web browser and sign into the AWS Marketplace Management Portal.

  2. From the menu bar, select Product, and choose Server.

  3. Choose Create server product and then choose Container.

  4. Generate a container product ID and code.

    Note

    (Optional) You can tag your product for tag-based authorization. For more information, see Tagging your AWS resources.

  5. Choose Continue to continue creating your product.

Creating an initial listing

After generating the product ID, product code, and public key, you'll use a wizard to create an initial listing.

  1. Provide product information for your product listing.

  2. Determine the pricing model for your product.

    Note

    For more information, see Container products pricing.

    Note

    For paid products, your product will start with $0.01 pricing to allow you and AWS Marketplace Seller Operations team to test the product without incurring a high cost. You'll provide the actual price when you go public.

  3. Provide additional offer information, including a refund policy, EULA, and offer availability.

  4. Add an initial repository for your container product.

  5. Choose Submit on the last step to move the product to Limited visibility.

    Note

    Your container product is initially created with a placeholder version. You'll add the final version when the product has a Limited visibility.

Creating or updating pricing details for container products (legacy)

To update the pricing details for your container product, you must use a product load form (PLF). The PLF for your product is a spreadsheet that contains information about your product. The following procedure outlines using the PLF to update information about your product, including pricing details.

Note

For more information about pricing models for container products, see Container products pricing.

Your pricing and metering must be aligned. For more information about metering with container products, see Hourly and custom metering with AWS Marketplace Metering Service.

To update pricing for your container product by using the product load form

  1. Open a web browser and sign into the AWS Marketplace Management Portal.

  2. From the menu bar, expand Assets, and choose File upload.

  3. From Product load forms and seller guides on the right side, choose Containers Product Load Form.

  4. Open the PLF spreadsheet on your computer, and fill out the fields to define your product. This information includes your product ID that you made note of when you created your container product.

    Tip

    When viewing the PLF in Microsoft Excel, hover over each of the fields to show comments that provide guidance about how to fill in each field.

    Provide pricing and metering dimensions, based on your pricing model for your product. For more information, see the following:

  5. Save your PLF.

  6. If it's not still open, open a web browser and sign into the AWS Marketplace Management Portal.

  7. From the menu bar, expand Assets, and choose File Upload.

  8. In Upload File, browse your computer and choose the PLF you saved for this container product.

  9. Provide a brief description for this PLF to help you identify it among the other PLFs you upload.

  10. Choose Upload. Your uploaded PLF appears in a table at the bottom of the page.

Your pricing details are reviewed and updated manually by the AWS Marketplace Seller Operations team. It typically takes a few business days to complete the update. You can check the status by choosing Container from the Assets menu in the AWS Marketplace Management Portal. An email message is sent to you when the review of your product pricing details is complete.

Note

Your container product is now created, in a limited state. Your account can view the product for testing and modify it. To make it visible to other test accounts, or when it's ready to be made publicly available, see Publishing container products (legacy).

You can edit your container product pricing by following this same procedure, until you publicly publish the product.

After you create the pricing details for your product, you can add other product details, integrate metering into your product, and create a software version for your product.

Integrating AWS Marketplace Metering Service for your container product

For container-based products with usage pricing, you use the AWS Marketplace Metering Service for both checking entitlement to use your product and metering usage for billing. You must meter for the pricing model that you created when setting your pricing information. For more information, see Hourly and custom metering with AWS Marketplace Metering Service.

Integrating AWS License Manager for your container product

For container-based products with contract pricing, you use the AWS License Manager to associate licenses with your product.

For more information about integrating with AWS License Manager, see Contract pricing for Container products with AWS License Manager.

Adding a new version of your product

Your product might have several versions over its lifetime. Each version has a set of container images that are specific to that version.

Note

You can't add a version to your product until you have created the product ID and the pricing for your product. For more information about these steps, see Creating the product ID and product code for your container product, and Creating or updating pricing details for container products (legacy).

Creating a version of your product involves the following steps:

Your container images and other artifacts for your product are stored in repositories in AWS Marketplace. Typically, you create one repository for each artifact needed, but the repository can store multiple versions of the artifact (with different tags).

Note

All images in your product deployment must use images from the AWS Marketplace repositories.

Step 1: Adding repositories

The following procedure describes how to add any needed repositories in AWS Marketplace.

To add repositories

  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 you want to modify, and then choose Add repositories from the Request changes dropdown.

  4. Enter the name for the repository that you want to create. If you want to create more than one new repository, choose Add new repository for each additional repository, and give it a unique name.

    Note

    The repository will have this structure: <repositoryID>.dkr.ecr.us-east-1.amazonaws.com/<sellerName>/<repositoryName>. When you add items to the repository (in the following procedure), they will get a tag and have this structure: <repositoryID>.dkr.ecr.us-east-1.amazonaws.com/<sellerName>/<repositoryName>:<tag>. The repositoryID is an internal ID for AWS Marketplace. The sellerName is based on the name you created for your seller account. You define the respositoryName in this step. The tag is set when you upload an artifact to the repository.

  5. Select Submit.

Note

You can have up to 50 repositories per product.

A new request is created and shown on the Requests tab. When it's completed, within minutes, you can start adding container images and other artifacts to the repositories you have created.

Step 2: Uploading container images and artifacts to repositories

To upload container images and artifacts to repositories

  1. Sign in to the AWS Marketplace Management Portal.

  2. From the Products menu, choose Server.

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

  4. Choose Add repositories from the Request changes dropdown.

  5. Choose View existing repositories.

  6. Select the repository to which you want to upload.

  7. 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, refer to Pushing an image in the Amazon Elastic Container Registry User Guide.

    Note

    You can use the following Amazon Elastic Container Registry (Amazon ECR) API operations when calling docker pull or docker push:

    • DescribeImages – Use this to review the metadata about the images in a repository.

    • GetAuthorizationToken – Use to authenticate before uploading artifacts to the repository, then use docker pull or docker push commands.

    • ListImages – Use to view a list of images you pushed.

  8. Use the commands listed to push any needed artifacts from your local repository to the AWS Marketplace repository for your product.

    Note

    The tag that you provide in the push commands is used to differentiate the version of the artifact that you are uploading to the repository. Use a tag that makes sense for the version the artifacts are a part of.

  9. Repeat for each container image or artifact you need in your version.

    Note

    Your version can include up to 50 container images or artifacts in each delivery option. Refer to the following procedure for more information about delivery options.

After you upload your artifacts, you're ready to create the version of your product.

Note

Your container images are scanned automatically to see if they meet the Container-based product requirements. For more information, refer to Container product scans for security issues.

Adding a new delivery option

Each version of your container product would need a delivery option. Delivery option specifies the deployment options available for the buyer. Depending on one of the delivery options below, you would need to upload the appropriate artifacts into the repositories.

  • For a Container image delivery option, upload all the container images required for the product installation into the Amazon Elastic Container Registry (Amazon ECR) repository created in the AWS Marketplace console.

  • For a Helm chart delivery option, upload the Helm chart and container images into the Amazon ECR repository created in the AWS Marketplace console.

  • For an Amazon EKS console add-on delivery option, upload the Helm chart and container images into the Amazon ECR repository created in the AWS Marketplace console.

Step 3: Adding a new version to your container product

Note

If you receive any errors when adding a new version to your container, see the Add a new version Asynchronous Errors table in the AWS Marketplace Catalog API Reference.

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.

    Note

    Your 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 per version of the product.

    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.

  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.

    • For an Amazon EKS console add-on delivery option, provide paths to Helm charts in an Amazon ECR repository that was created in the AWS Marketplace console. Buyers install the container using the Amazon EKS console or native Amazon EKS add-on APIs to launch the software. For more information, see Available Amazon EKS add-ons from Amazon EKS.

    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 of the Kubernetes namespace where the Helm chart will be installed.

      7. Optional - In Helm installation namespace, enter the name for the Helm release that will be used by the helm install command.

      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. 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.

      10. 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. If you have enabled QuickLaunch, also enter a parameter name and description for the CloudFormation form. There is a limit of 15 parameters when using the AWS Marketplace Management Console, but there is no limit when using the AWS Marketplace Catalog API. For more information, see Adding a new version to a container-based product.

        Note

        Some Override parameters are required. Amazon EKS Anywhere products require an Override parameter for license secret with a DefaultValue of "${AWSMP_LICENSE_SECRET}". For paid products, you must provide one Override parameter for service account configuration with the DefaultValue of "${AWSMP_SERVICE_ACCOUNT}".

      11. 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:

      Note

      Only one Amazon EKS add-on delivery option is supported per version. You aren't able to add a new version until the current version you're working with is published on the Amazon EKS console.

      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, enter up to 2 parameters in the Helm CLI commands that launch the software. These parameters allow buyers to override the default values, which are ${AWS_REGION} and ${AWS_EKS_CLUSTER_NAME}.

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

  8. Choose Submit.

Testing and releasing your product

This section provides guidance on the next steps after publishing a version for your container product. It outlines the specific steps and process required for testing and releasing your product to public.

Container image and Helm chart delivery options

This section provides guidance on the releasing your Container image and Helm chart.

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. If you receive any errors when testing or releasing your add-on, see the Aynchronous Errors table in Add a new version in the AWS Marketplace Catalog API Reference.

Note

If your product is currently set to limited availability, only the buyers that the product is available for can access the product version. If your product is currently set to public availability, all AWS Marketplace buyers can access the product version.

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 (legacy).

Amazon EKS add-on delivery option

This section provides guidance on testing and releasing your Amazon EKS add-on.

Test your add-on

  • After you submit your add-on, AWS Marketplace processes your request and publishes your add-on in a limited state for you to validate in the Amazon EKS add-on catalog. You can track the request from the Requests tab of the Server products page in the AWS Marketplace Management Portal. Ingestion times will vary.

  • After your add-on is available, you can find it in the Asia Pacific (Seoul) Region for testing purposes. AWS Marketplace relies on your expertise to verify the functionality of your software. To test your add-on, you must create an Amazon EKS cluster in the Asia Pacific (Seoul) Region in your seller account where your add-on is allowlisted. To test your add-on, follow these detailed instructions. Make sure to test on each Kubernetes version that your software supports.

  • If you're offering a paid product, create a private offer to the following internal AWS accounts. These accounts help integrate your software into the Amazon EKS console in all commercial AWS Regions.

    
Accounts List 1 471358734678,610158858058,027825190106,041405988046,939618537104,571342016161,915587997900,904230077954,000219069224,842354999200,051117675113,419405427192,294452347560,303128057820,186420152961,122010303470,435387826909,132270578346,796800024149,613093936565,051494632622,371872539196,074235463582,408202761791
Accounts List 2 101994863060,842064867862,784198098879,361865901973,883599120538,662413594417,262494542709,892528196571,938189271391,288092140294,297512042063,204409763375

  • Keep your test cluster with the add-on active until AWS Marketplace approves and moves your add-on version to public.

Release your add-on to public

After you have validated your software via Amazon EKS cluster as an add-on, you can now release the version to public using the AWS Marketplace Management Portal or AWS Marketplace Catalog API. For more information, see Update the visibility for an Amazon EKS add-on in the AWS Marketplace Catalog API Reference. You can track the request from the Requests tab of the Server products page in the AWS Marketplace Management Portal. Ingestion times will vary.

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.

  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.

    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.

  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.

Restricting a version of your Amazon EKS add-on

To restrict a version of your container product published as an add-on, contact the AWS Marketplace operations team using the contact us form at the bottom of the AWS Marketplace Management Portal.

Creating or updating product information for your container product

After you have created your product ID and set the pricing, you can edit your product information, including what customers will see about your container product in the AWS Marketplace. The following procedure outlines creating the product details for your product.

To create or update product details for your container product

  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 product information.

  5. Update any of the following fields that you want to change:

    • Product title

    • SKU

    • Short description

    • Long description

    • Product logo image URL

    • Highlights

    • Product categories

    • Keywords

    • Product video URL

    • Resources

    • Support information

    Note

    Image URLs must be in an Amazon S3 bucket that is publicly accessible. For more details about the logo format, see Company and product logo requirements.

  6. Choose Submit.

  7. Verify that the request appears on the Requests tab with the Under review status. You might need to refresh the page to see the request on the list.

You can check the status of your request at any time from the Requests tab of the Server Products page.

Publishing container products (legacy)

When you initially create your product, its availability is limited to just your account. Once your product is ready for testing (including having product details filled in and the first version created), you can make it available to other accounts for testing, or to all accounts as a public product.

Note

Before publishing publicly, you should review your product to ensure accuracy, including image links, deployment templates, descriptions, and pricing. Your pricing model can't be changed for publicly published products.

To publish your limited product to additional accounts or for public availability, contact the AWS Marketplace Seller Operations team. In your request, provide the product ID and describe the changes that you want to make.

Note

You can also choose to restrict a version that you no longer want available to buyers. You can include this in a request to publish a product publicly, to avoid test versions appearing in public products.

You can't restrict a version if it will leave your public product with no public versions.

When you publicly publish a container product, you make it visible to all AWS customers who can then subscribe and launch your product. The AWS Marketplace Seller Operations team reviews the data in your product information, as well as your test calls to the AWS Marketplace Metering Service.

Container product scans for security issues

When you create a change request to add a new version to your container product, we scan the container images included in that new version and check for security vulnerabilities. To do this, we perform a layer-by-layer static scan on the image. If we find critical vulnerabilities with remotely exploitable risk vectors, we provide you with a list of found issues. We strongly recommend that you perform your own security analysis using a container image scanner such as Clair, Twistlock, Aqua Security, or Trend Micro to avoid delays in the ingestion and publishing process.

Your choice of base image for building your container images can have a significant influence on the security profile of the final image. If you choose a base image that already has known critical vulnerabilities, they will be flagged because of the base layer, even if your application software layers are clean. We recommend that you verify that you're starting with a base container that is free of vulnerabilities before you build your images and submit them to AWS Marketplace.