- 最新
- 投票最多
- 评论最多
Hi JHKim,
From your description, you're using the HLS output group to send to MediaPackage. In that case it's necessary to create credential sets in the MediaLive channel configuration (open the twistie below the URL field). The IAM permissions you describe only work with the MediaPackage output group type.
Regards, Steve
Thanks for your question. The recommendation is to submit an AWS Support ticket for this and allow the Support team to determine the cause of the errors.
It seems by the errors you provided that the MediaLive is not delivering to MediaPackage. Several things need to be verified for proper operation.
How was the MediaLive Output Group defined? Using the MediaPackage or HLS selection? The MediaPackage Output Group type will automatically connect the to MediaPackage using the MediaPackage ID. The HLS Output Group type will require entry of the MediaPackage input URL, Username and Password. Depending on which Output Group you chose, recheck all the needed parameters.
There are two versions of MediaPackage currently. Both should be detailed in the MediaLive IAM Role that is used to enable MediaLive to deliver to any MediaPackage. The MediaLive IAM Role should contain similar to this regarding MediaPackage: { "Effect": "Allow", "Action": [ "mediapackage:DescribeChannel" ], "Resource": "" }, { "Effect": "Allow", "Action": [ "mediapackagev2:PutObject" ], "Resource": "" } Consider updating your IAM role.
Hello Steve, Thank you for your response! As I mentioned in the main text, I have applied the Credential set. I'm attaching an image for your reference. Would you please take a look?
Hello Mike,
It seems that based on the errors you provided, MediaLive is not delivering to MediaPackage. Several things need to be verified for proper operation.
Yes, you are correct. Thank you for clearly pointing out the cause.
How was the MediaLive Output Group defined? Using the MediaPackage or HLS selection?
I used HLS selection. HLS Output Group [1] consists of three outputs divided into 480p/720p/1080p. For HLS Output Group [2], I configured HLS group destination A to be saved in S3 for VOD. HLS Output Group [2] accumulates VOD files without any issues.
The MediaPackage Output Group type will automatically connect to MediaPackage using the MediaPackage ID.
Yes, I'm aware of that. However, I've been consistently using the HLS Output group.
The HLS Output Group type will require the entry of the MediaPackage input URL, Username, and Password. Depending on which Output Group you chose, recheck all the needed parameters.
Yes, I've double-checked several times. I'm really not sure what the root cause is.
Currently, there are two versions of MediaPackage. Both should be detailed in the MediaLive IAM Role that is used to enable MediaLive to deliver to any MediaPackage. The MediaLive IAM Role should contain something similar to this regarding MediaPackage: { "Effect": "Allow", "Action": [ "mediapackage:DescribeChannel" ], "Resource": "" }, { "Effect": "Allow", "Action": [ "mediapackagev2:PutObject" ], "Resource": "" } Consider updating your IAM role.
I'm using the v1 version. Initially, I read in the documentation that only "DescribeChannel" is required for v1, so I applied that initially. However, as problems persisted, I changed the settings to { "Effect": "Allow", "Action": [ "mediapackage:*" ], "Resource": "" }. But I still received the same error message.
I sincerely appreciate your thorough response. I have indeed carefully reviewed the information you provided, but I'm still unsure where the issue is occurring. Is there anything else that might be overlooked?
相关内容
- AWS 官方已更新 4 年前
Hello Steve, Thank you for your response! As I mentioned in the main text, I have applied the Credential set. I'm attaching an image for your reference. Would you please take a look?