You can use the AWS S3 Flow Logs API for AWS S3 onboarding for organization and standalone accounts on all supported stacks.
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
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/palo-alto-networks:palo-alto-networks-onboarding-aws-s3-flow-logs-api"curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
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.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
contact: {}
description: 'Access Keys are a secure way to enable programmatic access to the Prisma Cloud API. By default, only
the System Admin has API access and can enable API access for other administrators. If you have API access,
you can create up to two access keys. Create an access key for a limited time period and regenerate your API
keys periodically to minimize exposure and follow security best practices.'
title: Prisma Cloud Access Keys API Overview Onboarding AWS S3…
version: Latest
servers:
- url: https://api.prismacloud.io
- url: https://api2.prismacloud.io
- url: https://api3.prismacloud.io
- url: https://api4.prismacloud.io
tags:
- description: 'You can use the AWS S3 Flow Logs API for AWS S3 onboarding for organization
and standalone accounts on all supported stacks.'
name: Onboarding AWS S3 Flow Logs
paths:
/cloud-accounts-manager/v1/cloud-accounts/aws/{accountId}/features/aws-flow-logs/s3:
get:
description: Fetches AWS S3 Flow Log feature details of monitored account.
operationId: get-aws-s3-flowlog
parameters:
- in: path
name: accountId
required: true
schema:
type: string
responses:
'200':
content:
application/json; charset=UTF-8:
schema:
$ref: '#/components/schemas/AwsS3FlowLogsModel'
description: success
'400':
description: invalid_parameter_value / bad_request
'401':
description: unauthorized_access
'404':
description: account_not_exist_or_disabled / AWS Flow Logs S3 feature not configured
'500':
description: internal_error
security:
- x-redlock-auth: []
summary: Fetches AWS S3 Flow Log details
tags:
- Onboarding AWS S3 Flow Logs
patch:
description: Saves AWS S3 Flow Log feature details of monitored account.
operationId: save-aws-s3-flowlog
parameters:
- description: 1 Hour format
in: query
name: isHourlyFormat
required: true
schema:
type: boolean
- in: path
name: accountId
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AwsS3FlowLogsModel'
description: AWS S3 Flow Logs feature
required: true
responses:
'201':
description: success
'400':
description: invalid_parameter_value / bad_request / missing_required_parameter / Logging account and monitored account are in different partition / logging_account_bucket_not_found / AWS Flow Logs S3 feature not supported for account
'401':
description: unauthorized_access
'404':
description: account_not_exist_or_disabled / logging_account_not_exists
'500':
description: internal_error
security:
- x-redlock-auth: []
summary: Saves AWS S3 Flow Log details
tags:
- Onboarding AWS S3 Flow Logs
/cloud-accounts-manager/v1/cloud-accounts/aws/{accountId}/features/aws-flow-logs/s3/status:
post:
description: Checks AWS S3 Flow Log status of monitored account.
operationId: check-aws-s3-flowlog
parameters:
- description: 1 Hour format
in: query
name: isHourlyFormat
required: true
schema:
type: boolean
- in: path
name: accountId
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AwsS3FlowLogsLoggingAccountsModel'
description: AWS S3 Flow Logs feature
required: true
responses:
'200':
content:
'*/*':
schema:
$ref: '#/components/schemas/CloudAccountStatus'
description: success
'400':
description: invalid_parameter_value / bad_request / AWS Flow Logs S3 feature not supported for account
'401':
description: unauthorized_access
'404':
description: invalid_account_id_format
'500':
description: internal_error
security:
- x-redlock-auth: []
summary: Checks AWS S3 Flow Log status
tags:
- Onboarding AWS S3 Flow Logs
components:
schemas:
AccountStatusMessage:
properties:
message:
type: string
staticMessage:
type: boolean
type: object
AwsS3FlowLogsLoggingAccountsModel:
description: Model for AWS S3 Flow Logs Feature Logging Accounts Configuration
properties:
awsS3FlowLogsLoggingAccountId:
description: Logging Account Internal ID
format: int32
type: integer
bucketIds:
description: List of bucket Ids for the feature
items:
format: int32
type: integer
type: array
buckets:
description: List of buckets for the feature
items:
type: string
type: array
loggingAccountId:
description: Account ID of the Logging Account
type: string
type: object
CloudAccountStatus:
properties:
id:
type: string
name:
type: string
status:
type: string
statusMessage:
$ref: '#/components/schemas/AccountStatusMessage'
type: object
AwsS3FlowLogsModel:
description: Model for AWS S3 Flow Logs Feature Configuration
properties:
accountId:
description: Prisma Account ID from cloud_account table
format: int32
type: integer
loggingAccounts:
description: List of logging accounts with selected buckets for the given feature
items:
$ref: '#/components/schemas/AwsS3FlowLogsLoggingAccountsModel'
type: array
type: object
securitySchemes:
x-redlock-auth:
description: The x-redlock-auth value is a JSON Web Token (JWT).
in: header
name: x-redlock-auth
type: apiKey