Creating an AWS Standalone Acount

Before placing an order, it is necessary to add preconfigured AWS Standalone accounts to the AWS Management extension, since those accounts with their corresponding model (SPAM or ECAM) will be used by the connector during the account provisioning process for end customers. For additional information, see the following section in the AWS Management Extension Provider's Guide.

• Creating a Pool of Preconfigured AWS Standalone Accounts

When an order is placed, the connector will pick the oldest AWS Standalone account in Ready status from the extension and it will use it in the account provisioning process for the end-customer. Once the order has been completed, the status of the account used will change to Allocated in the AWS Management extension.

For additional information on how to manage AWS Standalone accounts in the AWS Management extension, see the AWS Management Extension Provider's Guide.

Below you can find a step-by-step walk-through of the order process as a transacting partner:

1. Log in to the Marketplace, and look for the AWS Standalone service plan.

   

2. Click Add to Cart. A notification icon will appear indicating the number of items that the cart contains.

   

3. Click the cart icon to review your order. Click Next.

   

4. You can choose to either purchase the subscription on behalf of an existing customer, or create a new customer. In this example, we will select an existing customer.

   

   

5. In the Order Mode field, select New Account. In the Use Existing CUR field, enter the name of an existing Cost and Usage Report (CUR).

   Note: To obtain information on where to find Cost and Usage Reports, refer to the AWS documentation.

   If an existing CUR is used, the usage report will include previous usage data. On the contrary, if a new CUR is used, usage will only be available 24 hours after the CUR creation date. In this case, it will not be possible to collect the usage generated before the new CUR was set up.

   

    

    

6. Fill in the following fields with the corresponding information:

   • IAM User Name

   • AWS Contact Name

   • AWS Alternate Contact Name

   • AWS Alternate Contact Email

   • AWS Alternate Contact Phone

   • AWS Alternate Contact Title

   • AWS Account Alias

   

7. Review the order details and click Buy.

Note: If the ECAM account model is used in the order, instructions will be provided on how to access the root user when the order is provisioned.