# Level 3 Like Level 2, let’s see what we can list from the bucket. ``` s3 ls s3://level3-9afd3927f195e10225021a578e6f78df.flaws.cloud/ --profile flaws ```

After listing the contents of the bucket, we can see that it contains a .git repository. This is worth looking into because .git repositories can contain sensitive data. Using the sync command, we can download the bucket's contents locally. First, we need to create a folder to place the contents. ``` mkdir /home/kali/Desktop/flaws ``` Next, we will download the s3 bucket to the new folder that was just created. ``` aws s3 sync s3://level3-9afd3927f195e10225021a578e6f78df.flaws.cloud/ /home/kali/Desktop/flaws --profile flaws ```

In the flaws folder that was just created, we want to list the contents to ensure that it was properly downloaded. As we can see here, it matches what we listed earlier above.

Since we are looking at a .git repository, we can use the `git log` command to view a record of the commits. We can see that there are two commits and one of them has a comment left by a previous user. *Note: The alphanumeric string after “commit” is the hash of the git repository at the time of commit.*

We can now use the `git checkout` command to navigate between branches. Let’s take a look at the first commit and list the contents. We can see here that there isn’t anything interesting.

Listing contents of the folder after navigating to the .git branch

Now, let’s do the same thing for the next commit and list the contents.

When we list the folder contents, there is an access\_keys.txt file.

To read the file, we will use the `cat` command. It looks like there is an access\_key and secret\_access\_key value saved to the file. We can use this to configure a new AWS profile.

Configuring a new AWS profile for Level 3

Now that we have access, let’s see what we can find by listing the bucket contents. Great, we’ve found buckets to the next levels!

Let's navigate to Level 4