In
order for Prisma SaaS to enforce your custom exclusion list, you
must add the bucket names after you onboard the Amazon S3 app—but
before
you
start scanning.
Otherwise, absent any bucket names, Prisma SaaS scans
All
S3
buckets, then displays those unwanted assets in the Prisma SaaS
web interface. If you add the bucket names
after
the scan
begins, Prisma SaaS stops scanning those buckets moving forward,
but those unwanted assets remain in Prisma SaaS. To remove those
assets, you must delete the Amazon S3 app and repeat the onboarding
process. Similarly, you can delete a bucket name from exclusion,
but previously discovered assets remain unless you
delete the cloud app.