Skip to content

Instantly share code, notes, and snippets.

@mbklein
Created January 23, 2019 16:27
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mbklein/3a8a51adfcf50467497683206e4097b2 to your computer and use it in GitHub Desktop.
Save mbklein/3a8a51adfcf50467497683206e4097b2 to your computer and use it in GitHub Desktop.
Basic info about NU Library's Fedora-on-AWS deployment
  • Version/Infrastructure info:
    • Fedora 4.7.5
    • In a private VPC with the rest of our applications
    • Deployed via Elastic Beanstalk on the Multicontainer Docker platform
      • t2.xlarge instance type
      • Behind a classic load balancer
    • Docker image: nulib/fcrepo4:s3fix
  • Prerequisites:
    • An RDS Postgresql instance for Fedora to use for metadata
    • An S3 Bucket for Fedora to use for binaries
    • Ideally, Fedora/Modeshape would use shared credentials from the environment and we could handle bucket access using an EC2 instance profile role. However, since it doesn't (yet), you'll need:
      • An IAM user with read/write access to the above bucket (I can send you the exact policy we use if you'd like)
      • A valid access key/secret for the above IAM user
  • Configuration via environment variables set through Elastic Beanstalk
    • JAVA_OPTIONS=
      • -Dfcrepo.postgresql.host=RDS_HOSTNAME
      • -Dfcrepo.postgresql.port=RDS_PORT
      • -Dfcrepo.postgresql.username=RDS_USERNAME
      • -Dfcrepo.postgresql.password=RDS_PASSWORD
      • -Daws.accessKeyId=IAM_USER_ACCESS_KEY_ID
      • -Daws.secretKey=IAM_USER_SECRET_KEY
      • -Daws.bucket=S3_BUCKET
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment