# New CloudFront OrignAccessControlType: Lambda

**URL:** <https://discuss.hashicorp.com/t/new-cloudfront-orignaccesscontroltype-lambda/66021>\
**Category:** AWS\
**Created:** [April 17, 2024, 1:21pm UTC](https://discuss.hashicorp.com/t/new-cloudfront-orignaccesscontroltype-lambda/66021 "2024-04-17T13:21:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacobhrussell](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jacobhrussell/32/41302_2.png) [@jacobhrussell](https://discuss.hashicorp.com/u/jacobhrussell)\
**Post date:** [April 17, 2024, 1:21pm UTC](https://discuss.hashicorp.com/t/new-cloudfront-orignaccesscontroltype-lambda/66021/1 "2024-04-17T13:21:41Z")

</div>

AWS [recently announced](https://aws.amazon.com/about-aws/whats-new/2024/04/amazon-cloudfront-oac-lambda-function-url-origins/) CloudFront Origin Access Control support for Lambda Function URLs. In the [aws\_cloudfront\_origin\_access\_control resource documentation](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_origin_access_control) I still only see `s3` and `mediastore` as valid values for the `origin_access_control_origin_type`.

Are there plans to support `lambda`?

---

<div class="post-metadata">

**Author:** ![jacobhrussell](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jacobhrussell/32/41302_2.png) [@jacobhrussell](https://discuss.hashicorp.com/u/jacobhrussell)\
**Post date:** [April 17, 2024, 1:46pm UTC](https://discuss.hashicorp.com/t/new-cloudfront-orignaccesscontroltype-lambda/66021/2 "2024-04-17T13:46:45Z")

</div>

Looks like it might be in the [upcoming 5.46.0 release](https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md). The [linked PR](https://github.com/hashicorp/terraform-provider-aws/pull/34362) doesn’t look like it has anything to do with CloudFront, but maybe the wrong one was linked accidentally.
