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.

Sign up for GitHub

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

Jump to bottom

SQS Sensor with EC2 Role #120

Closed
satellite-no opened this issue Jun 9, 2022 · 1 comment · Fixed by #121
Closed

SQS Sensor with EC2 Role #120

satellite-no opened this issue Jun 9, 2022 · 1 comment · Fixed by #121

Comments

@satellite-no
Copy link
Contributor

satellite-no commented Jun 9, 2022 •
edited
Loading

Does the AWS SQS sensor work when the provided aws.yaml is set to the below? Meaning the ec2 instance role is being used? I keep getting an error for InvalidClientTokenId.

---
region: "us-east-1"
aws_access_key_id: None
aws_secret_access_key: None
st2_user_data: ""

sqs_sensor:
  input_queues:
    - stacstormAlert.fifo

sqs_other:
  max_number_of_messages: 1

Error:

2022-06-09 20:50:27,308 ERROR [-] Sensor "AWSSQSSensor" run method raised an exception: An error occurred (InvalidClientTokenId) when calling the GetCallerIdentity operation: The security token included in the request is invalid..
@satellite-no
Copy link
Contributor Author

I should also mention that the aws.sqs_receive_message and aws.sqs_send_message actions work as expected.

@satellite-no satellite-no mentioned this issue Jun 10, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

if sqs sensor config None set to None
1 participant
@satellite-no