Joe Coyne's demonstration web application

This page calls a RESTful web service and displays responses in the same page. See notes below.
The same app is hosted on AWS Amplify, AWS Elastic Compute (EC2), and a secure custom domain. See the 3 links.

Retrieve All Users Create/Retrieve/Update/Delete one User





Base Service URL

(All users)

Access this application on different hosts:-

Hosted on AWS Amplify
Hosted on AWS Elastic Compute (EC2)
Hosted on a secure custom domain







(Only enter a user Id)
(Do not enter a user Id)
(Enter all fields - blanks overwrite)
(Only enter a user Id)

The responses to RESTful requests will be displayed below

Notes.
This is a functional demonstration of Joe's technical knowledge and development skills, not web-site design or aesthetics!
This 'full-stack' application uses HTML, CSS and Javascript in the browser, a RESTful web service/API developed in Java, running on an application server, and a MySQL database server for persistent data storage.
The same app is hosted on AWS Amplify, AWS Elastic Compute (EC2), and on servers in Joe's home office using a secure custom domain.
The Amplify and Elastic hosted sites show the default assigned AWS domain in the URL, so you can see the Amplify and Elastic domains.
The AWS Amplify and the custom domain sites are HTTPS enabled with trusted Security Certificates (i.e. signed by a trusted Certificate Authority).
The AWS Elastic site is only HTTP enabled, so your browser should report that the connection is not secure, unlike the other two sites. It's fine to follow the link anyway.
The AWS Elastic Compute variant is running on a Linux/Tomcat container in a European data centre (i.e. eu-west-1, as can be seen in the URL).
The secure custom domain uses a registered domain name, DNS, HTTPS/OpenSSL/Certificates, and CORS.
The AWS Amplify hosted site (HTTPS) calls a web service hosted on the custom domain (also HTTPS), to show cross domain working.
The AWS Elastic hosted site (HTTP) calls a web service hosted hosted on the AWS Elastic domain (also HTTP), to show that the REST service running in multiple places.
Any combination of domains/calls is OK, except that a secure page can't call a non-secure web service because modern browsers block that behaviour.
All three sites/services connect to the same database hosted on a shared back-end database server. A new or changed user entered through the front end hosted in any domain can be retrieved and seen through the front ends hosted in the other domains.