Document the set up of AWS/EKS
Budget: £250 – £750 GBP
We need to set up a POC on AWS using EKS (managed nodes).
We need someone to document the steps to set up in AWS and support us to get it running.
We need these items documented so we can replicate them.
1. Build a docker image for a Java Spring Boot application (Which we will supply). This will be very simple. It will return a message when a GET is received. This is Service A
The same applies to a different Spring Boot application (supplied). This will return a different message. This is Service B
2. Upload image to ECR. Document any steps in setting up ECR
3. Create a cluster in EKS.
4. Create a persistent volume.
5. Service A and Service B should also mount the PV so we can store local files if we need to
6. Create another service running MySQL (or postgres), storing the data on the PV
7. Create a secret to hold the MySQL username/password
8. Create the Service A & B. This configuration should set some example environment variables and the Secret values for MySQL
9. Create an Ingress so that a.domain.com will direct to Service A and b.domain.com will direct to Service B
10. Detail any settings we need to make in AWS (route 53 etc.)
We will then replicate the steps on our environment and run these tests
Test Service A is called when using the correct domain
Test the message return from Service A includes an Enviroment variable
Check that Service A can access the PV
Check Service A can access the database, using the secret
Same test for Service B
We need someone to document the steps to set up in AWS and support us to get it running.
We need these items documented so we can replicate them.
1. Build a docker image for a Java Spring Boot application (Which we will supply). This will be very simple. It will return a message when a GET is received. This is Service A
The same applies to a different Spring Boot application (supplied). This will return a different message. This is Service B
2. Upload image to ECR. Document any steps in setting up ECR
3. Create a cluster in EKS.
4. Create a persistent volume.
5. Service A and Service B should also mount the PV so we can store local files if we need to
6. Create another service running MySQL (or postgres), storing the data on the PV
7. Create a secret to hold the MySQL username/password
8. Create the Service A & B. This configuration should set some example environment variables and the Secret values for MySQL
9. Create an Ingress so that a.domain.com will direct to Service A and b.domain.com will direct to Service B
10. Detail any settings we need to make in AWS (route 53 etc.)
We will then replicate the steps on our environment and run these tests
Test Service A is called when using the correct domain
Test the message return from Service A includes an Enviroment variable
Check that Service A can access the PV
Check Service A can access the database, using the secret
Same test for Service B