Skip to content

Latest commit

 

History

History
24 lines (23 loc) · 1.43 KB

File metadata and controls

24 lines (23 loc) · 1.43 KB

Infra creation

  1. Deploy Route53 Hosted Zone CF (dns.cf.json)
    1. Get the NS servers from the deployed R53 zone, and then create a new record set on the root account with an NS record pointing to those NS servers
  2. Deploy FE CF (spa-cert.cf.yaml & spa.cf.yaml)
    1. The cert stack must be deployed in us-east-1, while the other main spa stack can be in any region
    2. As the cert stack deploying, add FE DNS records from SSL certificate to Route53 Hosted Zone
  3. Deploy API CF (api-s3.cf.yaml & api.cf.yaml)
    1. First deploy the S3 template, and upload a deployment.zip file to it
    2. As it's deploying, Add BE DNS records from SSL certification to Route53 Hosted Zone
  4. Deploy deployment user CF (deployment-user.cf.yaml)
  5. Update GitHub Actions secrets
    1. secrets.STAGE_AWS_ACCESS_KEY_ID & secrets.STAGE_AWS_SECRET_ACCESS_KEY
      1. Output from deployment-user stack
    2. secrets.STAGE_S3_BUCKET & secrets.STAGE_CF_DISTRIBUTION_ID
      1. Name of bucket from spa stack
    3. secrets.STAGE_S3_CODE_BUCKET & secrets.STAGE_API_CF_NAME
      1. Name of the api stack, and output from that stack
  6. Run a stage deploy through GitHub Actions
    1. Before code is deployed to the infra, you might see permission errors

Infra deletion

  1. Delete all manually created HostedZone DNS record for SSL certificates
  2. Delete all objects in S3 buckets (inc. all version)
  3. Delete all CF stacks