serverless-iiif-setup.md

log

9.28.2022

• Created IAM group sam-service-access with permissions to manage IAM, S3, Lambda, CloudFormation, and CloudFront.
• Created user aperitiiif-sam-deploy within sam-service-access to inherit policies.
• Created an NYU Web Hosting Bitwarden account w/ credentials in Box
• Added aperitiiif-sam-deploy credentials to NYU Web Hosting Bitwarden account
• Downloaded Bitwarden CLI client locally via npm and logged in for programmatic access to aperitiiif-sam-deploy AWS credentials.
• Made sure AWS-CLI, SAM-CLI, and Docker were installed.
• Made sure Docker was running.
• Ran aws configure --profile aperitiiif-sam-deploy with credentials plus us-east-1 as the default region and json as default output format.
• Ran cd sam/cloudfront && sam build --use-container
• Ran sam deploy --capabilities CAPABILITY_IAM CAPABILITY_AUTO_EXPAND --guided --profile aperitiiif-sam-deploy
  • Stack Name: aperitiiif-serverless-iiif
  • SourceBucket: aperitiiif-serverless-iiif-source-images
  • Managed S3 bucket: aws-sam-cli-managed-default-samclisourcebucket-1er0it3bgmcdy
• Created S3 source bucket aperitiiif-serverless-iiif-source-images

Additional Aperitiiif stuff:

• Created S3 bucket for IIIF presentation API JSON aperitiiif-presentation-api-store
  • Enabled ACLs on the bucket (in GUI)
  • Added the following CORS policy (in GUI)

      [
        {
          "AllowedHeaders": [
            "Authorization"
          ],
          "AllowedMethods": [
            "GET",
            "HEAD"
          ],
          "AllowedOrigins": [
            "*"
          ],
          "ExposeHeaders": [
            "Access-Control-Allow-Origin"
          ]
        }
      ]