Configuring Parameters

Configuration parameters need to be populated with correct values to ensure the proper functioning of the connector. In order to populate the configuration parameters with the correct values, complete the following steps:

  1. Log in to the CloudBlue Connect Distributor Portal.
  2. Click Products in the main menu at the top of the page and then select AWS.
  3. Click Configuration.
  4. Assign the proper value to each required parameter.

In the table below you can see a description of the parameters.

Parameter ID Description
ccRegion Configure the required region for the marketplace.
currency Provide the corresponding currency ISO code for each marketplace. For example: "EUR".
provisionServiceControlPolicies

Policy IDs which can be obtained by following the instructions provided in the Enable Service Control Policy Type for Organization’s Root and How to create Service Control Policy inside the AWS Organization sections. This value must be a string of IDs (separated by commas) of the AWS Service Control Policies.

Note: Please bear in mind that this feature will be available only for AWS Organizations with All Features enabled, as described in the CloudCheckr and AWS Management Console section.

awsApiMasterKey Provide the AWS Master API key, which can be obtained by following the instructions provided in the How to Obtain an AWS Access Key ID and a Secret Access Key section.
awsApiMasterSecret This value is the AWS API Master Secret, which can be obtained by following the instructions provided in the How to Obtain an AWS Access Key ID and a Secret Access Key section.
awsMasterPayerId

Provide the AWS Marketplace Master Payer ID, which you can find in the AWS Console:

Note: For further information about Master Payer accounts, refer to the CloudCheckr and AWS Management Console section.

ccPartnerProjectId Provide the CloudCheckr Marketplace Partner Project ID, which can be obtained by following the instructions provided in the Allowing AWS Credits to be Sent to the Reseller section.
providerConnectApiToken

Provider's encrypted Connect API token required to create a Tier Configuration Request. The Connect API token must be encrypted by using the public key provided by Ingram Micro.

Use the following command to encrypt the provider API token with the provided public key:

echo -n $TOKEN_PLAIN_TEXT | openssl rsautl -encrypt -pubin -inkey pbkey.pem | base64

The resulting value is a base64 string which you must use along with the private/public key pair version provided by Ingram Micro to construct a string with the following format: keyVersion:providerTokenEncryptedWithPublicKey

For example:

key_v1:MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv9MGNu+zPjafIKErT

Finally, use the resulting string to configure the providerConnectApiToken parameter.

ccApiMasterClientIdCmx This parameter has to be configured in order to move from using Access Keys to Access Tokens for managing CloudCheckr API calls.

Note: To generate the value for this parameter, you can view the section on Moving from Access Keys to CloudCheckr CMx Access Tokens to manage existing API calls.


ccApiMasterSecretCmx This parameter has to be configured in order to move from using Access Keys to Access Tokens for manaing CloudCheckr API calls. It must also be encrypted when being entered in Connect.

To generate the value for this parameter and for details on how to encrypt it, you can view the section on Moving from Access Keys to CloudCheckr CMx Access Tokens to manage existing API calls.


maxInviteResends Configure the number of times that the invitation to join the AWS organization will be resent after the original invitation expires.
includeTaxesEnabled This parameter allows you to choose "Yes" or "No" from a drop-down menu to indicate if you choose to include taxes in the usage report. It is set to "No" by default.
includeTaxesList This parameter comes into effect only when the includeTaxesEnabled parameter is set to "Yes". It allows you to specify the type of tax you wish to include in the usage report. If you want to include multiple taxes, each tax must be separated by a comma e.g. "tax1, tax2" and so on. If left blank, all taxes will be included in the usage report.
middlewareCountriesToCheck

Specify the marketplace countries that the processor will check in the Billing Middleware to determine if the usage should be processed. Country codes must be separated by commas. For example: ES, US, FR.

Notes:

- Usage will only be processed when all the specified countries correspond to countries in the Connect listing and when the Billing Middleware execution was completed successfully for all the specified countries. If the Middleware execution fails for one of the specified countries, the Connect listing will be ignored and usage will not be processed.
- If one of the specified countries cannot be found in the Middleware for a specific billing period, the Connect listing will be ignored and usage will not be processed.
- If a marketplace country of a Connect Listing is not specified in this parameter, usage will be processed for the listing even if the Middleware execution was not completed successfully for such country. Only countries included in the parameter will be taken into account.

cancelEmailSubject

Subject of the email that will be sent to the provider to allow the approval of cancellation requests. The recipient of this email must be configured in the providerContactEmail parameter. HTML tags can be used.

Note: If no subject is defined, a default subject will be used instead.

cancelEmailBody

Body of the email that will be sent to the provider to allow the approval of cancellation requests. The recipient of this email must be configured in the providerContactEmail parameter. HTML tags can be used.

Note: If no email body is defined, a default email body will be used.

tcrEmailSubject

Subject of the email that will be sent to the provider to allow the approval of reseller onboarding requests (TCR). The recipient of this email must be configured in the providerContactEmail parameter. HTML tags can be used.

Note: If no subject is defined, a default subject will be used instead.

tcrEmailBody

Body of the email that will be sent to the provider to allow the approval of reseller onboarding requests (TCR). The recipient of this email must be configured in the providerContactEmail parameter. HTML tags can be used.

Note: If no email body is defined, a default email body will be used.

providerContactEmail

Provider's contact email address. This email address will be the recipient of an email message containing a link that will make it possible to approve cancellation or reseller onboarding requests (TCR).

Note: If an email address is not specified, providers will not be able to approve cancellation or reseller onboarding requests (TCR) and those actions will be performed internally by CloudBlue.

CloudBlue, an Ingram Micro business, uses cookies to improve the usability of our site. By continuing to use this site and/or logging in you are accepting the use of these cookies. For more information, visit our Privacy Policy.