How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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.

Palo Alto Networks AWS Logging Accounts API is one of 741 APIs that Palo Alto Networks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include AWS Logging Accounts. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 17 operations across 11 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 15 base URLs: https://api.prismacloud.io, https://api2.prismacloud.io, https://api3.prismacloud.io, https://api4.prismacloud.io, https://api.anz.prismacloud.io, https://api.eu.prismacloud.io, https://api2.eu.prismacloud.io, https://api.gov.prismacloud.io, https://api.prismacloud.cn, https://api.ca.prismacloud.io, https://api.sg.prismacloud.io, https://api.uk.prismacloud.io, https://api.ind.prismacloud.io, https://api.jp.prismacloud.io, https://api.fr.prismacloud.io.

17 operations 11 paths 5 schemas 2 DELETE7 GET6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://{firewall}/api/
Authentication
API Key
License
Public
Resource Areas
1

Authentication & Security 1

Palo Alto Networks AWS Logging Accounts API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-redlock-auth (x-redlock-auth).

  • x-redlock-auth — The x-redlock-auth value is a JSON Web Token (JWT).

Paths & Operations 17

Across 11 paths, the API surfaces 17 operations — 2 DELETE, 7 GET, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

AWS Logging Accounts 17

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 o…

GET
/v1/cloudAccounts/awsLoggingAccounts
Get all AWS Logging Accounts
getLoggingArchiveAccounts 1 param → 200204401
POST
/v1/cloudAccounts/awsLoggingAccounts
Add AWS Logging Account
saveLoggingAccount body → 200201400401
POST
/v1/cloudAccounts/awsLoggingAccounts/cft
Generate a New CFT Template
generate-log-account-cft body → 200400
POST
/v1/cloudAccounts/awsLoggingAccounts/permissionsStatus
Get Logging Account Status
checkLoggingAccountStatus body → 200401
GET
/v1/cloudAccounts/awsLoggingAccounts/{accountId}
Get Logging Account By ID
getLoggingArchiveAccount 1 param → 200400401404
DELETE
/v1/cloudAccounts/awsLoggingAccounts/{accountId}/buckets/{bucketName}
Delete an S3 bucket
deleteBucket 2 params → 200204400401404
GET
/v1/cloudAccounts/awsLoggingAccounts/{accountId}/cft
Regenerate CFT for an Existing Account
generate-log-account-cft-existing 1 param → 200400404
POST
/v1/cloudAccounts/awsLoggingAccounts/{accountId}/cft
Regenerate CFT for New RoleName
generate-log-account-cft-role 1 param body → 200400404
GET
/v1/cloudAccounts/awsLoggingAccounts/{accountId}/role/{roleName}/externalId
Get External ID of an Account
Get External ID 2 params → 200400
PUT
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}
Update Logging Account
updateLoggingAccount 1 param body → 204400401
DELETE
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}
Delete a Logging Account by ID
deleteLoggingAccount 1 param → 204400401
GET
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets
List S3 Bucket Names
getBuckets 1 param → 200400401404
POST
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets
Add an S3 bucket
saveBucket 1 param body → 200400401404
GET
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets/{bucketName}
Get all S3 Buckets
getBucketDetails 2 params → 200401404
PUT
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/buckets/{bucketName}
Update S3 Bucket Details
updateBucket 2 params body → 200400401404
GET
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/permissionsStatus
Get Logging Account Status - GET
getLoggingAccountStatus 1 param → 200400401404
POST
/v1/cloudAccounts/awsLoggingAccounts/{loggingAccountId}/permissionsStatus
Get Logging Account Status - POST
checkLoggingAccountStatusForProvidedAccount 1 param body → 200400401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are BucketModel (7 properties), LoggingArchiveAccountModel (7 properties), LoggingAccountCFTRequest (7 properties), CloudAccountStatus (4 properties). Each schema is shown below with its type and property counts.

CloudAccountStatus
object
4 properties
LoggingAccountCFTRequest
object
7 properties
LoggingArchiveAccountModel
object
Logging Archive Account Model
7 properties 7 required
BucketModel
object
Model for S3 Bucket
7 properties 3 required
AccountStatusMessage
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

palo-alto-networks-aws-logging-accounts-api-openapi.yml Raw ↑

Other APIs Palo Alto Networks publishes across the network.

PAN-OS XML API
PAN-OS OpenConfig API
Panorama API
AutoFocus API (Deprecated)
Prisma SASE Service Status API
Cross-Platform Service Status API
SASE Authentication Service API
Expedition API (Deprecated)
VM-Series Licensing API
Palo Alto Networks 5G Deregistered Trend API
Palo Alto Networks 5G Network Interconnects and Bandwidth API
Palo Alto Networks 5G Registered Trend API
Where this information came from

This is an independent, third-party profile of Palo Alto Networks AWS Logging Accounts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.