Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS tokens #26

Closed
shortstack opened this issue Dec 12, 2018 · 0 comments
Closed

AWS tokens #26

shortstack opened this issue Dec 12, 2018 · 0 comments

Comments

@shortstack
Copy link
Contributor

Hi,

Attempting to use the AWS keys

I have canarytokens running in Docker on Ubuntu 16.04, sitting behind an ELB, 443/HTTPS pointing to 80/HTTP/nginx.

All of the other tokens I've tried are working fine.

[default]
aws_access_key_id = $GENERATEDACCESSKEYID
aws_secret_access_key = $GENERATEDACCESSKEY
region = us-east-2
output = json

I put the above in ~/.aws/credentials

Ran aws configure, picked it up no problem

Ran the following:

aws iam create-user --user-name TestMePlease
aws s3 ls
aws ec2 describe-instances

And probably a few others, have waited about an hour, no alert and nothing in the logs on my end.

I know this piece is hosted on your lambda. I tried the version on canarytokens.org and got an alert about 20 minutes later (which you mentioned on your blog).

Wondering where the disconnect is. Thank you.

wleightond pushed a commit that referenced this issue May 5, 2023
Co-authored-by: Benjamin <benjamin@thinkst.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant