Creating default IAM account fails

[lukklin]

Hello everybody,

I would like to try the Veeam Backup for AWS, the cloud formation template was running successfully, but inside the software, it seems to fail during the creation of the default IAM account:

Case ID: 03894503

Has anyone an idea, what to check?

Thanks!
Lukas

[nielsengelen]

Best would be to wait for feedback from support here.

[Mike Resseler]

Hey Lukas,

Where did it exactly fail? Somewhere in this procedure? https://helpcenter.veeam.com/docs/vbaws ... tml?ver=10

[lukklin]

Hi Mike,

It fails at this point: https://helpcenter.veeam.com/docs/vbaws ... tml?ver=10

Because there is no default IAM user been created during install.

[Mike Resseler]

OK. So you need to add an IAM role with the necessary rights. Maybe there is an issue?

See here: https://www.veeam.com/kb3032

[lukklin]

Yes, I know that kb. I've created this IAM role but the wizard shows this message: "The default account is not initialized" (In the veeam console)

[Mike Resseler]

OK. I noticed our support is looking in certain logs. Please keep us informed about what is happening

Thanks
Mike

[lukklin]

I will do

[lukklin]

It looks like there were some network issues during the initial deployment of the appliance, which prevented the appliance to reach AWS IAM.

The support and I were able to get the appliance to work by simply restarting some services:

Code: Select all

sudo systemctl restart veeam-updater.service

Code: Select all

sudo systemctl restart veeamawsbackup.service

Code: Select all

sudo systemctl restart veeamawsbackupweb.service

But I'm very happy with the solution, even for a 1.0 release..Backup & FLR was working very seamless so far

Cheers!
Lukas

[nielsengelen]

Thanks for the follow-up Lukas. Any extra feedback is appreciated!

[master_mike]

I am having the same issue after deploying the clod formation for veeam twice now... The default account is not initialized.
Under accounts it is empty, the default account is not created.
I cant seem to SSH intot he appliance either, as I get no authorization methods specifed when i do.

Any insight into the issue?

Mike

[Mike Resseler]

Hi @master_mike

Could you create a support call?

Thanks
Mike

[HannesK]

Hello,
thanks @lukklin for posting the solution. I ran into the same issue.

Best regards,
Hannes

[master_mike]

my issue was networking related, and because I deployed into a private VPC behind a NAT, which would cause this issue. I had to deploy into a VPC with IGW and no NAT.
Even thought the NAT gave the instance a public IP and the security groups and NACL was setup properly, I guess it still had issues connecting to the AWS services it needed to to activate the default account. Support wrote this KB about the issue.. https://www.veeam.com/kb3071

[Roberto]

Also a misconfigured Veeam Backup for AWS appliance (EC2) "instance profile" make this error as EC2 cannot assume right role in local or external account nor can you ever change roles configurations