Amazon S3 Buckets

This section covers the following topics:

• Licensing
• Requirements
  • Encryption
• Adding an Amazon S3 Target
  • Get AWS User Security Credentials
  • Set Up Amazon S3 as a Target
• Edit Amazon S3 Target Path

Licensing

For Sitewide Licenses, all scanned Amazon S3 Targets consume data from the Sitewide License data allowance limit.

For Non-Sitewide Licenses, Amazon S3 Targets require Server & DB Licenses, and consume data from the Server & DB License data allowance limit.

See Target Licenses for more information.

Requirements

Encryption

ER2 supports Amazon S3 Buckets that use the following encryption methods:

1. Server-side encryption with Amazon S3-managed encryption keys (SSE-S3)
2. Server-side encryption with AWS KMS-managed keys (SSE-KMS)

3. Server-side encryption with customer-provided encryption keys (SSE-C)

   ER2 supports only one encryption key value for scanning Amazon S3 Buckets protected by SSE-C method. Scan the Target using different credential sets if multiple encryption key values are required to access all objects within a Bucket.

Adding an Amazon S3 Target

To add Amazon S3 Buckets as Targets:

1. Get AWS User Security Credentials
2. Set Up Amazon S3 as a Target

To scan specific objects in the Target Bucket, see Edit Amazon S3 Target Path.

Get AWS User Security Credentials

1. Log in to the AWS IAM console.
2. On the left of the page, click Users and select an IAM user with the following access permissions to the Amazon S3 Buckets that you want to scan:
   • ListAllMyBuckets
   • ListBucket
   • GetBucketLocation
   • GetObject
     
   Each Amazon S3 Bucket that is included in a scan schedule consumes one Amazon S3 Bucket license. Make sure to use credentials that have access to all Amazon S3 Buckets that are selected for a scan to avoid licenses being consumed for inaccessible Buckets.
3. On the User page, click on the Security Credentials tab. The tab displays the user’s existing Access Keys.
4. Click Create Access Key. A dialog box appears, displaying a new set of User security credentials. This consists of an Access Key ID and a Secret Access Key.
5. Click Download Credentials to save the User security credentials in a secure location, or write it down in a safe place. You cannot access this set of credentials once the dialog box is closed.
   

Set Up Amazon S3 as a Target

1. From the New Scan page, Add Targets.
2. In the Select Target Type dialog box, select Amazon S3.

3. In the Amazon S3 Details section, fill in the following fields:
   

   Field	Description
   Label	Enter a descriptive label for the Amazon S3 Target. For example, UserA_Amazon_S3.
   New Credential Label	Enter a descriptive label for the credential set.
   Access Key ID	Enter the Access Key ID obtained in Get AWS User Security Credentials. For example, AKIAABCDEFGHIEXAMPLE.
   Secret Access Key	Enter the Secret Access Key obtained in Get AWS User Security Credentials. For example, aBcDeFGHiJKLM/A1NOPQR/wxYzdcbAEXAMPLEKEY.
   Private Key	Upload the file containing the customer-provided 256-bit encryption key. Only required for Amazon S3 Buckets that use the server-side encryption with customer-provided encryption keys (SSE-C) method for object encryption. For example, my_amazon_key.txt.
   Agent to act as a proxy host	Select a Proxy Agent host with direct Internet access.

   AWS
   Please check if your AWS administrator has a set of IAM access keys for your use. AWS advises against using AWS root credentials. Use IAM whenever possible. For more information, see the AWS official documentation.
   Recommended Least Privilege User Approach

   To reduce the risk of data loss or privileged account abuse, the Target credentials provided for the intended Target should only be granted read-only access to the exact resources and data that require scanning. Never grant full user access privileges or unrestricted data access to any application if it is not required.

4. Click Test. If ER2 can connect to the Target, the button changes to a Commit button.
5. Click Commit to add the Target.
6. Back in the New Search page, locate the newly added Amazon S3 Target and click on the arrow next to it to display a list of available Buckets for the Amazon S3 user.

7. Select the Target location(s) to scan.

   Each Amazon S3 Bucket that is included in a scan schedule consumes one Amazon S3 Bucket license. Make sure to use credentials that have access to all Amazon S3 Buckets that are selected for a scan to avoid licenses being consumed for inaccessible Buckets.
   1. If "All data on new target AWSS3:<Amazon_Target_Label>" or "Amazon S3 : All buckets on new target AWSS3:<Amazon_Target_Label>" is selected, ER2 scans all objects contained in all Buckets available for the user account.
      
      For this setup, ER2 probes and retrieves the Buckets under a user account for each instance of a recurring scan. Any new Bucket added after the scan was first scheduled is included in the following scan.

   2. If only specific Buckets are selected, ER2 scans only the objects contained in the selected Buckets.
      

      For this setup, ER2 probes and retrieves only the objects in the selected Buckets. Any new Bucket added after the scan was first scheduled is not included in the following scan.
8. Click Next to continue configuring your new scan.

Edit Amazon S3 Target Path

To scan a specific object in the Amazon S3 Bucket:

1. Set Up Amazon S3 as a Target.
2. In the Select Locations section, select your Amazon S3 Bucket Target location and click Edit.

3. In the Edit Amazon S3 Bucket Location dialog, enter the Path to scan. Use the following syntax:

   Path	Syntax
   Whole Bucket	<BucketName>
   Specific folder in Bucket	<BucketName/folder_name>
   Specific file in Bucket	<BucketName[/folder_name]/filename.txt>

4. Click Test and then Commit to save the path to the Target location.