Setup ALB routing

[briri]

Once the new HostedZone is in place we need to setup the ALB with listener rules.

New DMPHub pages will be accessed through the DMPTool UI. For example:

• Dashboard - When admin logins in they will go here instead of the standard DMPTool Dashboard
• Landing page - via the DMP ID links throughout the site
• Curation/Edit page - via a link on the DMP Landing Page, Dashboards, etc. (assuming the user has authority)
• Upload page - via a new menu item on the DMPTool main navigation

The ALB Listener rules will need to do the following:

Short Term: we want to direct DMPHub traffic as follows:

• dmphub.cdlib.org -> Redirect to dmptool.org
• dmphub.cdlib.org/dashboard -> CloudFront Hosted Dashboard page
• dmphub.cdlib.org/dmps/new -> CloudFront Hosted Upload/Create page
• dmphub.cdlib.org/dmps/edit/10.12345/ABC123 -> CloudFront Hosted edit/curation page
• dmphub.cdlib.org/dmps/10.12345/ABC123 -> CloudFront Hosted Landing page
• dmphub.cdlib.org/api -> API Gateway
• dmphub.cdlib.org/auth -> Cognito

Long Term: Eventually we do not want to have the separate dmphub domain, so update to use the DMPTool domain but I think that will require us to host the app in the new AWS environment so that we have authority over its Hosted Zone:

• dmptool.org -> ECS Hosted DMPTool Rails app
• dmphub.cdlib.org -> Redirect to dmptool.org
• hub.dmptool.org/dashboard -> CloudFront Hosted Dashboard page
• hub.dmptool.org/dmps/new -> CloudFront Hosted Upload/Create page
• hub.dmptool.org/dmps/edit/10.12345/ABC123 -> CloudFront Hosted edit/curation page
• hub.dmptool.org/dmps/10.12345/ABC123 -> CloudFront Hosted Landing page
• api.dmptool.org/ -> API Gateway
• auth.dmptool.org/ -> Cognito

[briri]

This will not be necessary until we move the DMPTool into an ECS cluster