AWS Elastic Transcoder：找不到管道 [英] AWS Elastic Transcoder: Pipeline not found

问题描述

我已配置了Elastic Transcoder管道，它已成功处理了通过AWS管理控制台创建的作业。但是，使用Ruby API时，似乎不存在管道：

I have an Elastic Transcoder pipeline configured, and it has successfully processed jobs created via the AWS Management Console. However, when using the Ruby API, the pipeline doesn't appear to exist:

et = AWS::ElasticTranscoder::Client.new
puts et.list_pipelines.inspect
# {:pipelines=>[], :request_id=>"e9e5ae2b-ca43-11e3-969d-530832cf62dd"}

类似地，使用正确的：pipeline_id调用 create_job 引发错误，声称AWS返回了该管道ID的404。

Similarly, calling create_job with the correct :pipeline_id raises an error, claiming AWS returned a 404 for that pipeline ID.

根据文档，这不会 not 指示权限错误。权限错误应返回403。但是请确定，我将IAM用户的权限设置为超级用户，如下所示：

According to the documentation, this does not indicate a permissions error. A permissions error should return a 403. But just to be sure, I set the IAM user's permissions to superuser as follows:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "*",
      "Resource": "*"
    }
  ]
}

为什么找不到管道？

推荐答案

您必须连接到相同的AWS管道所在的区域。要查找管道的区域，请执行以下操作：

You have to connect to the same AWS region in which your pipeline resides. To find out the pipeline's region:

1. 转到AWS管理控制台中的管道列表。


2. 单击管道图标。这应该打开管道的详细信息。


3. 在ARN字符串中查找区域。例如， us-west-2 。

1. Go to the list of pipelines in the AWS Management Console.
2. Click the magnifying glass icon for your pipeline. This should open the pipeline's details.
3. Find the region in the ARN string. For example, us-west-2.

然后，当您连接时到AWS上，是这样的：

Then, when you connect to AWS, do it like this:

AWS.config({
  :access_key_id => 'abc',
  :secret_access_key => '123',
  :region => 'us-west-2' # Or whatever your region is
})

这篇关于AWS Elastic Transcoder：找不到管道的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！