Manage buckets, etc. in Terraform

[eddierubeiz]

• [x] Describe all resources in Terraform
  • [x] Bucket for storing EADS
  • [x] IAM user that only has write access to the EAD bucket
  • [x] Policy that grants the IAM user access to the EAD bucket
  • [x] Policy on that EAD bucket (public)
  • [x] Ownership controls on that bucket (BucketOwnerEnforced)
  • [x] Terraform state bucket
  • [x] Public access block for the state bucket
  • [x] Dynamodb table for the state locks
• [x] Ensure Terraform is using the state bucket to store state
• [x] Document in the wiki

[eddierubeiz]

OK -- we finally have the following resources in the state file, and the state stored on S3.

aws_iam_policy.export_archivesspace_xml_policy: Refreshing state... [id=arn:aws:iam::335460257737:policy/export_archivesspace_xml_policy]
aws_iam_user.export_archivesspace_xml_user: Refreshing state... [id=export_archivesspace_xml]
aws_dynamodb_table.terraform_state_locks: Refreshing state... [id=export-archivesspace-xml-terraform-state-locks]
aws_s3_bucket.ead: Refreshing state... [id=ead.sciencehistory.org]
aws_s3_bucket.terraform_state: Refreshing state... [id=export-archivesspace-xml-terraform-state]
aws_iam_user_policy_attachment.export-archivesspace-xml_user_policy_attachment: Refreshing state... [id=export_archivesspace_xml-20220120140710366600000001]
aws_s3_bucket_policy.ead: Refreshing state... [id=ead.sciencehistory.org]
aws_s3_bucket_ownership_controls.ead: Refreshing state... [id=ead.sciencehistory.org]
aws_s3_bucket_public_access_block.terraform_state: Refreshing state... [id=export-archivesspace-xml-terraform-state]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.