Skip to main content
All CollectionsConnectorsCloud
Defining an S3 Bucket for Vulcan Integration
Defining an S3 Bucket for Vulcan Integration

How to define S3 bucket

Updated over 10 months ago

About

In this quick how-to, you'll learn the step-by-step process of defining an Amazon S3 (Simple Storage Service) bucket for use with Vulcan. This involves creating a specific AWS (Amazon Web Services) IAM (Identity and Access Management) policy, assigning it to a user, and then using those credentials in Vulcan.

Steps

  1. Create an IAM Policy in AWS:

    • Navigate to AWS Management Console.

    • Go to IAM service.

    • Select 'Policies' from the sidebar.

    • Click on 'Create policy'.

    • Define a policy with the following permissions:

      • s3:ListBucket

      • s3:GetBucketLocation

      • s3:PutObject

      • s3:GetObject

      • s3:DeleteObject

    • These permissions will allow the specified actions on your S3 bucket.

  2. Assign the Policy to a User:

    • After creating the policy, assign it to the user whose Access Key ID and Secret Access Key you plan to use.

    • Navigate to 'Users' in the IAM service.

    • Select the user and attach the newly created policy.

  3. Adding S3 Bucket to Vulcan:

    • With the policy in place and assigned, you're ready to add the S3 bucket to Vulcan.

    • Use the credentials (Access Key ID and Secret Access Key) of the user with the attached policy.

    • In Vulcan, navigate to the section where you can add a new S3 bucket.

    • Enter the required details of the S3 bucket you wish to add.

  4. Test the Connection:

    • Before finalizing, use the 'Test Connection' feature in Vulcan to ensure that the integration is set up correctly.

    • This step is crucial to verify that Vulcan can successfully connect to and interact with the S3 bucket.

  5. Finalize the Setup:

    • Once the connection test is successful, click on 'Add Bucket' to complete the process.

Important Considerations:

  • Policy Permissions: Ensure that the policy permissions align with your organization's security policies and the intended use of the S3 bucket.

  • User Credentials: Be cautious with the user credentials. They should be handled securely and should not be shared.

  • Bucket Naming and Access: Make sure the S3 bucket name is correctly entered and that it is accessible with the provided credentials.

Did this answer your question?