[FOLIO-1134] Secure public AWS instances Created: 16/Mar/18  Updated: 10/Feb/20

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Umbrella Priority: P3
Reporter: Wayne Schneider Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: ci, for-next-sprint
Remaining Estimate: Not Specified
Time Spent: 3 hours
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-759 Update how db credentials are passed ... Open
is blocked by FOLIO-1136 Build AMI from folio-snapshot-stable Open
is blocked by FOLIO-1137 Update folio-demo Open
is blocked by FOLIO-778 Enforce permissions on Okapi administ... Closed
is blocked by FOLIO-897 Avoid external port 9130 in full-stac... Closed
is blocked by FOLIO-1135 Use HTTPS to serve FOLIO AWS instances Closed
Relates
relates to FOLIO-1133 Create a Vagrant box for snapshot-stable Open
relates to OKAPI-787 Support SSL connections to Postgres Closed
Sprint:
Development Team: Core: Platform

 Description   

Our AWS instances are becoming more visible in the community. We need to do some work to secure them. Also, it is probably time to repurpose the folio-demo.aws.indexdata.com CNAME to point to a more reasonable system that is better maintained. This is an umbrella issue to cover the work required.


Generated at Thu Feb 08 23:11:05 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.