PRA: add pingdom IP addresses, update readme (#3111)

ministryofjustice · Aug 16, 2023 · 13e3eeb · 13e3eeb
1 parent 0620f30
commit 13e3eeb
Show file tree

Hide file tree

Showing 3 changed files with 83 additions and 62 deletions.
diff --git a/terraform/environments/pra-register/README.md b/terraform/environments/pra-register/README.md
@@ -1,76 +1,37 @@
-# Service Runbook
-
-<!-- This is a template that should be populated by the development team when moving to the modernisation platform, but also reviewed and kept up to date.
-To ensure that people looking at your runbook can get the information they need quickly, your runbook should be short but clear. Throughout, only use acronyms if you’re confident that someone who has just been woken up at 3am would understand them. -->
-
-_If you have any questions surrounding this page please post in the `#team-name` channel._
-
 ## Mandatory Information
 
 ### **Last review date:**
 
-<!-- Adding the last date this page was reviewed, with any accompanying information -->
+16/08/2023
 
 ### **Description:**
 
-<!-- A short (less than 50 word) description of what your service does, and who it’s for.-->
+The Parental Responsibility Agreement Register (PRA) application is a business critical application that allows HMCTS Central Family court staff to register all Parental Responsibility Agreements (PRAs)  submitted to Central Family Court. Staff users can also view submitted PRAs within the lifecycle of the Agreement and search for agreements using selected criteria.
+
+PRA agreements are termed certificates once signed and witnessed by the relevant parties.
 
 ### **Service URLs:**
 
-<!--  The URL(s) of the service’s production environment, and test environments if possible-->
+Development: https://pra-register.hmcts-development.modernisation-platform.service.justice.gov.uk/
+Preproduction: https://pra-register.hmcts-preproduction.modernisation-platform.service.justice.gov.uk/
+Production: https://parental-responsibility-agreement.service.justice.gov.uk/
 
 ### **Incident response hours:**
 
-<!-- When your service receives support for urgent issues. This should be written in a clear, unambiguous way. For example: 24/7/365, Office hours, usually 9am-6pm on working days, or 7am-10pm, 365 days a year. -->
+9am-5:30pm Mon-Fri
 
 ### **Incident contact details:**
 
-<!-- How people can raise an urgent issue with your service. This must not be the email address or phone number of an individual on your team, it should be a shared email address, phone number, or website that allows someone with an urgent issue to raise it quickly. -->
+<[email protected]>
 
 ### **Service team contact:**
 
-<!-- How people with non-urgent issues or questions can get in touch with your team. As with incident contact details, this must not be the email address or phone number of an individual on the team, it should be a shared email address or a ticket tracking system.-->
+<dts-legacy-apps-support-team@hmcts.net>
 
 ### **Hosting environment:**
 
 Modernisation Platform
 
-<!-- If your service is hosted on another MOJ team’s infrastructure, link to their runbook. If your service has another arrangement or runs its own infrastructure, you should list the supplier of that infrastructure (ideally linking to your account’s login page) and describe, simply and briefly, how to raise an issue with them. -->
-
-## Optional
-
 ### **Other URLs:**
 
-<!--  If you can, provide links to the service’s monitoring dashboard(s), health checks, documentation (ideally describing how to run/work with the service), and main GitHub repository. -->
-
-### **Expected speed and frequency of releases:**
-
-<!-- How often are you able to release changes to your service, and how long do those changes take? -->
-
-### **Automatic alerts:**
-
-<!-- List, briefly, problems (or types of problem) that will automatically alert your team when they occur. -->
-
-### **Impact of an outage:**
-
-<!-- A short description of the risks if your service is down for an extended period of time. -->
-
-### **Out of hours response types:**
-
-<!-- Describe how incidents that page a person on call are responded to. How long are out-of-hours responders expected to spend trying to resolve issues before they stop working, put the service into maintenance mode, and hand the issue to in-hours support? -->
-
-### **Consumers of this service:**
-
-<!-- List which other services (with links to their runbooks) rely on this service. If your service is considered a platform, these may be too numerous to reasonably list. -->
-
-### **Services consumed by this:**
-
-<!-- List which other services (with links to their runbooks) this service relies on. -->
-
-### **Restrictions on access:**
-
-<!-- Describe any conditions which restrict access to the service, such as if it’s IP-restricted or only accessible from a private network.-->
-
-### **How to resolve specific issues:**
-
-<!-- Describe the steps someone might take to resolve a specific issue or incident, often for use when on call. This may be a large amount of information, so may need to be split out into multiple pages, or link to other documents.-->
+The service's GitHub repository can be found at: <https://github.com/ministryofjustice/PRA>
diff --git a/terraform/environments/pra-register/load_balancer.tf b/terraform/environments/pra-register/load_balancer.tf
@@ -28,14 +28,69 @@ resource "aws_security_group" "pra_lb_sc" {
   }
 }
 
+resource "aws_security_group" "lb_sc_pingdom" {
+  name        = "load balancer Pingdom security group"
+  description = "control Pingdom access to the load balancer"
+  vpc_id      = data.aws_vpc.shared.id
+
+  // Allow all European Pingdom IP addresses
+  ingress {
+    from_port = 443
+    to_port   = 443
+    protocol  = "tcp"
+    cidr_blocks = [
+      "178.255.152.2/32",
+      "185.180.12.65/32",
+      "185.152.65.167/32",
+      "82.103.139.165/32",
+      "82.103.136.16/32",
+      "196.244.191.18/32",
+      "151.106.52.134/32",
+      "185.136.156.82/32",
+      "169.51.2.18/32",
+      "46.20.45.18/32",
+      "89.163.146.247/32",
+      "89.163.242.206/32",
+      "52.59.46.112/32",
+      "52.59.147.246/32",
+      "52.57.132.90/32",
+      "82.103.145.126/32",
+      "85.195.116.134/32",
+      "178.162.206.244/32",
+      "5.172.196.188/32",
+      "185.70.76.23/32",
+      "37.252.231.50/32",
+      "52.209.34.226/32",
+      "52.209.186.226/32",
+      "52.210.232.124/32",
+      "52.48.244.35/32",
+      "23.92.127.2/32",
+      "159.122.168.9/32",
+      "94.75.211.73/32",
+      "94.75.211.74/32",
+      "185.246.208.82/32",
+      "185.93.3.65/32",
+      "108.181.70.3/32",
+      "94.247.174.83/32",
+      "185.39.146.215/32",
+      "185.39.146.214/32",
+      "178.255.153.2/32",
+      "23.106.37.99/32",
+      "212.78.83.16/32",
+      "212.78.83.12/32"
+    ]
+  }
+}
+
+
 resource "aws_lb" "pra_lb" {
   name                       = "pra-load-balancer"
   load_balancer_type         = "application"
-  security_groups            = [aws_security_group.pra_lb_sc.id]
+  security_groups            = [aws_security_group.pra_lb_sc.id, aws_security_group.lb_sc_pingdom.id]
   subnets                    = data.aws_subnets.shared-public.ids
   enable_deletion_protection = false
   internal                   = false
-  depends_on                 = [aws_security_group.pra_lb_sc]
+  depends_on                 = [aws_security_group.pra_lb_sc, aws_security_group.lb_sc_pingdom]
 }
 
 resource "aws_lb_target_group" "pra_target_group" {

diff --git a/terraform/environments/pra-register/migrate_db.sh b/terraform/environments/pra-register/migrate_db.sh
@@ -5,14 +5,19 @@ export PGPASSWORD=$PRA_DB_PASSWORD;
 SCHEMA=$(psql -h ${DB_HOSTNAME} -p 5432 -U $PRA_DB_USERNAME -d $DB_NAME -c "SELECT schema_name FROM information_schema.schemata WHERE schema_name = 'dbo'" | grep -o 'dbo')
 echo "Schema = $SCHEMA"
 
-export PGPASSWORD=$SOURCE_DB_PASSWORD;
-pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -O --section=pre-data > pre-data.sql
-pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -t 'dbo.*_seq' > sequences.sql
-pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -O --section=data > data.sql
-pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -O --section=post-data > post-data.sql
+if [ "$SCHEMA" == "dbo" ]; then
+    echo "The Schema dbo is already present in the database"
+else
+    export PGPASSWORD=$SOURCE_DB_PASSWORD;
+    pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -O --section=pre-data > pre-data.sql
+    pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -t 'dbo.*_seq' > sequences.sql
+    pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -O --section=data > data.sql
+    pg_dump -U $SOURCE_DB_USERNAME -h $SOURCE_DB_HOSTNAME -d $SOURCE_DB_NAME -O --section=post-data > post-data.sql
 
-export PGPASSWORD=$PRA_DB_PASSWORD;
-psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f pre-data.sql
-psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f sequences.sql
-psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f data.sql
-psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f post-data.sql
+    export PGPASSWORD=$PRA_DB_PASSWORD;
+    psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f pre-data.sql
+    psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f sequences.sql
+    psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f data.sql
+    psql -U $PRA_DB_USERNAME -h $DB_HOSTNAME -d $DB_NAME -f post-data.sql
+
+fi