Having a single account..

[venkyvb]

BTW, great documentation !!

I am doing a POC wherein the Spinnaker is running in one EKS cluster (e.g spinnaker) and apps are deployed in another EKS cluster (e.g. staging). In this case basically both the Managing account and the Managed account are the same.

Are the steps outlined in the https://docs.armory.io/spinnaker-install-admin-guides/add-aws-account/ still the same? Or can I just add the PowerUserAccess be directly assigned to the EC2 instances and then run:

hal config provider aws enable

[justinrlee]

Are you deploying only to EKS? Or are you also trying to deploy AWS resources directly (EC2 instances, etc.)?

If you're doing EKS, we basically treat EKS as a Kubernetes cluster and ignore the fact that it's an AWS item. You actually wanna follow this document: https://docs.armory.io/spinnaker-install-admin-guides/add-kubernetes-account/

If you wanna add AWS to deploy EC2 instances or CF or whatever, then you need to follow the https://docs.armory.io/spinnaker-install-admin-guides/add-aws-account/ document; Clouddriver doesn't directly use the permissions it has (aside from two mentioned roles) - it will always try to assume a role (even if it's the same account), so you need to tell it what role to assume.

[venkyvb]

@justinrlee Thanks for the quick feedback.

I am only targeting deploy to EKS and not to AWS in general. Of course Spinnaker is running in a separate EKS cluster (if you want to use the term Managing Cluster) from the app EKS cluster (Managed Cluster).

Will check out the https://docs.armory.io/spinnaker-install-admin-guides/add-kubernetes-account/.