Scanning AWS S3 buckets

We would like to have the ability to use temporary credentials to access different S3 buckets, in different AWS accounts without needing static AWS access key and secret pairs to accomplish.

How are some of the other financial institutions scanning their AWS environment with Collibra?

manrichkotze

Posted 5 years ago · Edited 1 year ago·Last reply 2 years ago

6 comments

Ritesh Mody

·4 years ago · Edited

Hey @manrich.kotze, we are using role based access to scan S3 buckets - as within our org, each team has their own AWS accounts and accessing S3 buckets through credentials (secrets) is a big NO!! I’d be happy to share more details with you on this if you are still looking for different options. Thanks!

hainguyen

·2 years ago · Edited

Hi Ritesh,

we successfully deployed Edge in EKS. However, the challenge we are currently facing lies in setting up connections and capabilities for S3, especially with regards to EC2 instances deployed in EKS & Edge environments. The existing documentation lacks clear instructions on these specific configurations (link)

Could you please elaborate how to set up AWS S3 connections and capabilities on EDGE?

Ritesh Mody

·4 years ago · Edited

Ritesh Mody

·2 years ago · Edited

Apologies for the delayed response! We were able to setup our connections via job server that was installed on EC2; haven’t tried this via Edge - Edge installation is WIP for us. Please let me know if you’d still like me to share the details on how we configured our access and I’d be happy to help. Thanks!

Alexandra Jorgenson

Admin4 years ago · Edited

@manrich.kotze, are you still interested in feedback on this issue because if so, I have some ways to try and get you some responses :)!

manrichkotze

OP4 years ago · Edited

Hi Kirsten, we are good thank you. We were able to get it right via using Athena. We also implemented a method of using temporary credentials when connecting and scanning. We enabled profiling and classification as well.