- 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.
public.ecr.aws are not read. Plerion also skips an image when its COPY or ADD layers are over 256 MiB each, compressed, or 1 GiB together. When an image is skipped, a read fails, or a read cut short by a limit finds no tools, the tab keeps the tools from the last full read. Plerion reads tools from AgentCore runtimes only. Lambda web functions get the same findings scan as before.
Lambda web functions keep their code the same way: a zip in an S3 bucket in your account, named on each revision. Plerion scans web functions under the AWS Lambda workload type, with no setting of their own, and reads their code from shared buckets exactly as described here. Everything below applies to a web function as it does to a runtime, with the messages saying “web function”.
Share a code bucket with Plerion
Do this once for each bucket that holds runtime or web function code. Runtimes deployed withagentcore deploy use your CDK assets bucket, named cdk-<qualifier>-assets-<account>-<region>. For a web function, that is the bucket in the revision’s CodeUri (SAM) or S3Object (CloudFormation); the aws lambda-web deploy command uploads the package to an S3 bucket in your account as well.
- 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
PlerionAccesswith the valueGranted.
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: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.