You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: infrastructure/README.md
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,22 +4,36 @@ Our infrastructure sits in the Europe(London) region coded 'eu-west-2' in AWS.
4
4
5
5
## Post deployment steps
6
6
7
-
### Setting up and using secrets
7
+
### Setting up and using secrets in AWS Secrets Manager
8
+
9
+
Secrets need to be created in AWS Secrets Manager as follows:
10
+
11
+
1. Click on `Store a new secret` in Secrets Manager
12
+
2. Secret Type: `Other type of secret`
13
+
3. Select `Plaintext` option
14
+
4. Fill in the secret value in the text area
15
+
5. Encryption key: `aws/secretsmanager`, and click next
16
+
6. Add a name for the secret and description
17
+
7. Tags as [below](#tags)
18
+
8. Click next on the screens and then store.
8
19
9
20
Update the values for the following secrets after generating them: -
10
21
11
-
- /vita/apim/prod-1.pem - APIM private key used to sign JWTs generated from [here](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/user-restricted-restful-apis-nhs-login-separate-authentication-and-authorisation#step-3-generate-a-key-pair). 'prod-1' here is the key id used during generation.
22
+
- /vita/apim/prod-1.pem - APIM private key used to sign JWTs to access user-restricted APIs via APIM, generated from [here](https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/user-restricted-restful-apis-nhs-login-separate-authentication-and-authorisation#step-3-generate-a-key-pair). 'prod-1' here is the key id used during generation.
12
23
- /vita/apim/prod-1.json - APIM public key in JWKS format generated above
13
24
- /vita/nhslogin/private_key.pem - NHS Login private key generated from [here](https://nhsconnect.github.io/nhslogin/generating-pem/)
14
25
- /vita/nhslogin/public_key.pem - NHS Login public key generated above
15
26
- /vita/splunk/hec/endpoint - HEC endpoint of Splunk
16
27
- /vita/splunk/hec/token - HEC token of Splunk endpoint to store operational logs
17
28
18
-
Now fill the values used by the application below: -
29
+
The following secrets need to be created and set before running the application:
19
30
20
-
- Go to AWS service "Systems Manager"
21
-
- Click on "Parameter Store" under application tools section
22
-
- Update the values as per integrations in that environment
31
+
-`/vita/APIM_PRIVATE_KEY`: Same value as `/vita/apim/prod-1.pem`
32
+
-`/vita/AUTH_SECRET`: A randomly generated string used to sign JWTs for authentication (NextAuth)
33
+
-`/vita/CONTENT_API_KEY`: NHS UK Content API Key
34
+
-`/vita/ELIGIBILITY_API_KEY`: EliD API Key
35
+
-`/vita/NHS_LOGIN_CLIENT_ID`: NHS Login OIDC Client ID for VitA App
36
+
-`/vita/NHS_LOGIN_PRIVATE_KEY`: Same value as `/vita/nhslogin/private_key.pem`
23
37
24
38
### Setting up Cloudfront error pages
25
39
@@ -38,12 +52,10 @@ Manually create the following error routes.
38
52
39
53
### Setting default limits and settings
40
54
41
-
- Increase the default throughput limit of the parameter store, instructions [here](https://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-throughput.html#parameter-store-throughput-increasing)
42
55
- Also setup [service quotas automatic management](https://docs.aws.amazon.com/servicequotas/latest/userguide/automatic-management.html) to alert on Slack channel
43
56
- Review AWS > Service Quotas
44
57
- AWS Lambda > Concurrent executions: Default is 1000 counts.
45
-
- AWS Systems Manager > Rate of GetParameter requests: Currently 10,000 per second. Cannot request an increase via AWS console.
46
-
- AWS Key Management Service (AWS KMS) > Cryptographic operations (symmetric) request rate: Currently 20,000 per second (used by SSM and Lambda)
58
+
- AWS Key Management Service (AWS KMS) > Cryptographic operations (symmetric) request rate: Currently 20,000 per second (used by Secrets Manager and Lambda)
47
59
- Setup important notifications
48
60
- AWS > User Notifications > Delivery Channels > Chat channels. Select the channel
0 commit comments