AIP Account Request Form
Audience: Cloud Operations and ServiceNow Administrators.
Purpose: Document the account request workflow from customer form to provisioning.
Overview
The Aggie Innovation Platform (AIP) account request process uses a web form that integrates with ServiceNow and GitHub for automated account provisioning.
Request Workflow
Step 1: Customer Request
Customer fills out the AIP form at it.tamu.edu/cloud
Form Information Collected
| Field | Purpose |
|---|---|
| Business Unit | Account naming and organization |
| Resource Name | Account identifier |
| Data Classification | OU placement and policies |
| Owners | Account administrators |
| Expenditure | Budget allocation |
| FAMIS Code | Billing code |
Step 2: ServiceNow Processing
The form submission creates a REQ####### in the public cloud aws-azure-gcp, AE (TAMU) assignment group.
RITM Details
The REQ contains a RITM####### populated with the form data:
- Account details and classification
- Owner information
- Budget and billing codes
Step 3: GitHub Integration
ServiceNow's GitHub Spoke integration:
- Creates a new branch in
it-cloud-account-hub - Generates a
.jsondefinition file with account details - Opens a pull request
Definition File Location
it-cloud-account-hub/accounts/aws/definitions/<account-name>.json
Step 4: Terraform Provisioning
When the PR is approved and merged, Terraform:
- Reads definition files from the definitions directory
- Calls the AWS account module to create the account
- Calls the Kion module to configure governance
See: