counterweight/superhog-infra-repo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ssh key

Browse source
This commit is contained in:
Pablo Martin 2024-02-06 17:11:27 +01:00
parent e03c57e094
commit c499acb768
1 changed files with 27 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

30
human-script.md
View file

@ -2,13 +2,16 @@
Follow this to deploy the entire data infra. Follow this to deploy the entire data infra.
## 0. Pre-requisites and conventios ## 0. Pre-requisites and conventions
- You need an Azure subscription and a user with administrator rights in it. - You need an Azure subscription and a user with administrator rights in it.
- Whenever you see `<your-env>`, you should replace that with `dev`,`uat`, `prd` or whatever fits your environment. - Whenever you see `<your-env>`, you should replace that with `dev`,`uat`, `prd` or whatever fits your environment.
- We traditionally deploy resources on the `UK South` region. Unless stated otherwise, you should deploy resources there. - We traditionally deploy resources on the `UK South` region. Unless stated otherwise, you should deploy resources there.
- You have an SSH key pair ready to use for access to the different machines. You can always add more pairs later.
## 1. Resource group ## 1. Resource group and SSH Keypair
### 1.1 Create Resource Group
- Create a resource group. This resource group will hold all the resources. For the rest of this guide, assume this is the resource group where you must create resources. - Create a resource group. This resource group will hold all the resources. For the rest of this guide, assume this is the resource group where you must create resources.
- Name it: `superhog-data-rg-<your-env>` - Name it: `superhog-data-rg-<your-env>`
@ -16,6 +19,17 @@ Follow this to deploy the entire data infra.
- `team: data` - `team: data`
- `environment: <your-env>` - `environment: <your-env>`
### 1.2 SSH Keypair
- We will create an SSH Keypair for this deployment. It will be used to access VMs, Git repos and other services.
- Create the SSH Key pair
- Name the key `superhog-data-<your-env>-general-ssh`
- Add tags:
- `team: data`
- `environment: <your-env>`
- Pay attention when storing the private key. You probably want to store it in a safe password manager, like Keeper.
- Optionally, you can also be extra paranoid, generate the SSH key locally and only upload the public key to Azure. Up to you.
## 2. Networking ## 2. Networking
### 2.1 VNET ### 2.1 VNET
@ -171,7 +185,17 @@ Follow this to deploy the entire data infra.
## 3. Jumphost ## 3. Jumphost
### 3.1 Deploy Jumphost machine ### 3.1 Deploy Jumphost VM
- The first VM we must deploy is a jumphost, since that will be our door to all other services inside the virtual network.
- Create the VM
- Name it: `jumphost`
- Use Ubuntu Server 22.04
- Use Size: `Standard_B1s`
### 3.2 Configure a
### 3.3 Harden
## 4. DWH ## 4. DWH