s3./ in cfn-init.log,Įnsure the deployment S3 bucket name is correct and that the S3 object key name of authorization files and SSL certificates are correct. If you see the message Error encounteredĭuring build of config: Failed to retrieve.The following provides tips to troubleshoot stack creation failure using some of the error messages you may see in the log files:
However, this means you need to clean up the CloudWatch log groups when you no longer need them. To prevent this and, therefore, provide you with the log files you need to troubleshoot stack creation failures, the Esri sample CloudFormation templates change this setting so the CloudWatch log groups are not deleted. Note that if stack creation fails before any instances are launched, a log group might not be created.īy default, AWS deletes CloudWatch log groups if stack creation fails. If stack creation fails, go to the CloudFormation Resources list in the AWS Management Console to find the log group. If CloudFormation stack creation succeeds, the stack output parameters provide a link to the log group in the AWS Management Console. For example, a log stream of i-c8244b6f/chef-run.log is the Chef configuration management tool log file for EC2 instance i-c8244b6f. This allows you to identify to which EC2 instance the log file pertains. The CloudWatch log group contains log streams, which include the ID of the instance with the log file name. You won't be able to see the log messages for these regions in the AWS Management Console, but you can still check the log files on the instance. Some AWS regions, such as GovCloud and China region, do not have logging implemented.
0 kommentar(er)
