You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to manage our CloudFront distributions like we do our applications with known-good configuration, data.gov developers want the CloudFront distribution configuration under source control as configuration-as-code.
Acceptance Criteria
GIVEN access to an S3 terraform state bucket
WHEN I run terraform show
THEN I see catalog.data.gov and www.data.gov CloudFront distributions represented in Terraform output
User Story
From the 2020-11-04 catalog.data.gov partial outage retrospective.
In order to manage our CloudFront distributions like we do our applications with known-good configuration, data.gov developers want the CloudFront distribution configuration under source control as configuration-as-code.
Acceptance Criteria
WHEN I run
terraform show
THEN I see catalog.data.gov and www.data.gov CloudFront distributions represented in Terraform output
Background
https://docs.google.com/document/d/193UUWNO7rvGYsiXZJJb4AlRV4s1iT-ZG5mkAXfrv404/edit#
Security Considerations (required)
SSP should be updated to include how we manage the CloudFront distribution configuration and how it is secured via GitHub and AWS IAM.
Sketch
Create a new GH repo to manage this.
The text was updated successfully, but these errors were encountered: