Horotonworks Data Cloud error autoscaling token expired

[#1]

I am provisioning a cluster using version 1.14.0 of Hortonworks Data Cloud. The Autoscaling status slider is in the off position, but cluster provisioning fails with the following error on the auto scaling token:

Infrastructure creation failed. Reason: com.amazonaws.AmazonServiceException: The security token included in the request is expired (Service: AmazonAutoScaling; Status Code: 403; Error Code: ExpiredToken; Request ID: cf2aebb0-2cec-11e7-8985-4100dda4669c)

The autoscaling tab on the failed cluster in the cloud controller, shows the cluster trying to autoscale to 3 nodes:

[#2]

Ok - AWS cloudformation completed in under four minutes, but HDP is stuck on creating infrastructure. No clue what it is doing, just says Building and only one entry in the event history

[#3]

Failed, see attached

[#4]

cluster-6-4

Other Actions Update Stack

Stack name:

cluster-6-4

Stack ID:

arn:aws:cloudformation:us-east-1:231904212587:stack/cluster-6-4/7da49330-301a-11e7-a663-503aca4a58fd

Status:

CREATE_COMPLETE

Status reason:

IAM Role:

Description:

Outputs

Resources

Events

2017-05-03	Status	Type	Logical ID	Status reason
09:10:00 UTC-0700 CREATE_COMPLETE AWS::CloudFormation::Stack cluster-6-4 09:09:55 UTC-0700 CREATE_COMPLETE AWS::AutoScaling::AutoScalingGroup AmbariNodesmaster 09:09:55 UTC-0700 CREATE_COMPLETE AWS::AutoScaling::AutoScalingGroup AmbariNodescompute 09:09:54 UTC-0700 CREATE_COMPLETE AWS::AutoScaling::AutoScalingGroup AmbariNodesworker

[#5]

Okay, we'll need to see the Cloudbreak logs. You can get it by ssh-ing to the controller machine and get it with the command: "cbd logs cloudbreak". You can also check the autoscaling tab on the EC2 console (Scaling history) and check if the VMs are available and healthy. @cduby @DL

[#6]

@cduby @DL Did you end up getting past this error and successfully creating a cluster?

[#7]

@Dominika Bialek Thanks for checking in. I ended up switching regions.