Skip to content

Add OriginAccessControlId to OnlyOne#2878

Merged
kddejong merged 1 commit intoaws-cloudformation:mainfrom
kddejong:fix/issue/2877
Sep 13, 2023
Merged

Add OriginAccessControlId to OnlyOne#2878
kddejong merged 1 commit intoaws-cloudformation:mainfrom
kddejong:fix/issue/2877

Conversation

@kddejong
Copy link
Copy Markdown
Contributor

@kddejong kddejong commented Sep 13, 2023

Issue #, if available:
fix #2877
Description of changes:
Add OriginAccessControlId to OnlyOne

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@kddejong kddejong merged commit ba19c30 into aws-cloudformation:main Sep 13, 2023
@kddejong kddejong deleted the fix/issue/2877 branch September 13, 2023 21:58
@jakob-keller
Copy link
Copy Markdown
Contributor

I'm sorry, but this appears to be incorrect: For my AWS::CloudFront::Distribution resources, I need to set OriginAccessControlId to an actual ID as well as set S3OriginConfig to {}. If I remove the empty S3OriginConfig property, CloudFormation throws the following error:

Resource handler returned message: "Invalid request provided: Exactly one of CustomOriginConfig and S3OriginConfig must be specified" (RequestToken: xxx, HandlerErrorCode: InvalidRequest)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CloudFront Distribution does not allow Origin Access Control without empty S3OriginConfig object

2 participants