Why are output groups not stoppable?

Question

We are trying to use the API to start and stop certain output groups but it does not allow us to do this. How can this be achieved?

"output_groups": [
            {
                "id": 67,
                "startable": false,
                "stoppable": false,
                "pausable": true,
                "unpausable": false
            },
            {
                "id": 68,
                "startable": false,
                "stoppable": false,
                "pausable": true,
                "unpausable": false
            }
        ],

Roman Chekmazov · Answer

You can create two events: one for udp output and another for HLS output.

Configure HLS output  in VOD mode, as well as $dt$ in folder name and then stop and start this event.

![Enter image description here](/media/postImages/original/IMl1z-BldIRT-liqJrVdAwBg)

Roman Chekmazov · Answer

I am not sure how pause will help.

But this is example of api call that is working for me:

./auth_curl.rb --login elemental --api-key API_KEY curl -H "Accept: application/xml" -H "Content-type: application/xml" -k --insecure -d "GROUP_ID" https://localhost/live_events/EVENT_ID/pause_output_group

Roman Chekmazov · Answer

I suggest to open ticket in aws support for I-frame only issue.
I-frame only manifest is there after pause only for single hls stream and disappears for ABR configuration.

Roman Chekmazov · Answer

Rollover is applicable for archive output group as this is the tool that allow to do recording.

What output types are you looking for? And what functionality do you need? What is your use case?

Roman Chekmazov · Answer

How do you configure i-frame only manifest.

As I see it still there when I pause HLS output group:

#EXTM3U

#EXT-X-VERSION:4

#EXT-X-INDEPENDENT-SEGMENTS

#EXT-X-STREAM-INF:BANDWIDTH=620952,AVERAGE-BANDWIDTH=620952,CODECS="avc1.4d4020,mp4a.40.2",RESOLUTION=1280x720,FRAME-RATE=59.940
d_1.m3u8

#EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=257676,AVERAGE-BANDWIDTH=257676,CODECS="avc1.4d4020",RESOLUTION=1280x720,URI="d_1_I-Frame.m3u8"

This is my config:

VOD Mode - is enabled

Add I-Frame Only Manifest - is enabled

Roman Chekmazov · Answer

What is your manifest looks like?

Roman Chekmazov · Answer

You might get 404 if you are using latest sotware version where https is enabled by default or you are using auth.

This is example of how to ignore ssl certificate when https is used and how to pass auth.

cd /opt/elemental_se/web/public/authentication_scripts

./auth_curl.rb --login elemental --api-key API_Key curl -X GET -H "Accept: application/xml" -H "Content-type: application/xml" -k --insecure https://IP_ADDRESS /live_events/EVENT_ID/status

Use $dt$  as name modifier and in destination url to keep files unique names and create unique folder names each time when you start event.

![Enter image description here](/media/postImages/original/IMdqhDBknoR7S_DDBRvCBZqw)

You have another option that allow to create new file (for Archive) based on the following api call and you don't need to stop channel:

curl -H "Accept: application/xml" -H "Content-type: application/xml" -d "OUTPUT_ID" http://IP_ADDRESS/live_events/EVENT_ID/rollover_output”

Roman Chekmazov · Answer

Please check this blog: https://aws.amazon.com/blogs/media/application-programming-interface-api-call-samples-for-aws-elemental-live/

[https://aws.amazon.com/blogs/media/application-programming-interface-api-call-samples-for-aws-elemental-live/](https://aws.amazon.com/blogs/media/application-programming-interface-api-call-samples-for-aws-elemental-live/)

You can't stop separate output group on Elemental Live (ex. Archive) but you can pause specific output.

re:Post Agent · Answer

Based on the information provided, I don't have specific details about why output groups are not stoppable in your particular AWS service context. The JSON snippet you've shared shows output groups with "stoppable: false" attributes, but without knowing which specific AWS service you're using, I can't provide a definitive answer.

In general, when AWS services send stop signals to resources, they typically use a SIGTERM signal first (allowing for graceful shutdown), followed by a SIGKILL if the resource doesn't terminate within the allocated time. For example, in ECS, when stopping a task, a SIGTERM signal is sent with a default 30-second timeout before SIGKILL is issued.

If you're trying to control resources like databases, you might consider using tags to identify which resources can be stopped. For Amazon Aurora DB clusters, for instance, you can tag clusters as "stoppable" and then use scripts to stop those specific clusters.

Without knowing the specific AWS service you're working with, I recommend:

1. Checking the service-specific documentation for output group management
2. Looking for alternative control mechanisms like pause/unpause (which appear to be available based on your JSON)
3. Contacting AWS Support for guidance specific to your service
4. Exploring if there are service-specific APIs or commands that might allow you to achieve your goal through a different approach  
**Sources**  
[StopTask - Amazon Elastic Container Service](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_StopTask.html)

Why are output groups not stoppable?

Add your answer

Relevant content