Plerion AWS integration API
In order to connect your AWS account to Plerion or update existing account, you will need, CloudFormation Template URL. Retrieve the template from GetCloudFormation template External Id of the tenant. Retrieve the External Id from Getthe external id of the tenant Plerion AWS Account Id. The value will always be 588158338731 Temporary Auth Token. Token to be passed to CloudFormation template that auto registersthe AWS integration. Retrieve the temporary auth token from Generate temporary token for creating AWS integration Plerion API URL. The value will always be au.api.plerion.com Select Capabilities. Select CSPM for CSPM only capability or ALL for both CSPM and CWPPcapability. Select KMSKeyAccessMode. When CWPP is enabled, you can choose the KMS Key access modeto facilitate Plerion's access to keys for decrypting volumes, images, and lambda code. In the ALL_KEYS mode, Plerion is granted access to all KMS keys in the account. However, you have the option to restrict access to certain keys by applying the "PlerionAccess: Denied" tag. Alternatively, the SELECTED_KEYS mode allows Plerion access solely to the KMS keys that have been tagged with "PlerionAccess: Granted". Passing the parameters to the CloudFormation template will create a new AWS integration or update existing integration. Quick StartFollow the guide to create a new AWS integration or update existing integration using curl command. Note: Replace {$PLERION_API_KEY} with your API key. Create a new AWS Integration export PLERION_API_URL=au.api.plerion.com export PLERION_API_KEY={$PLERION_API_KEY} export PLERION_AWS_ACCOUNT_ID=588158338731 # Fetch the template URL export TEMPLATE_URL=$(curl -s GET "https://$PLERION_API_URL/v1/tenant/cloudformation-templates?type=AWSAccount"-H "Authorization: Bearer $PLERION_API_KEY" | jq -r '.data.templateURL') # Generate the temporary auth token export TEMP_AUTH_TOKEN=$(curl -s -X POST "https://$PLERION_API_URL/v1/tenant/integrations/token"-H "Authorization: Bearer $PLERION_API_KEY" | jq -r '.data.token') # Fetch the external ID export EXTERNAL_ID=$(curl -s -X GET "https://$PLERION_API_URL/v1/tenant/external-id" -H "Authorization:Bearer $PLERION_API_KEY" | jq -r '.data.externalId') # Create the stack export PLERION_STACK_NAME=plerion-aws-integration aws cloudformation create-stack --stack-name $PLERION_STACK_NAME --template-url $TEMPLATE_URL --capabilitiesCAPABILITY_NAMED_IAM \ --parameters ParameterKey=ExternalId,ParameterValue=$EXTERNAL_ID \ ParameterKey=PlerionAccountId,ParameterValue=$PLERION_AWS_ACCOUNT_ID \ ParameterKey=AuthToken,ParameterValue=$TEMP_AUTH_TOKEN \ ParameterKey=Capabilities,ParameterValue=ALL \ ParameterKey=KMSKeyAccessMode,ParameterValue="ALL_KEYS" \ ParameterKey=PlerionURL,ParameterValue=$PLERION_API_URL # Wait for the stack to complete aws cloudformation wait stack-create-complete --stack-name $PLERION_STACK_NAME Update an existing AWS Integration export PLERION_API_URL=au.api.plerion.com export PLERION_API_KEY={$PLERION_API_KEY} export PLERION_AWS_ACCOUNT_ID=588158338731 # Fetch the template URL export TEMPLATE_URL=$(curl -s GET "https://$PLERION_API_URL/v1/tenant/cloudformation-templates?type=AWSAccount"-H "Authorization: Bearer $PLERION_API_KEY" | jq -r '.data.templateURL') # Generate the temporary auth token export TEMP_AUTH_TOKEN=$(curl -s -X POST "https://$PLERION_API_URL/v1/tenant/integrations/token"-H "Authorization: Bearer $PLERION_API_KEY" | jq -r '.data.token') # Fetch the external ID export EXTERNAL_ID=$(curl -s -X GET "https://$PLERION_API_URL/v1/tenant/external-id" -H "Authorization:Bearer $PLERION_API_KEY" | jq -r '.data.externalId') # Update an existing stack export PLERION_STACK_NAME=plerion-aws-integration aws cloudformation update-stack --stack-name $PLERION_STACK_NAME --template-url $TEMPLATE_URL --capabilitiesCAPABILITY_NAMED_IAM \ --parameters ParameterKey=ExternalId,ParameterValue=$EXTERNAL_ID \ ParameterKey=PlerionAccountId,ParameterValue=$PLERION_AWS_ACCOUNT_ID \ ParameterKey=AuthToken,ParameterValue=$TEMP_AUTH_TOKEN \ ParameterKey=Capabilities,ParameterValue=ALL \ ParameterKey=KMSKeyAccessMode,ParameterValue="ALL_KEYS" \ ParameterKey=PlerionURL,ParameterValue=$PLERION_API_URL # Wait for the stack to complete aws cloudformation wait stack-update-complete --stack-name $PLERION_STACK_NAME
Plerion AWS integration API is one of 13 APIs that Plerion publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include AWS integration. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.
This API exposes 3 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against a single base URL, https://{region}.api.plerion.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Plerion AWS integration API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (apiKey) (APIKey).
APIKey— Bearer API Key. For example, "Bearer {Tenant API Key}"
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
In order to connect your AWS account to Plerion or update existing account, you will need, CloudFormation Template URL . Retrieve the template from Get CloudFormation template Ext…
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ExternalId (1 property), TemporaryAuthToken (1 property), InternalServerErrorResponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Plerion 12
Other APIs Plerion publishes across the network.
This is an independent, third-party profile of Plerion AWS integration 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.