Comment afficher les appels d'API AWS effectués par Packer dans la section post-processeurs?

Question

J'ai un modèle Packer avec la section post-processors suivante:

"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"] 
    } 

Je suis en train de déboguer un problème de politique/autorisations et je voulais voir plus de détails sur ce que l'API AWS appelle Packer fait ici avec l'amazone -import Post-Processor.

Je connais la variable d'environnement PACKER_LOG = 1, mais y a-t-il quelque chose de plus détaillé que celui-ci? Cette sortie ne me donne pas beaucoup à continuer:

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 

Je suppose que c'est un problème d'autorisations de politique, mais je ne peux pas dire ce que je suis absent de la sortie ci-dessus.

Answer 1

Malheureusement, il n'y a plus de débogage à activer.

Je vous recommande de vérifier que vous avez créé toutes les règles conformément au docs et de vérifier les droits de l'utilisateur. Vous pouvez le faire en collant l'ACCESS KEY ID dans Search IAM.

En tant que dernière ressource, il peut être utile de passer par le processus manuellement avec le cli AWS.

Answer 2

pas dans les Packer, mais vous pouvez utiliser AWS CloudTrail pour voir que des API ont été appelés:

https://aws.amazon.com/cloudtrail/