You can disconnect Parsivex from your AWS account at any time. Revoking access is immediate — no waiting period, no support ticket required.
Delete the IAM role in AWS
The fastest way to revoke access is to delete the read-only IAM role from your AWS account:
Open the IAM console
Sign in to the AWS Management Console and navigate to IAM → Roles.
Find your Parsivex role
Search for the role you created during onboarding (commonly named
ParsivexReadOnlyor similar).Delete the role
Select the role, choose Delete, and confirm. If you deployed via CloudFormation, you can delete the entire stack instead.
Once the role is deleted, Parsivex cannot assume it. Any in-progress scan will fail, and no new scans can run against that AWS account until you reconnect.
Deleting the IAM role revokes AWS access instantly. This is by design — you stay in full control of when Parsivex can read your account.
Remove the connection in Parsivex (optional)
Deleting the IAM role is sufficient to stop all AWS access. You can also remove the connection record from Parsivex:
- Go to Integrations → AWS connections
- Click Remove on the connection you want to disconnect
- Confirm the removal
Removing the connection cleans up your Parsivex dashboard but does not affect the IAM role in AWS. If you only remove the connection in Parsivex without deleting the role, the role still exists in your account (harmless, but unused).
What happens to your Parsivex data
Revoking AWS access and deleting Parsivex data are separate actions:
| Action | AWS access | Parsivex scan data |
|---|---|---|
| Delete IAM role | Revoked immediately | Retained — past scans and reports remain in your account |
| Remove AWS connection in Integrations | Revoked (role must also be deleted for full revocation) | Connection record removed; scan history retained |
| Delete your Parsivex account | N/A — you must still delete IAM roles manually | Permanently deleted — all workspaces, scans, and reports removed |
Past scan results, findings, and reports stay in your Parsivex account after you revoke AWS access. This lets you review historical savings data even after disconnecting. If you want that data removed too, delete your Parsivex account from Settings → Danger zone.
Deleting your Parsivex account does not remove IAM roles from your AWS account. You must delete those manually in the AWS console. See account deletion scope for details.
Re-connecting later
You can reconnect Parsivex to the same AWS account at any time:
- Create a new read-only IAM role (the previous role was deleted, so you start fresh)
- Use the External ID shown in your Parsivex dashboard during onboarding
- Paste the new Role ARN into Integrations or the onboarding wizard
- Run a new scan
Your previous scan history remains in Parsivex if you did not delete your account. New scans will produce fresh findings based on current resource state.
Related articles
- What data can Parsivex see? — full breakdown of read permissions
- Security FAQ — data retention, storage location, and account deletion