Connecting Labra for Marketplace Cloud Settings

To manage your AWS Marketplace listing and activate Marketplace features such as offers, data feeds, Private Offers (POs), and Agreement-Based Offers (ABOs), Labra requires secure, limited access to your AWS account.

This access can be configured using either of the following deployment methods:

• AWS CloudFormation (CFT): Deploy the required AWS resources using a CloudFormation template provided by Labra.
• Terraform: Download and deploy the required infrastructure using Terraform, allowing your AWS team to manage the configuration through Infrastructure as Code (IaC).

Both methods establish the AWS resources and permissions required to connect your Marketplace account to Labra.

This step is part of your Labra Marketplace onboarding and may require support from your AWS Administrator.

Before starting, ensure that all AWS Marketplace Seller prerequisites have been completed.

📒 Before You Begin

You can review AWS Marketplace prerequisites at any time by clicking Check AWS Requirements in the top-right corner of the Labra Platform.

Your AWS Administrator should have the necessary permissions to deploy AWS resources using your selected method.

➡️ Step 1 – Log in to Labra & Access Cloud Settings

Your AWS Administrator should:

1. Log in to the AWS Console using the AWS account that will be used for your AWS Marketplace listing.
   
   
   Fig. 1
    
2. In a separate tab, log in to your Labra account.
3. Complete your Company details, check the Labra Terms and Conditions box, and click Continue.
   
   
   Fig. 2

You will then be redirected to the Cloud Settings page.

➡️ Step 2 – Add AWS Account Details

In Step 01 – AWS account details, complete the following fields:

• AWS account ID - Enter your 12-digit AWS account ID.
   
• AWS account name - Enter the AWS account name associated with your Marketplace account. This is the account name displayed in the AWS Console next to your account ID.

• Country - Select the country configured as your Business Location in AWS Marketplace Management Portal (AMMP).
   

• Marketplace Role - Choose the option that best describes your Marketplace business model:

  • Independent Software Vendor (ISV)
    Your company sells software directly to customers or through channel partners.
  • Channel Partner (CP)
    Your company sells software on behalf of Independent Software Vendors.

  
  Fig. 3
   

• Currency - Select the currency you intend to transact in through AWS Marketplace.
  
  
  Fig. 4

➡️ Step 3 – Choose Your Deployment Method

Once you have completed your AWS account details, navigate to Step 02 – Create stacks.

You will see two deployment options:

• CloudFormation Stack
• Terraform Stack

Choose the method that best aligns with your organization's AWS infrastructure management practices.

☁️ Option 1: CloudFormation Stack

Select CloudFormation Stack to deploy the required AWS resources using the template provided by Labra.

This option is recommended for customers who prefer to complete the setup directly through the AWS Console.

Continue to Option 1 – CloudFormation Setup below.

🛠️ Option 2: Terraform Stack

Select Terraform Stack to download the infrastructure configuration and deploy the required AWS resources through Terraform.

This option is recommended for customers whose AWS teams manage infrastructure using Terraform or existing Infrastructure as Code workflows.

Continue to Option 2 – Terraform Setup below.

➡️ Step 4 – Configure Your Marketplace Data Feeds

Regardless of your selected deployment method, you will be asked:

"Have you already set up Data Feeds in your own S3 bucket?"

AWS Marketplace Data Feeds provide reporting related to:

• Contracts
• Revenue
• Disbursements

The setup includes:

• S3 Bucket: Stores Marketplace reporting data.
• KMS Key: Encrypts the stored data.
• SNS Topic: Notifies Labra when new Marketplace data is available.

AWS Marketplace data feeds are typically updated every 24 hours.

Select "No" if:

• You are setting up Marketplace onboarding for the first time.
• You do not already manage Marketplace data feeds.
• You do not have an existing S3 bucket configured for Marketplace data feeds.
• You are migrating from another Marketplace platform.

This is the recommended option for most customers.


Fig. 5

Select "Yes" only if:

You already manage your AWS Marketplace data feeds infrastructure and have the following resources configured:

• S3 Bucket ARN
• KMS Key ARN
• SNS Topic ARN

Fig. 6

☁️ Option 1 – CloudFormation Setup

➡️ Step 5A – Launch the CloudFormation Stack

Select CloudFormation Stack and click Launch CloudFormation Stack.

You will be redirected to AWS CloudFormation.

Most fields will be prefilled automatically, including:

• External ID
• Partner Organization Name
• Required Marketplace permissions

➡️ Step 6A – Create the Stack in AWS

In AWS CloudFormation:

1. Review the prefilled values.

2. Update the Stack Name so it is unique.

   Example: labra-marketplace-role-companyname

3. Acknowledge that AWS CloudFormation may create IAM resources with custom names.
4. Click Create Stack.
5. Wait for the stack status to change to CREATE_COMPLETE.

This process may take a few minutes.

➡️ Step 7A – Retrieve the CloudFormation Outputs

Once the stack is successfully created:

1. Open the stack in AWS CloudFormation.
2. Navigate to the Outputs tab.
3. Copy the required output values.
4. Return to Labra and paste them into their corresponding fields.

Depending on your configuration, the required values may include:

• Platform Role ARN
• S3 Bucket ARN
• KMS Key ARN
• SNS Topic ARN

Once complete, proceed to Step 8 – Validate Your AWS Connection.

🛠️ Option 2 – Terraform Setup

If your organization uses Terraform to manage AWS infrastructure, you can deploy the required Marketplace resources using the Terraform configuration provided by Labra.

This method allows your AWS Administrator or DevOps team to complete the deployment through their existing infrastructure management workflow.

➡️ Step 5B – Download the Terraform Stack

In Step 02 – Create stacks:

1. Select Terraform Stack.
2. Confirm your Marketplace Data Feeds configuration by selecting Yes or No.
3. Click Download Terraform Stack.
   
   
   Fig. 7

A window titled Download Terraform Stack will appear with the deployment instructions and required commands.

4. Review the instructions.
5. Click Download stack (.zip).

Fig. 8

The downloaded ZIP file contains the Terraform configuration required to deploy the AWS resources.

➡️ Step 6B – Prepare Your Terraform Environment

Before running the deployment, ensure that:

• Terraform CLI is installed.
• AWS credentials are configured for the AWS account being connected to Labra.
• Your AWS Administrator has the necessary permissions to create the required resources.

Once ready:

1. Locate the downloaded labra-terraform-stack.zip file.
2. Extract the ZIP file.
3. Open a terminal in the extracted folder.

➡️ Step 7B – Deploy the Terraform Stack

In the Download Terraform Stack window, Labra provides three commands to complete the deployment.

The commands contain configuration values generated for your setup, including your Client External ID and deployment parameters.

Run the commands in the following order:

1. Initialize Terraform

Copy and run the make init command provided in Labra.

This initializes the Terraform working directory and prepares the configuration for deployment.

2. Review the deployment plan

Copy and run the make plan command.

This allows your AWS team to review the resources Terraform intends to create or modify before applying the configuration.

3. Apply the Terraform configuration

Once the plan has been reviewed, copy and run the make apply command.

This deploys the required AWS infrastructure and permissions.

Insert new screenshot 2 – Highlight the three deployment commands.

➡️ Step 8B – Retrieve the Terraform Output Values

After Terraform has successfully deployed the infrastructure, retrieve the output values generated by the deployment.

Return to Labra → Onboarding → Cloud settings.

Under Terraform Stack, enter the following values into their corresponding fields:

Table 1


Fig. 9

Once all required values have been entered, proceed to the connection validation.

✅ Complete Your Cloud Settings Configuration

The following steps apply to both CloudFormation and Terraform deployments.

➡️ Step 8 – Validate Your AWS Connection

Once the required AWS resources have been deployed and the corresponding ARN values entered in Labra:

1. Return to Cloud Settings.
2. Verify that the required ARN fields are populated.
3. Click Validate connection.
4. Wait for Labra to verify the configuration.

If validation fails, confirm that:

• The AWS resources were deployed successfully.
• The correct AWS account was used.
• All required ARN values were entered correctly.
• The necessary IAM permissions are configured.

➡️ Step 9 – Complete Customer Data Feeds Setup

If prompted, open the AWS Marketplace Management Portal (AMMP) link provided in Labra.


Fig. 10
 

Under Setup customer data storage, enter the following values:

• S3 Bucket ARN
• KMS Key ARN
• SNS Topic ARN

Use the corresponding values from your CloudFormation or Terraform deployment.

If the SNS Topic ARN is not visible in AWS Marketplace Management Portal, retrieve it from your infrastructure deployment outputs.

For CloudFormation deployments:

1. Open AWS CloudFormation.
2. Select the relevant stack.
3. Open the Outputs tab.
4. Copy the SNSTopicARN value.
5. Paste it into the corresponding fields in AWS Marketplace Customer Data Storage and Labra Cloud Settings.

For Terraform deployments, use the SNS Topic ARN generated by your Terraform deployment.

Once complete, return to Labra and verify that all required validations are successful.

➡️ Step 10 – Submit Cloud Settings

Once all validations have passed:

1. Click Submit.
2. Wait for confirmation that Cloud Settings have been completed successfully.

You can continue with the remaining AWS Marketplace onboarding requirements, including Seller Registration and listing configuration, as applicable.

❓Need Help?

If you encounter any issues while deploying the CloudFormation or Terraform configuration, or if your AWS connection fails validation, please submit a support ticket through Labra Support.

When contacting Support, include the deployment method used, the step where the issue occurred, and any relevant error messages.