Palo Alto Networks

Palo Alto Networks AWS Logging Accounts API

To ingest the VPC flow logs from Amazon S3 buckets to Prisma Cloud, you need an AWS logging account. If you need flow logs ingestion, after onboarding your AWS account, you must onboard the logging account which has the S3 bucket storing VPC flow logs for the monitored account. The APIs in this category can be used to configure and manage these logging accounts.

GitHub OpenAPI

Operations 17

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /v1/cloudAccounts/awsLoggingAccounts List all AWS logging accounts · Get all AWS Logging Accounts #
Ask an LLM
“Which AWS logging accounts are onboarded to Prisma Cloud?”
“Can I list logging accounts only for one AWS partition such as GovCloud?”
Tell an agent
List all AWS logging accounts in partition {awsPartition}.
Show every onboarded AWS logging account and its details.
POST /v1/cloudAccounts/awsLoggingAccounts Add a new AWS logging account · Add AWS Logging Account #
Ask an LLM
“How do I onboard a new AWS logging account with its role and S3 buckets?”
“What role ARN and external ID are needed to register a logging account?”
Tell an agent
Add AWS logging account {loggingAccountId} named {loggingAccountName} using role ARN {loggingAccountRoleArn}.
Register logging account {loggingAccountId} with role {loggingAccountRoleName}, external ID {externalId} and buckets {loggingAccountBuckets}.
POST /v1/cloudAccounts/awsLoggingAccounts/cft Generate a CloudFormation template for a new logging account · Generate a New CFT Template #
Ask an LLM
“Can Prisma Cloud generate the CloudFormation template I need before onboarding a logging account?”
“How do I get a CFT that creates the role for a logging account I haven't added yet?”
Tell an agent
Generate a CFT for new AWS logging account {loggingAccountId} with role name {loggingAccountRoleName}.
Create a CloudFormation template for a logging account in partition {awsPartition} covering buckets {loggingAccountBuckets}.
POST /v1/cloudAccounts/awsLoggingAccounts/permissionsStatus Check permissions status for logging account details · Get Logging Account Status #
Ask an LLM
“Before saving, can I check whether a logging account's role and buckets have the right permissions?”
“What permission status would an AWS logging account get with a given role ARN and bucket list?”
Tell an agent
Check permission status for unsaved logging account {loggingAccountId} using role ARN {loggingAccountRoleArn}.
Validate the permissions of logging account details {loggingAccountName} with buckets {loggingAccountBuckets} before onboarding.
GET /v1/cloudAccounts/awsLoggingAccounts/{accountId} Get one AWS logging account · Get Logging Account By ID #
Ask an LLM
“How do I see the details of a single AWS logging account?”
“What role and buckets are configured on a specific logging account?”
Tell an agent
Get the details of AWS logging account {accountId}.
Show me the configuration of logging account {accountId}.
DELETE /v1/cloudAccounts/awsLoggingAccounts/{accountId}/buckets/{bucketName} Remove an S3 bucket from a logging account · Delete an S3 bucket #
Ask an LLM
“Can I detach one S3 bucket from a logging account without deleting the account?”
“How do I stop Prisma Cloud from reading logs out of a particular bucket?”
Tell an agent destructive · confirm first
Delete S3 bucket {bucketName} from logging account {accountId}.
Remove bucket {bucketName} from AWS logging account {accountId}.
GET /v1/cloudAccounts/awsLoggingAccounts/{accountId}/cft Regenerate the CFT for an existing logging account · Regenerate CFT for an Existing Account #
Ask an LLM
“Can I download a fresh CloudFormation template for a logging account that's already onboarded?”
“Where do I get the current CFT for an existing logging account?”
Tell an agent
Regenerate the CloudFormation template for existing logging account {accountId}.
Get the current CFT for AWS logging account {accountId}.
POST /v1/cloudAccounts/awsLoggingAccounts/{accountId}/cft Regenerate a logging account CFT after a role name change · Regenerate CFT for New RoleName #
Ask an LLM
“I renamed the IAM role on my logging account; how do I get an updated CFT?”
“Can I regenerate a CloudFormation template for an existing account with a new role name?”
Tell an agent
Regenerate the CFT for logging account {accountId} with new role name {loggingAccountRoleName}.
Build a new CloudFormation template for account {accountId} because its role changed to {loggingAccountRoleName}.
GET /v1/cloudAccounts/awsLoggingAccounts/{accountId}/role/{roleName}/externalId Get the external ID for a logging account role · Get External ID of an Account #
Ask an LLM
“What external ID should the trust policy use for my logging account role?”
“How do I look up the external ID for a given account and role name?”
Tell an agent
Get the external ID for logging account {accountId} and role {roleName}.
Show the external ID tied to role {roleName} on AWS account {accountId}.
PUT /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId} Update an AWS logging account · Update Logging Account #
Ask an LLM
“Can I rename a logging account or change its role ARN?”
“How do I update the bucket list on an onboarded logging account?”
Tell an agent
Rename logging account {loggingAccountId} to {loggingAccountName}.
Update logging account {loggingAccountId} to use role ARN {loggingAccountRoleArn}.
DELETE /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId} Delete an AWS logging account · Delete a Logging Account by ID #
Ask an LLM
“How do I offboard an AWS logging account entirely?”
“What gets removed when a logging account is deleted from Prisma Cloud?”
Tell an agent destructive · confirm first
Delete AWS logging account {loggingAccountId}.
Offboard logging account {loggingAccountId} from Prisma Cloud.
GET /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets List S3 bucket names on a logging account · List S3 Bucket Names #
Ask an LLM
“Which S3 buckets are attached to my logging account?”
“Can I get just the bucket names for a logging account?”
Tell an agent
List the S3 bucket names on logging account {loggingAccountId}.
Show which buckets logging account {loggingAccountId} reads from.
POST /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets Add an S3 bucket to a logging account · Add an S3 bucket #
Ask an LLM
“How do I attach another S3 bucket to an existing logging account?”
“Can I set path prefixes and a KMS key when adding a bucket?”
Tell an agent
Add S3 bucket {bucketName} in region {bucketRegion} to logging account {loggingAccountId}.
Attach bucket {bucketName} with KMS key {keyArn} to logging account {loggingAccountId}.
GET /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets/{bucketName} Get S3 bucket details on a logging account · Get all S3 Buckets #
Ask an LLM
“What region, prefixes and key are configured for a specific bucket on my logging account?”
“Can I inspect one bucket's settings within a logging account?”
Tell an agent
Get details of bucket {bucketName} on logging account {loggingAccountId}.
Show the region and path prefixes for bucket {bucketName} in account {loggingAccountId}.
PUT /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets/{bucketName} Update an S3 bucket on a logging account · Update S3 Bucket Details #
Ask an LLM
“How do I change the path prefixes on a bucket already attached to a logging account?”
“Can I swap the KMS key used for a logging bucket?”
Tell an agent
Set path prefixes {bucketPathPrefixes} on bucket {bucketName} in logging account {loggingAccountId}.
Change the KMS key of bucket {bucketName} on account {loggingAccountId} to {keyArn}.
GET /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/permissionsStatus Get the permissions status of a saved logging account · Get Logging Account Status - GET #
Ask an LLM
“Is my onboarded logging account healthy, or is it missing permissions?”
“What is the current status of a saved logging account by its ID?”
Tell an agent
Get the permissions status of logging account {loggingAccountId}.
Check whether saved logging account {loggingAccountId} is healthy.
POST /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/permissionsStatus Check a saved logging account's status with new details · Get Logging Account Status - POST #
Ask an LLM
“Can I test an existing logging account's permissions against a different role or bucket?”
“What detailed status would my saved logging account have with a changed role ARN?”
Tell an agent
Check detailed status of existing logging account {loggingAccountId} against role ARN {loggingAccountRoleArn}.
Test saved account {loggingAccountId} permissions using buckets {loggingAccountBuckets}.

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/palo-alto-networks/refs/heads/main/openapi/palo-alto-networks-aws-logging-accounts-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/palo-alto-networks:palo-alto-networks-aws-logging-accounts-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

palo-alto-networks-aws-logging-accounts-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  version: v1
  title: Prisma Cloud REST API Doc AWS Logging Accounts API
  contact: {}
  license:
    name: Public
  description: To ingest the VPC flow logs from Amazon S3 buckets to Prisma Cloud, you need an AWS logging account. If you need flow logs ingestion, after onboarding your AWS account, you must onboard the logging account which has the S3 bucket storing VPC flow logs for the monitored account. The APIs in this category can be used to configure and manage these logging accounts.
servers:
- url: https://api.prismacloud.io
- url: https://api2.prismacloud.io
- url: https://api3.prismacloud.io
- url: https://api4.prismacloud.io
- url: https://api.anz.prismacloud.io
- url: https://api.eu.prismacloud.io
- url: https://api2.eu.prismacloud.io
- url: https://api.gov.prismacloud.io
- url: https://api.prismacloud.cn
- url: https://api.ca.prismacloud.io
- url: https://api.sg.prismacloud.io
- url: https://api.uk.prismacloud.io
- url: https://api.ind.prismacloud.io
- url: https://api.jp.prismacloud.io
- url: https://api.fr.prismacloud.io
tags:
- name: AWS Logging Accounts
  description: To ingest the VPC flow logs from Amazon S3 buckets to Prisma Cloud, you need an AWS logging account. If you need flow logs ingestion, after onboarding your AWS account, you must onboard the logging account which has the S3 bucket storing VPC flow logs for the monitored account. The APIs in this category can be used to configure and manage these logging accounts.
paths:
  /v1/cloudAccounts/awsLoggingAccounts:
    get:
      tags:
      - AWS Logging Accounts
      summary: Get all AWS Logging Accounts
      description: Get the list of all the AWS Logging accounts and its details.
      operationId: getLoggingArchiveAccounts
      parameters:
      - name: awsPartition
        in: query
        description: AWS Partition Name (optional)
        required: false
        schema:
          type: string
      responses:
        '200':
          description: Successfully retrieved list of accounts
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/LoggingArchiveAccountModel'
        '204':
          description: No logging archive accounts exists for customer
        '401':
          description: Unauthorized Access
      security:
      - x-redlock-auth: []
      x-public: 'true'
    post:
      tags:
      - AWS Logging Accounts
      summary: Add AWS Logging Account
      description: Add new AWS logging account.
      operationId: saveLoggingAccount
      requestBody:
        $ref: '#/components/requestBodies/LoggingArchiveAccountModel'
      responses:
        '200':
          description: successful operation
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/LoggingArchiveAccountModel'
        '201':
          description: Successfully created account
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/cft:
    post:
      tags:
      - AWS Logging Accounts
      summary: Generate a New CFT Template
      description: Dynamically generate a CFT for the AWS Logging Account.
      operationId: generate-log-account-cft
      requestBody:
        $ref: '#/components/requestBodies/LoggingAccountCFTRequest'
      responses:
        '200':
          description: success
        '400':
          description: bad_request
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/permissionsStatus:
    post:
      tags:
      - AWS Logging Accounts
      summary: Get Logging Account Status
      description: Get the status of the AWS logging account based on filter criteria such as, ID, name, RoleRN, and bucket.
      operationId: checkLoggingAccountStatus
      requestBody:
        $ref: '#/components/requestBodies/LoggingArchiveAccountModel'
      responses:
        '200':
          description: Successfully completed status check for logging account
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/CloudAccountStatus'
        '401':
          description: Unauthorized Access
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/{accountId}:
    get:
      tags:
      - AWS Logging Accounts
      summary: Get Logging Account By ID
      description: Get details of a logging account by ID.
      operationId: getLoggingArchiveAccount
      parameters:
      - name: accountId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Successfully retrieved account
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/LoggingArchiveAccountModel'
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
        '404':
          description: Account not found
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/{accountId}/buckets/{bucketName}:
    delete:
      tags:
      - AWS Logging Accounts
      summary: Delete an S3 bucket
      description: Delete an S3 bucket in a logging account.
      operationId: deleteBucket
      parameters:
      - name: accountId
        in: path
        description: AWS Logging Account ID
        required: true
        schema:
          type: string
      - name: bucketName
        in: path
        description: AWS S3 Bucket Name
        required: true
        schema:
          type: string
      responses:
        '200':
          description: successful operation
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/BucketModel'
        '204':
          description: Successfully deleted bucket
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
        '404':
          description: Account or bucket not found.
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/{accountId}/cft:
    get:
      tags:
      - AWS Logging Accounts
      summary: Regenerate CFT for an Existing Account
      description: Dynamically generate a CFT for an existing Log Account.
      operationId: generate-log-account-cft-existing
      parameters:
      - name: accountId
        in: path
        description: Account ID
        required: true
        schema:
          type: string
      responses:
        '200':
          description: success
        '400':
          description: bad_request
        '404':
          description: Account or bucket not found.
      security:
      - x-redlock-auth: []
      x-public: 'true'
    post:
      tags:
      - AWS Logging Accounts
      summary: Regenerate CFT for New RoleName
      description: Regenerate a new CFT for an existing logging account if roleName changes.
      operationId: generate-log-account-cft-role
      parameters:
      - name: accountId
        in: path
        description: Account ID
        required: true
        schema:
          type: string
      requestBody:
        $ref: '#/components/requestBodies/LoggingAccountCFTRequest'
      responses:
        '200':
          description: success
        '400':
          description: bad_request
        '404':
          description: Account or bucket not found.
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/{accountId}/role/{roleName}/externalId:
    get:
      tags:
      - AWS Logging Accounts
      summary: Get External ID of an Account
      description: Get external ID of an AWS Logging Accountby account ID and rolename.
      operationId: GetExternalID
      parameters:
      - name: accountId
        in: path
        description: AWS AccountId
        required: true
        schema:
          type: string
      - name: roleName
        in: path
        description: AWS Role Name
        required: true
        schema:
          type: string
      responses:
        '200':
          description: success
          content:
            application/json; charset=UTF-8:
              schema:
                type: string
        '400':
          description: bad_request
      security:
      - x-redlock-auth: []
      x-public: 'true'
      x-operation-id-source: normalized
      x-operation-id-original: 'Get External ID '
  /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}:
    put:
      tags:
      - AWS Logging Accounts
      summary: Update Logging Account
      description: Update details of the logging account.
      operationId: updateLoggingAccount
      parameters:
      - name: loggingAccountId
        in: path
        description: AWS Logging Account ID
        required: true
        schema:
          type: string
      requestBody:
        $ref: '#/components/requestBodies/LoggingArchiveAccountModel'
      responses:
        '204':
          description: No content
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
      security:
      - x-redlock-auth: []
      x-public: 'true'
    delete:
      tags:
      - AWS Logging Accounts
      summary: Delete a Logging Account by ID
      description: Delete an AWS logging account based on account ID.
      operationId: deleteLoggingAccount
      parameters:
      - name: loggingAccountId
        in: path
        required: true
        schema:
          type: string
      responses:
        '204':
          description: No content
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets:
    get:
      tags:
      - AWS Logging Accounts
      summary: List S3 Bucket Names
      description: Get a list of all the S3 bucket names associated to a logging account.
      operationId: getBuckets
      parameters:
      - name: loggingAccountId
        in: path
        description: AWS Logging Account ID
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Successfully retrieved buckets
          content:
            application/json; charset=UTF-8:
              schema:
                type: array
                items:
                  type: object
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
        '404':
          description: Account not found
      security:
      - x-redlock-auth: []
      x-public: 'true'
    post:
      tags:
      - AWS Logging Accounts
      summary: Add an S3 bucket
      description: Add an S3 bucket to the existing logging account.
      operationId: saveBucket
      parameters:
      - name: loggingAccountId
        in: path
        description: AWS Logging Account ID
        required: true
        schema:
          type: string
      requestBody:
        $ref: '#/components/requestBodies/BucketModel'
      responses:
        '200':
          description: Successfully saved bucket
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/BucketModel'
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
        '404':
          description: Account not found.
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets/{bucketName}:
    get:
      tags:
      - AWS Logging Accounts
      summary: Get all S3 Buckets
      description: Get the list of all S3 bucket and its details associated with a logging account.
      operationId: getBucketDetails
      parameters:
      - name: loggingAccountId
        in: path
        required: true
        schema:
          type: string
      - name: bucketName
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Successfully retrieved bucket
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/BucketModel'
        '401':
          description: Unauthorized Access
        '404':
          description: Resource not found
      security:
      - x-redlock-auth: []
      x-public: 'true'
    put:
      tags:
      - AWS Logging Accounts
      summary: Update S3 Bucket Details
      description: Update details of an S3 bucket associated to a specific logging account.
      operationId: updateBucket
      parameters:
      - name: loggingAccountId
        in: path
        description: AWS Logging Account ID
        required: true
        schema:
          type: string
      - name: bucketName
        in: path
        description: AWS S3 Bucket Name
        required: true
        schema:
          type: string
      requestBody:
        $ref: '#/components/requestBodies/BucketModel'
      responses:
        '200':
          description: Successfully updated bucket
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/BucketModel'
        '400':
          description: Bad Request. Data validation failed.
        '401':
          description: Unauthorized Access
        '404':
          description: Account or bucket not found.
      security:
      - x-redlock-auth: []
      x-public: 'true'
  /v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/permissionsStatus:
    get:
      tags:
      - AWS Logging Accounts
      summary: Get Logging Account Status - GET
      description: Get status of a logging account based on ID.
      operationId: getLoggingAccountStatus
      parameters:
      - name: loggingAccountId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: List of logging account statuses
          content:
            application/json; charset=UTF-8:
              schema:
                type: array
                items:
                  type: object
        '400':
          description: Invalid parameter
        '401':
          description: Unauthorized Access
        '404':
          description: Account not found
      security:
      - x-redlock-auth: []
      x-public: 'true'
    post:
      tags:
      - AWS Logging Accounts
      summary: Get Logging Account Status - POST
      description: Get detailed status of a logging account based on ID, name, roleRN or bucket name.
      operationId: checkLoggingAccountStatusForProvidedAccount
      parameters:
      - name: loggingAccountId
        in: path
        required: true
        schema:
          type: string
      requestBody:
        $ref: '#/components/requestBodies/LoggingArchiveAccountModel'
      responses:
        '200':
          description: Successfully completed status check for existing logging account
          content:
            application/json; charset=UTF-8:
              schema:
                $ref: '#/components/schemas/CloudAccountStatus'
        '400':
          description: Invalid parameter
        '401':
          description: Unauthorized Access
        '404':
          description: Logging Account doesn't exist
      security:
      - x-redlock-auth: []
      x-public: 'true'
components:
  schemas:
    AccountStatusMessage:
      type: object
      properties:
        message:
          type: string
        staticMessage:
          type: boolean
    LoggingAccountCFTRequest:
      type: object
      properties:
        awsPartition:
          type: string
        externalId:
          type: string
        loggingAccountId:
          type: string
        loggingAccountRoleName:
          type: string
        trustedEntity:
          type: string
        partitionName:
          type: string
          enum:
          - US_GLOBAL
          - US_GOV
          - CHINA
        loggingAccountBuckets:
          type: array
          items:
            $ref: '#/components/schemas/BucketModel'
    CloudAccountStatus:
      type: object
      properties:
        id:
          type: string
        name:
          type: string
        status:
          type: string
        statusMessage:
          $ref: '#/components/schemas/AccountStatusMessage'
    BucketModel:
      type: object
      required:
      - bucketName
      - bucketRegion
      - loggingAccountId
      properties:
        bucketName:
          type: string
          description: S3 Bucket Name
        bucketRegion:
          type: string
          description: S3 Bucket Region
        bucketPathPrefixes:
          type: string
          description: Bucket Path Prefixes
        keyArn:
          type: string
          description: CMS Key ARN
        loggingAccountId:
          type: integer
          format: int32
          description: Log Archive Account Id
        featureMap:
          type: object
          description: Monitored account and bucket purpose details
          additionalProperties:
            type: array
            items:
              type: string
        lastUpdatedTs:
          type: integer
          format: int64
          description: Last Updated Timestamp
      description: Model for S3 Bucket
    LoggingArchiveAccountModel:
      type: object
      required:
      - externalId
      - loggingAccountBuckets
      - loggingAccountId
      - loggingAccountName
      - loggingAccountRoleArn
      - loggingAccountRoleName
      - status
      properties:
        loggingAccountId:
          type: string
          description: CSP Cloud Account Id
        loggingAccountName:
          type: string
          description: Account Name
        loggingAccountRoleName:
          type: string
          description: Account Role Name
          readOnly: true
        loggingAccountRoleArn:
          type: string
          description: Account Role ARN
        externalId:
          type: string
          description: External Id for Account
          readOnly: true
        status:
          type: string
          description: Account status
          readOnly: true
        loggingAccountBuckets:
          type: string
          description: List of buckets associated with account
      description: Logging Archive Account Model
  requestBodies:
    BucketModel:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/BucketModel'
    LoggingArchiveAccountModel:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/LoggingArchiveAccountModel'
    LoggingAccountCFTRequest:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/LoggingAccountCFTRequest'
      description: Logging Account CFT
      required: true
  securitySchemes:
    x-redlock-auth:
      description: The x-redlock-auth value is a JSON Web Token (JWT).
      in: header
      name: x-redlock-auth
      type: apiKey