我使用的是AWS PHP SDK将文件上传到S3则c它移植$ C $有弹性横贯codeR。

先通过一切正常，该putobject命令会覆盖S3的旧文件（始终命名为相同）：

  $ S3-＆GT; putObject（[
      '斗'=＆GT;配置::得到（'app.aws.S3.bucket），
      '关键'=＆GT; $关键，
      '的SourceFile'=＆GT; $路径，
      元数据=＆GT; [
        '标题'=＆GT;输入::获得（标题）
      ]
    ]）;
 

但是创建第二个转码作业时，我得到的错误：

 指定的对象不能保存在指定的水桶，因为对象由该名称已经存在
 

跨codeR角色具有完全S3访问。有没有办法解决这个或将我以前的跨codeD删除使用SDK每次文件？

我的创造就业：

  $结果= $跨codeR-＆GT; createJob（[
      PipelineId'=＆GT;配置::得到（'app.aws.ElasticTrans coder.PipelineId'），
      输入=＆GT; [
        '关键'=＆GT; $关键
      ]
      输出=＆GT; [
        '关键'=＆GT; 视频/'.$用户。'/'。$ output_key，
        ThumbnailPattern'=＆GT; 视频/'.$用户。/拇指{}算'，
        '旋转'=＆GT; 0，
        'presetId'=＆GT;配置::得到（'app.aws.ElasticTrans codeR，presetId'）
      ]
    ]）;
 

解决方案

在亚马逊弹性横贯codeR服务文档，这是这里的预期的行为：http://docs.aws.amazon.com/elastictrans$c$cr/latest/developerguide/job-settings.html#job-settings-output-key.

如果您的工作流程需要您覆盖相同的密钥，那么它听起来像你应该有作业输出独特的地方，然后发出一个S3 CopyObject操作来覆盖旧的文件。

I'm using the AWS PHP SDK to upload a file to S3 then trancode it with Elastic Transcoder.

First pass everything works fine, the putobject command overwrites the old file (always named the same) on s3:

$s3->putObject([
      'Bucket'     => Config::get('app.aws.S3.bucket'),
      'Key'        => $key,
      'SourceFile' => $path,          
      'Metadata'   => [
        'title'     => Input::get('title')
      ]
    ]);

However when creating a second transcoding job, i get the error:

  The specified object could not be saved in the specified bucket because an object by that name already exists

the transcoder role has full s3 access. Is there a way around this or will i have to delete the files using the sdk everytime before its transcoded?

my create job:

    $result = $transcoder->createJob([
      'PipelineId' => Config::get('app.aws.ElasticTranscoder.PipelineId'),
      'Input' => [
        'Key' => $key
      ],
      'Output' => [
        'Key' => 'videos/'.$user.'/'.$output_key,
        'ThumbnailPattern' => 'videos/'.$user.'/thumb-{count}',
        'Rotate' => '0',
        'PresetId' => Config::get('app.aws.ElasticTranscoder.PresetId')       
      ],
    ]);

The Amazon Elastic Transcoder service documents that this is the expected behavior here: http://docs.aws.amazon.com/elastictranscoder/latest/developerguide/job-settings.html#job-settings-output-key.

If your workflow requires you to overwrite the same key, then it sounds like you should have the job output somewhere unique and then issue an S3 CopyObject operation to overwrite the older file.