Cloud Scanning
Scan Your AWS Account
Connect Your AWS Account
SecureSlate helps you secure your Amazon Web Services (AWS) environment by scanning for misconfigurations and risky settings. The connection uses a dedicated read-only IAM user so SecureSlate never modifies your resources. After you connect, findings appear on the Checks tab of the Cloud overview page, filtered by AWS.
Connection is done in four steps: create an IAM user, set up a supplemental policy, enter credentials in SecureSlate, and name your cloud connection.
Step 1: Create IAM user in AWS
- Go to the Cloud overview page, click Connect cloud, and choose AWS to open the AWS Configuration wizard.
- In the wizard, start at Create IAM user.
- Log into your AWS account as an admin (or with permission to create IAM resources).
- In the AWS console, open IAM → Users → Add user.
- Set the username to secureslate-scanner.
- Choose Programmatic access, then click Next.
- Select Attach existing policies directly and attach the SecurityAudit policy.
- Do not complete user creation yet. Continue to Step 2 in the SecureSlate wizard to add the required supplemental policy, then return to finish the user.

Tip: Use Open IAM Users Console in the wizard to jump to the right place in AWS.
Step 2: Set up policy
- In the SecureSlate wizard, go to Set up policy.
- In AWS IAM, click Create policy (or open Policies → Create policy).
- Open the JSON tab and paste the supplemental policy provided in the wizard (it allows read-only actions such as
ses:DescribeActiveReceiptRuleSet,athena:GetWorkGroup,logs:DescribeLogGroups,logs:DescribeMetricFilters, and other describe/list actions on the required services). - Click Review policy, name it SecureSlateSupplemental, and click Create policy.
- Return to the Create user flow in AWS. Attach the new SecureSlateSupplemental policy to the secureslate-scanner user, then click Next: Tags.
- Add tags if needed, then click Create user.
- Save the Access key ID and Secret access key—you will need them in the next step. You cannot view the secret again after leaving the page.

Note: The IAM user has only read-only permissions. SecureSlate uses it to scan configuration and will not change any resources.
Step 3: Connect accounts
- In the SecureSlate wizard, go to Connect accounts.
- Enter the Access key ID and Secret access key for the secureslate-scanner user.
- Click Continue.
Use the credentials you saved when creating the user. Never share your secret access key.

Step 4: Name your cloud connection
- In the wizard, go to Name your cloud connection.
- Enter a Cloud name (for example, “AWS Production” or “AWS Cloud Infrastructure”).
- Select the purpose of the connection (e.g., production, staging, development) from the dropdown.
- Click Complete Configuration.

After you complete the flow, SecureSlate will start scanning your AWS resources and typically report misconfigurations within a few minutes.
Prerequisites
- AWS account with permission to create IAM users and policies.
- Permission to attach the SecurityAudit managed policy and to create a custom policy (e.g., SecureSlateSupplemental).
- Ability to create access keys for the IAM user and to paste them into SecureSlate.