Stream created from ExecuteCommand have limited buffor?

Question

Hello,

I wanted to use the ExecuteCommand function in Step Functions to execute a command that contained a very large amount of output. However, the command was stopping after some time. After logging into the ECS container, I noticed that the command was practically not using resources. When I ran it normally everything worked. In addition, when I used session-manager-plugin to connect to the Stream of command execution (I took the parameters from Step Functions) it executed correctly. Is there any limit for the StreamURL created and is it possible to bypass this limit somehow ?

Answer

Greetings,

I understand that you are currently trying to use the ExecuteCommand function in Step Functions to execute a command that has a very large amount of output to be displayed. However, the command is failing and you are unable to view the entire output.

Please allow me to mention that as of today there is a limit for the StreamURL created by the ExecuteCommand function in Step Functions. The limit is 256 KB. This means that if the output of your command is larger than 256 KB, the StreamURL will be truncated and the command will stop.

Unfortunately, there is no way currently available to bypass this limit.

However, there is a work around to this problem which i guess you have already tried and implemented it which is by using the session-manager-plugin to connect to the Stream of command execution. This plugin will allow you to view the entire output of the command, even if it is larger than 256 KB.

I hope this helps!

Stream created from ExecuteCommand have limited buffor?

Relevant content