Skip to content

Based on my PingFederate migration from AWS EKS to AWS ECS Fargate for about 20,000 daily users

Notifications You must be signed in to change notification settings

bmcanelly/pingfederate-fargate

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 

Repository files navigation

pingfederate-fargate

initial Terraform for PingFederate and PingFederate Admin ECS/Fargate containers

Requirements

  • Terraform Version 1 or newer
  • Existing domains and domain certificates required from data.tf files
  • Existing EFS volumes with configurations/files for (in) /opt/in mounts for pingfederate container and /opt/in and /opt/out/instance/service/default/data (data) mounts - import with terraform import from efs.tf files in va/tst or va/prd depending on environment
  • Existing Systems Manager parameters/secrets and environment vars updated in va/tst/configs/ or va/prd/configs/ ECS container json definitions
  • Update local settings in existing locals.tf files

Optional

  • S3 Bucket for ALB logging (or comment out)
  • S3 Bucket for terraform remote state in s3 (uncomment and configure in _config.tf files)

Virginia AWS Test Application resources

Virginia AWS Production Application resources

Procedures

  • get requirements setup
  • config applied in va to create VPC and all other resources. define settings in va/locals.tf.
  • apply test or production as needed

Todo

  • Pull in WAFv2/GlobalAccelerator configs
  • Automate more requirements
  • HA to another region
  • Cleanup

About

Based on my PingFederate migration from AWS EKS to AWS ECS Fargate for about 20,000 daily users

Topics

Resources

Stars

Watchers

Forks

Languages