Identify the profiles stored in S3 Bucket?

Whatever you're done is custom, not AWS standard, you'll have to find the code doing this and look at how it works.

Oh, so you are saying the SHA256 was created cos somebody decided that way? I know that converting a user's email to SHA256 will generate the code and then have to manually compare it. COnsidering there are over 100 of such codes... can u imagine the workload? Hence, if there is a way via AWL CLI to say "ok, show me the owner/email of this profile"

matter of fact, when downloading the profile.vhdx file and opening with notepad, I can then find the [email protected] emaiol address poiting to the user's account. Again, this is still a lot of manual process .... :/

Again, someone set this up as a custom piece of code. AWS has no knowledge of what you store in the bucket. A couple of scripts should make this a small job.

Thanks Tim, may you point me in right direction and explain in what the scripting involves? would appreciate your assistance

Some kind of script to hash the profile names and outputs profile name vs sha, another that takes the sha code from "s3 ls" and matches them up. You could even tag the S3 objects with the user name, but that would defeat the purpose of the obfuscation.

... not sure how.

Best hire someone

ohhh that's an amazing suggestion ... hah

We can't teach you scripting. On SF we can help you understand a specific issue so you can work the rest out yourself. The situation you have is someone wrote some code that puts files on S3, it's not well documented, and you're trying to understand it. Given the lack of documentation you will need to reverse engineer it. The simplest way forward for you is probably to individually hash the email addresses of people who have left the company then manually match that to the S3 bucket. Alternately a lifecycle policy for archiving old data to reduce costs.

indeed ... a life cycle would solve it, just raised a nother question on that, hoping there is some guide on that part in how to create a life cycle policy to delete profiles in S3 buckets IF not utilised/accessed over 3 months.

as for the hashing ... not aware that there is ascript to hash it and really why it was requested to be hashed? Maybe cos of the URL generated when calling for the AppStream session? hmmmm I dont know nor aware how it was setup. If lifecycle can delete them after a particular time then it would safe the time indeed.

I sit in a Tesla and translated this thread with Ai: