Unable to create application - no accounts listed in the dashed box next to the โ€œAccountsโ€ heading

I am working on the Spinnaker Getting Started reference. Spinnaker now runs on an EC2 instance and is accessible via http: // localhost: 9000 .

When I try to create a new application, I understand that I expect my-aws-account and my-google-account . However, I do not see any parameters on this screen. Any idea on what could go wrong?

+6
source share
1 answer
  • Create an AWS User Account for Spinnaker
    • In the AWS Console, open AWS Identity and Access Management โ†’ Users โ†’ Create New Users.
    • Enter your username and click Create.
    • Create a passkey for the user.
    • Click "Download Credentials", you will need them later.
    • Click "Close."
  • Apply permissions for new user
    • Click on the username you entered for a more detailed screen.
    • On the Summary page, click the Permissions tab.
    • Apply Managed Policy
      • Click "Attach Policy."
      • Check the box next to PowerUserAccess, then click "Attach Policy."
    • Create Inline Policy
      • Click the Inline Policies heading, then click the link to create an inline policy.
      • Click "Select for policy generator."
      • Select AWS Identity and Access Management from the AWS drop-down list.
      • Select PassRole for action.
      • Enter * (asterisk) in the Amazon Resource Name (ARN) field.
      • Click Add Expression, then Next Step.
      • Click Apply Policy.
  • Add AWS Credentials for Spinnaker
    • Connect to an instance of Spinnaker (I assume you are using Linux)
    • Run the command: sudo mkdir /home/spinnaker/.aws
    • Run the command: sudo vim /home/spinnaker/.aws/credentials
    • Add the following lines to the file, then save and close:
      • Be sure to replace my-aws-account with your AWS my-aws-account name
      • Be sure to replace the key ID and access key values โ€‹โ€‹with the credentials that you downloaded in step 1, part 4
  [my-aws-account] aws_access_key_id = AKIAIOSFODNN7EXAMPLE aws_secret_access_key = wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY 
  1. Update default Spinnaker configuration files
    • Run the command: sudo vi /etc/default/spinnaker
    • Find the line SPINNAKER_AWS_ENABLED and change the value to true
    • Find the line SPINNAKER_AWS_DEFAULT_REGION and change the value to the area where the Spinnaker instance is running (for example, us-east-1 , without quotes)
    • Save and exit
  2. Update the local Spinnaker configuration files (they override the YAML files that come with the Spinnaker installation)
    • Run the command: sudo vim /opt/spinnaker/config/spinnaker-local.yml
    • Find providers , then find aws under this
    • Under aws find enabled and change the value to true
    • At the bottom of aws find defaultRegion and change the value to the area where the Spinnaker instance is running (e.g. us-east-1 , without quotes)
    • Under primaryCredentials find name and change the value to my-aws-account
      • Be sure to replace my-aws-account with your AWS my-aws-account name
    • Save and exit
  3. Restart spinnaker
    • Run the command: sudo /opt/spinnaker/scripts/reconfigure_spinnaker.sh
    • Run the command: sudo restart spinnaker
  4. Reset the tunnel from your local machine to the Spinnaker instance
+9
source

All Articles