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

Conjur docker-compose fails to initialize Cloudwatch #251

Open
2 tasks
fyllekanin opened this issue Aug 25, 2022 · 0 comments
Open
2 tasks

Conjur docker-compose fails to initialize Cloudwatch #251

fyllekanin opened this issue Aug 25, 2022 · 0 comments

Comments

@fyllekanin
Copy link

Summary

Conjur fails to start with docker-compose after reboot of system because of Cloudwatch log stream InvalidSignatureException, Signature expired 20220624T005716Z is now earlier than 20220624T005801Z (20220624T010301Z - 5 min.)

Steps to Reproduce

  1. Have conjur running with docker-compose on an EC2 in AWS
  2. Restart the machine
  3. When machine starts up again with autostart service (systemd) conjur fails to initialize logging driver
  4. See error

Expected Results

Conjur be able to start without issue

Actual Results

docker-compose[1420]: ERROR: for conjur_server Cannot start service conjur: failed to initialize logging driver: failed to create Cloudwatch log stream: InvalidSignatureException: Signature expired: 20220624T005716Z is now earlier than 20220624T005801Z (20220624T010301Z - 5 min.)
docker-compose[1420]: status code: 400, request id:

Reproducible

  • [x ] Always
  • Sometimes
  • Non-Reproducible

Version/Tag number

1.11.6

Environment setup

  • AWS
    Running inside a EC2 machine dedicated for cyberark/conjur server and cyberark/conjur-cli within a docker-compose.

Additional Information

If I make an AMI of the current running machine and create a new machine from it with identical setup it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants