2017-08-12 73 views
0

我有以下post-processors部分封隔器模板:方式來顯示AWS API調用被封隔器後置處理器部分製成?

"post-processors": [ 
    { 
     "type": "amazon-import", 
     "ami_name": "my_image-{{user `os_version`}}", 
     "access_key": "{{user `aws_access_key`}}", 
     "secret_key": "{{user `aws_secret_key`}}", 
     "region": "us-east-1", 
     "s3_bucket_name": "my_s3_bucket", 
     "tags": { 
     "Description": "Packer build {{timestamp}}", 
     "Version": "{{user `build_version`}}" 
     }, 
     "only": ["aws"] 
    } 

我試圖調試策略/權限問題,並希望看到更多的細節,以什麼AWS API調用封隔器與亞馬遜在這兒舉行進口後處理器。

我知道了PACKER_LOG = 1環境變量,但還有什麼比這個更詳細的?這個輸出並沒有給我太多的去:

2017/08/11 23:55:24 packer: 2017/08/11 23:55:24 Waiting for state to become: completed 
2017/08/11 23:55:24 packer: 2017/08/11 23:55:24 Using 2s as polling delay (change with AWS_POLL_DELAY_SECONDS) 
2017/08/11 23:55:24 packer: 2017/08/11 23:55:24 Allowing 300s to complete (change with AWS_TIMEOUT_SECONDS) 
2017/08/12 00:29:59 ui:  aws (amazon-import): Import task import-ami-fg0qxxdb complete 
    aws (amazon-import): Import task import-ami-fg0qxxdb complete 
2017/08/12 00:29:59 ui:  aws (amazon-import): Starting rename of AMI (ami-c01125bb) 
    aws (amazon-import): Starting rename of AMI (ami-c01125bb) 
2017/08/12 00:29:59 ui:  aws (amazon-import): Waiting for AMI rename to complete (may take a while) 
2017/08/12 00:29:59 packer: 2017/08/12 00:29:59 Waiting for state to become: available 
    aws (amazon-import): Waiting for AMI rename to complete (may take a while) 
2017/08/12 00:29:59 packer: 2017/08/12 00:29:59 Using 2s as polling delay (change with AWS_POLL_DELAY_SECONDS) 
2017/08/12 00:29:59 packer: 2017/08/12 00:29:59 Allowing 300s to complete (change with AWS_TIMEOUT_SECONDS) 
2017/08/12 00:29:59 packer: 2017/08/12 00:29:59 Error on AMIStateRefresh: UnauthorizedOperation: You are not authorized to perform this operation. 
2017/08/12 00:29:59 packer:  status code: 403, request id: f53ea750-788e-4213-accc-def6ca459113 
2017/08/12 00:29:59 [INFO] (telemetry) ending amazon-import 
2017/08/12 00:29:59 [INFO] (telemetry) found error: Error waiting for AMI (ami-3f132744): UnauthorizedOperation: You are not authorized to perform this operation. 
    status code: 403, request id: f53ea750-788e-4213-accc-def6ca459113 
2017/08/12 00:29:59 Deleting original artifact for build 'aws' 
2017/08/12 00:29:59 ui error: Build 'aws' errored: 1 error(s) occurred: 

* Post-processor failed: Error waiting for AMI (ami-3f132744): UnauthorizedOperation: You are not authorized to perform this operation. 
    status code: 403, request id: f53ea750-788e-4213-accc-def6ca459113 
2017/08/12 00:29:59 Builds completed. Waiting on interrupt barrier... 
2017/08/12 00:29:59 machine readable: error-count []string{"1"} 
2017/08/12 00:29:59 ui error: 
==> Some builds didn't complete successfully and had errors: 
2017/08/12 00:29:59 machine readable: aws,error []string{"1 error(s) occurred:\n\n* Post-processor failed: Error waiting for AMI (ami-3f132744): UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: f53ea750-788e-4213-accc-def6ca459113"} 
Build 'aws' errored: 1 error(s) occurred: 

2017/08/12 00:29:59 ui error: --> aws: 1 error(s) occurred: 

* Post-processor failed: Error waiting for AMI (ami-3f132744): UnauthorizedOperation: You are not authorized to perform this operation. 
    status code: 403, request id: f53ea750-788e-4213-accc-def6ca459113 
2017/08/12 00:29:59 ui: 
==> Builds finished but no artifacts were created. 
* Post-processor failed: Error waiting for AMI (ami-3f132744): UnauthorizedOperation: You are not authorized to perform this operation. 
    status code: 403, request id: f53ea750-788e-4213-accc-def6ca459113 

==> Some builds didn't complete successfully and had errors: 
--> aws: 1 error(s) occurred: 

* Post-processor failed: Error waiting for AMI (ami-3f132744): UnauthorizedOperation: You are not authorized to perform this operation. 
    status code: 403, request id: f53ea750-788e-4213-accc-def6ca459113 

==> Builds finished but no artifacts were created. 
2017/08/12 00:30:00 [WARN] (telemetry) Error finalizing report. This is safe to ignore. Post https://checkpoint-api.hashicorp.com/v1/telemetry/packer: context deadline exceeded 
2017/08/12 00:30:00 waiting for all plugin processes to complete... 
2017/08/12 00:30:00 /usr/local/bin/packer: plugin process exited 
2017/08/12 00:30:00 /usr/local/bin/packer: plugin process exited 
2017/08/12 00:30:00 /usr/local/bin/packer: plugin process exited 

我假設這是一個政策的權限問題,但我不能告訴我是從上面的輸出丟失。

回答

0

不幸的是沒有更多的調試啓用。

我建議您檢查是否已根據docs創建了所有策略並檢查了用戶的權限。你可以通過在粘貼快捷鍵ID搜索IAM

作爲最後一個資源,使用AWS CLI可以手動完成該過程。