Defining the Business Model

As a service provider, you can not only define if new AWS accounts will follow the SPAM or ECAM ordering flow, but also choose if you wish to provide end-customers with an IAM User (default) or a Root user. The business model can be defined at a reseller /Opco level if the Multi-Payer functionality is enabled.

About SPAM and ECAM

SPAM	ECAM
The solution provider’s agreement governs all access and use of AWS services. The solution providers can create their own terms and conditions with respect to AWS services and their authorized use for their end-customers. The email domain for the management (payer) account and all member (linked) accounts should be from the solution provider. AWS services are resold through the solution provider’s accounts.	The end-customer’s agreement governs all access and use of AWS services with the exception of fees, payment, pricing, and tax terms, which are superseded by the terms set forth in the solution provider’s agreement with the end customer. The management (payer) account is set up with the solution provider’s email domain, but all member (linked) accounts should have the end customer’s email domain. The solution provider in this model is set up as the payer so they can receive the bill, but all AWS services are resold through the accounts owned by the end customer.

SPAM

ECAM

The solution provider’s agreement governs all access and use of AWS services. The solution providers can create their own terms and conditions with respect to AWS services and their authorized use for their end-customers.
The email domain for the management (payer) account and all member (linked) accounts should be from the solution provider.
AWS services are resold through the solution provider’s accounts.

The end-customer’s agreement governs all access and use of AWS services with the exception of fees, payment, pricing, and tax terms, which are superseded by the terms set forth in the solution provider’s agreement with the end customer.
The management (payer) account is set up with the solution provider’s email domain, but all member (linked) accounts should have the end customer’s email domain.
The solution provider in this model is set up as the payer so they can receive the bill, but all AWS services are resold through the accounts owned by the end customer.

AWS Business Model Configuration

To define the business model you must use the AWS Account Model marketplace configuration parameter in Connect.

In the ordering process, the ECAM/SPAM configuration is only applied when the New Accounts option is selected in the Order Mode field.

When the ECAM model is selected in the configuration parameter, end-customers will be able to specify their own AWS account email. Consequently, the new account will have the end-customer's domain rather than the provider’s domain.

Additionally, you can choose to generate an IAM User for the end-customer, which is available at Marketplace or OPCO level.

If an IAM user was generated for the end-customer, the subscription information displayed to the end-customer will include the AWS IAM User created by the connector with the relevant SCP applied. To display this template, the provideRootUserForECAM parameter must be set to No. This is configurable at marketplace or OPCO level.

If the ECAM model is selected and the provider chose not to provide the end-customer with an AWS IAM user, the end-customer will have to access with a Root user by resetting their credentials in the AWS console. This is configurable per marketplace/Opco by setting the provideRootUserForECAM parameter to Yes.

For additional information, see the Distributor Portal Configuration Guide.