Onboard AMC Instances

AMC provides you with an S3 bucket name you must deploy to receive data back from the sent workflow execution requests. The TPS microservices streamlines this process by deploying the bucket and a corresponding bucket policy, granting only the instance-specific AMC data upload account write access. Therefore, to execute AMC workflows, you must first onboard AMC instances into the solution. The notebook TPS_Interface.ipynb provides a step-by-step guide for onboarding one or more AMC instances.

Enter Customer Information

You will need to provide the following customer information in the notebook.

Enter Customer Information

• customer_id *- A distinct identifier assigned to an AMC instance by you. This can be any unique string that helps identify the instance. When managing AMC workflows, you will input the * customer_id for which you want to submit request, and the solution will automatically retrieve the AMC instance information associated with that customer.

• customer_name - The name of the customer. Like the customer_id, this can be a meaningful string that helps identify the customer.

• auth_id - An optional parameter that selects right OAuth credentials to use when making API calls to this instance. You only need to specify it when multi-credential secrets configured.

Specify AMC Instance Information

Enter the connection attributes for the AMC instances, see Prerequisites section to locate AMC instance information.

Enter Customer Information

Next, you’ll need to choose a deployment pattern for the AMC instance S3 buckets. You have three options:

1. If the bucket doesn’t exist in any of your accounts, provide the Region where you want to deploy it and set bucket_exists to false.

2. If the bucket exists in the current AWS account, provide the region and set bucket_exists to true.

3. If the bucket exists in a separate AWS account, provide the AWS account ID and set bucket_account to the account ID.