J-9 DoD Account Provisioning Tool API Amendment 0002

openapi: 3.0.2
info:
description: >- This API is meant for provisioning resources in a target Cloud Environment in a vendor-agnostic fashion. By implementing this API, vendors make it possible to automatically provision accounts via ATAT.

## Portfolios

Portfolios represent a logical container for a group of related Environments and the Task Orders/CLINs which fund them. As a general rule, everything within a given Portfolio is part of the same overall Mission or Program.

## Environments

Environments represent a logical container for a set of cloud resources which are funded by a particular CLIN within a Task Order. The term is meant to be agnostic across CSPs. An Environment can be thought of as an account at the root of a hierarchy. ATAT does not dictate structure within a Portfolio. Once an Environment has been provisioned a Mission Owner is free to organize and secure resources to satisfy mission requirements.

## Task Orders

Portfolios contain one or more *Task Orders* (TO), which in turn contain one or more *Contract Line Item Numbers* (CLINs). Each have separate Periods of Performance (PoP) dates; CLIN PoP dates will be within the time frames of the Task Order in which they belong.

## Cost reporting

Provisioned resources incur costs with participating CSPs. Costs related to provisioned resources can be attributed to specific CLINs. Actual and forecasted CSP costs can be reported by CLIN. version: 1.3.2
title: ATAT CSP API
contact:
email: [email protected] tags:
- name: access
description: >- Operations to manage access to provisioned Environments - name: cost
description: >- Operations to query for actual and forecasted costs
- name: provisioning
description: >- Operations to manage provisioned Environments
paths:
'/portfolios':
parameters:
- $ref: '#/components/parameters/ApiVersion'
post:
tags:
- provisioning
summary: Adds a new Portfolio
security:
- oidc: [atat/write-portfolio]
description: >- Adds a new Portfolio to be provisioned, including Task Orders and Operators. Once provisioned, Operators can log in to the CSP and begin using provisioned resources and services, funded by the provided Task Order(s). Note that invitations should be sent to all Operator email addresses included in the request. See [#/info/description](#/info/description) and [#/components/schemas](#/components/schemas) for details of these constructs.