Feature Request: Support CloudFront Field Level Encryption Profile

[bflad]

Recently the AWS SDK for Go has added support for managing CloudFront field level encryption profiles as first announced in: https://aws.amazon.com/about-aws/whats-new/2017/12/introducing-field-level-encryption-on-amazon-cloudfront/

Please vote on this issue by adding a 👍 reaction to the original issue to help prioritize interest. If you're interested in implementing this feature request, please comment below.

Prerequisite: aws-sdk-go v.1.13.26 (already merged)

Terraform Version

terraform 0.10+

New Resource(s)

• aws_cloudfront_field_level_encryption_profile

Terraform Configuration Files

# Example implementation, may change when developed
resource "aws_cloudfront_field_level_encryption_profile" "example" {
  comment = "" # optional
  encryption_entity { # required
    field_patterns = [] # required
    provider_id = "" # required
    public_key_id = "" # required
  }
  name = "" # required
}

Expected Behavior

Resource creates, updates, and deletes CloudFront field level encryption profiles.

Actual Behavior

New feature.

References

• https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/field-level-encryption.html
• https://docs.aws.amazon.com/sdk-for-go/api/service/cloudfront/#CloudFront.CreateFieldLevelEncryptionProfile

[saravanan30erd]

I will start to work on this resource.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!