Attach an Amazon Web Services (AWS) volume
Overview
Attach a volume for use on the Seven Bridges Platform's visual interface. Use this tutorial if your cloud storage provider is Amazon Web Services (AWS).
Or, learn more if the storage bucket that you want to attach is hosted on Google Cloud Storage (GCS).
Prerequisite
- An Amazon Web Services (AWS) account.
- One or more buckets on this AWS account.
Step 1: Access the Volumes Dashboard
- Click on the Data tab of the top navigation bar.
- Select Volumes from the drop-down menu.
Step 2: Choose a cloud storage provider
- On the Volumes Dashboard, click +Connect Storage.
- Select Amazon Web Services as your cloud storage provider and click Next.
Step 3: Provide S3 bucket details
- Enter your S3 bucket name, as displayed in the AWS Management Console.
- (Optional) Define a new name for the volume created from this S3 bucket on the Platform. The following characters are allowed for naming a volume: A-Z, a-z, 0-9, and “_”. An underscore can only be used between characters. The minimum number of characters is 3, while the maximum is 32.
- (Optional) Enter a description for your volume.
- Select access privileges: choose between Read only (RO) and Read and Write (RW) permissions.
- (Optional) enter a prefix. Learn more about prefixes.
- Click Next.
Step 4: Copy the policy
In this step, copy the policy and use it to create a new custom policy in the AWS Management Console.
- Copy the policy from the text box on the Seven Bridges Platform.
- Go to the AWS Management Console.
- In the top menu select Services and then choose IAM.
- In the left navigation menu select Policies.
- Click Create policy and select the JSON tab.
- Paste the policy you copied from the wizard on the Platform, replacing the existing content.
- Click Review policy and enter a policy name, e.g.
sb-access-policy
(remember this policy name as you will need to attach it later to the IAM user). - (Optional) Enter the policy description.
- Click Create policy to finish process of policy creation.
Step 5: Set up an IAM user and enter its details
Authentication of the Platform is done through AWS Identity and Access Management (IAM) services, specifically through an IAM user.
Follow these steps to set up an AWS IAM user that you will use to connect an S3 bucket (volume) to the Seven Bridges Platform:
- Go to the AWS Management Console.
- In the top menu select Services and then choose IAM.
- In the left navigation menu select Users, and then choose Add user.
- Enter the User name for the user you are creating.
- In the Access type section, select Programmatic access.
- Click Next: Permissions.
- In the Set permissions section select Attach existing policies directly.
- Use search bar to find and select the policy you created earlier (e.g.
sb-access-policy
) - Click Next: Tags.
- (Optional) Add tags to the user. These are key-value pairs that contain additional information about the IAM user and are not necessary for the process of attaching a volume to the Seven Bridges Platform.
- Click Next: Review. The user details screen is displayed. Check once again that all entered information is correct.
- Click Create user. You will see a message that the user is successfully created.
- On the confirmation screen, copy the provided Access key ID and Secret access key and use them for volume creation on the Seven Bridges Platform.
- Click Close.
- On the Seven Bridges Platform, enter Access Key ID and Secret Access Key in the corresponding fields of the volume connection wizard.
- Click Next.
Step 6: Configure additional options
In this tab, you have the option to configure the endpoint, including a FIPS endpoint if you need to use one. You can also set up server-side encryption, and AWS Canned ACL.
Step 7: Review volume details
On this tab, review the details for your volume and click Connect.
Next step
Congratulations! You've attached your volume to the Platform. You can make individual data objects within it available as "aliases" on the Platform. Aliases point to files stored on your cloud storage bucket and can be copied, executed, and organized like normal files on the Platform. We call this operation "importing". Learn more about working with aliases.
Updated about 3 years ago