Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup new AWS SubAccount #56

Open
nce opened this issue Dec 16, 2022 · 1 comment
Open

Setup new AWS SubAccount #56

nce opened this issue Dec 16, 2022 · 1 comment

Comments

@nce
Copy link
Contributor

nce commented Dec 16, 2022

We need to switch to a new Account and recreate Clusters.
I'll document all the steps for a working setup here.

Local Machine

  1. Create a new AWS Profile for the account in ~/.aws/credentials
  2. Export that profile on the cli export AWS_PROFILE=xxx

Initial TF Bucketsetup/Github User

  1. run terraform in the root folder (picking up init.tf)
  2. Gather the outputs (access & secret key) and put them in the repo as secrets

DNS

  1. In the new account switch to route53 and create a new hosted zone.
  2. In the root account, in r53 modify our adorsys.io Domain to point to the new NS of the newly created Zone in the new subaccount

Kubermatic

  1. In the dev-intern project create/modify the k8s clusters by managing with the webui
  2. Download the kubeconfig and place it in the clusters-name folder as .kubeconfig

Clusterconfig

Create a new folder with the name of your cluster, like: foobar-cluster

  1. Modify the variables.tf and add name & kubermatic cluster id
  2. Modify the terraform.tf and rename the tf s3 bucket
  3. Modify the provider.tf and rename the tags with correct cluster name
  4. Modify the main.tf as you see fit

AWS Secretsmanager

  1. Go through all secrets in /kaas/ evaluate; migrate to new account
  2. Copy/Update those secrets
nce added a commit that referenced this issue Dec 16, 2022
nce added a commit that referenced this issue Dec 16, 2022
@nce
Copy link
Contributor Author

nce commented Dec 18, 2022

Most work was done in the linked commits and this PR: #57

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant