# Ray head stuck on ssh when implementing Cloudwatch

**URL:** <https://discuss.ray.io/t/ray-head-stuck-on-ssh-when-implementing-cloudwatch/22127>\
**Category:** Ray Clusters\
**Created:** [March 25, 2025, 6:48am UTC](https://discuss.ray.io/t/ray-head-stuck-on-ssh-when-implementing-cloudwatch/22127 "2025-03-25T06:48:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![christina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/christina/32/7542_2.png) [@christina](https://discuss.ray.io/u/christina)\
**Post date:** [March 28, 2025, 1:49am UTC](https://discuss.ray.io/t/ray-head-stuck-on-ssh-when-implementing-cloudwatch/22127/2 "2025-03-28T01:49:39Z")

</div>

Hi doyen and welcome to the Ray community!

Since it connects okay without issues once Cloudwatch is removed I’m guessing it’s an issue with the integration between Cloudwatch \<\> Ray \<\> AWS?

1. Does your Ray cluster have the proper IAM permissions from AWS to talk to the Cloudwatch instance? Mostly create/write permissions to allow nodes to log to CloudWatch.
2. Are there any network or firewall restrictions to Cloudwatch?
3. Does the security group related with Ray allow ssh access and the key pairing is working?

Are there any error messages or is it just stuck with `waiting-for-ssh`?  
Also, is there any code where we can reproduce this issue? Can you paste your updated YAML config (make sure you censor out any sensitive info tho)!

Here’s a few other folks who have run into this issue (albeit not with CloudWatch specifically), maybe it can help debug. Sorry I wasn’t more help!

- [[Ray Cluster] Ray cluster stuck after using ray up · Issue #38718 · ray-project/ray · GitHub](https://github.com/ray-project/ray/issues/38718)
- [Worker nodes stuck in "waiting-for-ssh"](https://discuss.ray.io/t/worker-nodes-stuck-in-waiting-for-ssh/6677)

---

_[View the full topic](https://discuss.ray.io/t/ray-head-stuck-on-ssh-when-implementing-cloudwatch/22127)._