ParkEunsoo
Reputation: 21
AWS Systems Manager Run Command execution timeout when I use nohup &
AWS Systems Manager Run Command
when I use command nohup & it returns execution timeout
Does AWS Systems Manager Run command not supports background process?
How to fix this problem?
Upvotes: 2
Views: 684
Answers (0)
Related Questions
- Can we run command as background process through AWS SSM?
- Schedule of Run Command in AWS Systems Manager
- Bash- Running aws ec2 run-instances in background
- Why my AWS Lambda function doesn't wait for SSM Send Command (which runs Shell script remotely on EC2) to complete?
- Lifetime cycle config is longer than 5 minutes, nohup command not working
- AWS ssm send-command : modify timeout in CLI
- Have SSM start-session use bash
- SSM Automation Run Command is not longer than default 3600 seconds
- SSM send-command with Powershell does not complete until background job finishes
- Terminate AWS EC2 instance when SSM Run Command status changes