Skip to main content
Solved

AWS onboarding as secondary CSP

  • July 15, 2023
  • 3 replies
  • 98 views

Bigo
Forum|alt.badge.img+4
  • Second Officer
  • 13 replies

I have my Aviatrix controller deployed in Azure, and I’d like to start managing AWS resources.

I couldn’t find where the documentation for onboarding AWS account is.

I could only find docs aboutusing AWS as the first CSP, where the controller lives.

Can anyone sahre some tutorial for  onboarding AWS accounts as secondary CSP?

Best answer by Nico

Hi @Bigo ,

as per your request, to create resources in AWS realm, you need to add an Access Account in the Aviatrix Controller.

In the documentation page, there is a clear screenshot explaining how adding a new AWS access account. Considering your Controller has been deployed in Azure and for my understanding, you should untick the “Iam role-based” value, filling the AWS Account Number and Key.

Please, let me know if you still need any clarification.

3 replies

Nico
Forum|alt.badge.img+1
  • Aviatrix Employee
  • 27 replies
  • Answer
  • July 18, 2023

Hi @Bigo ,

as per your request, to create resources in AWS realm, you need to add an Access Account in the Aviatrix Controller.

In the documentation page, there is a clear screenshot explaining how adding a new AWS access account. Considering your Controller has been deployed in Azure and for my understanding, you should untick the “Iam role-based” value, filling the AWS Account Number and Key.

Please, let me know if you still need any clarification.


Bigo
Forum|alt.badge.img+4
  • Author
  • Second Officer
  • 13 replies
  • July 18, 2023

Hi @Domenico_Marino.1 , many thanks for pointing me to that page, it worked and I could onboard the AWS account from the Controller in Azure.

The step of  un-ticking the “Iam role-based” value was crucial I guess.

In general, I’d suggest to update that part of documentation in a more “cloud neutral” way, as it is currently much AWS-centric. 


Nico
Forum|alt.badge.img+1
  • Aviatrix Employee
  • 27 replies
  • July 18, 2023

Awesome @Bigo! Glad we fixed it!

Thank you for your suggestions, highly appreciated and anything you need, ping us!