Scan AgentCore runtimes deployed from a code zip

Plerion scans Amazon Bedrock AgentCore runtimes as part of workload scanning when the Amazon Bedrock AgentCore Runtime workload type is on. Turn it on or off with the other workload types in the integration’s settings, or in the service account’s settings. New integrations have it on. An integration set up before this workload type existed follows its AWS Lambda setting until you change it.

A runtime deployed from a container image is scanned with no extra setup.
A runtime deployed from a code zip keeps its code in an S3 bucket in your account. Plerion reads the zip only from buckets you share with it, so no other bucket is readable.

Until you share the bucket, the runtime’s Vulnerabilities, Sensitive data and SBOM tabs say that it was not scanned and name the bucket.

Do this once for each bucket that holds runtime code. Runtimes deployed with agentcore deploy use your CDK assets bucket, named cdk-<qualifier>-assets-<account>-<region>.

In the Amazon S3 console, open the bucket and choose Properties.
Under Bucket ABAC, choose Edit, turn on Enable, and save. ABAC (attribute-based access control) lets IAM policies match on the bucket’s tags.
Under Tags, add the tag PlerionAccess with the value Granted.

With the AWS CLI:

aws s3api put-bucket-abac --bucket <bucket> --abac-status Status=Enabled
aws s3control tag-resource --account-id <account-id> \
  --resource-arn arn:aws:s3:::<bucket> \
  --tags Key=PlerionAccess,Value=Granted

The runtime is scanned on the integration’s next workload scan.

Sharing a bucket lets Plerion read every object in it, not only runtime code. With agentcore deploy, that is your whole CDK assets bucket, which also holds the code and templates of your other CDK stacks. To limit what Plerion can read, keep runtime code zips in a bucket of their own and share that one.

Once ABAC is on, tags on the bucket are managed with TagResource and UntagResource. The S3 console and CloudFormation already use them. Tools that still call PutBucketTagging can no longer change the bucket’s tags.

What Plerion can read

The Plerion appliance role gets this statement in policy version v37 of the Plerion stack:

{
  "Sid": "PlerionAgentCoreCodeBucketRead",
  "Effect": "Allow",
  "Action": ["s3:GetObject", "s3:GetObjectVersion"],
  "Resource": ["arn:aws:s3:::*/*"],
  "Condition": {
    "StringEqualsIgnoreCase": { "aws:ResourceTag/PlerionAccess": "Granted" }
  }
}

S3 evaluates aws:ResourceTag only on buckets with ABAC turned on, so a bucket needs both the tag and ABAC before Plerion can read it. The role can also read each bucket’s ABAC status and tags, so a scan can tell you which of the two is missing. If the bucket is encrypted with a customer managed KMS key, Plerion decrypts through S3 with the same KMS key access you chose for the integration. Objects encrypted with the AWS managed aws/s3 key need nothing extra. This works the same way whether Plerion scans in your account, from your service account, or from a Plerion-managed scanning account. Each of them reads the code as the Plerion appliance role in the runtime’s account.

Why a runtime was not scanned

Message on the runtime	What to do
To scan this runtime, turn on Bucket ABAC and/or add the tag PlerionAccess: Granted on S3 bucket …	Follow Share a code bucket with Plerion for that bucket.
To scan this runtime, update the Plerion stack in this account to the latest template, …	Your Plerion stack is older than policy version v37. Update the AWS integration, then share the bucket.
Plerion could not read this runtime’s code at s3://…	The bucket is shared but the read was still denied. Give Plerion access to the bucket’s KMS key, and check that the bucket policy does not deny the Plerion appliance role.
This runtime’s code at s3://… no longer exists.	The zip the runtime was deployed from has been deleted or replaced. Redeploy the runtime.

Getting started

Administration

Integrations

Platform

What Plerion can read

Why a runtime was not scanned

​Share a code bucket with Plerion

​What Plerion can read

​Why a runtime was not scanned

Share a code bucket with Plerion

What Plerion can read

Why a runtime was not scanned