AWS::CloudFront::Distribution Custom Response Headers

aws-cloudformation / cloudformation-coverage-roadmap

The AWS CloudFormation Public Coverage Roadmap

https://aws.amazon.com/cloudformation/

Creative Commons Attribution Share Alike 4.0 International

1.11k stars 54 forks source link

AWS::CloudFront::Distribution Custom Response Headers #969

Open ueokande opened 2 years ago

ueokande commented 2 years ago

Name of the resource

AWS::CloudFront::Distribution

Resource name

No response

Description

CloudFront Distribution now provides custom response headers. https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-cloudfront-supports-cors-security-custom-http-response-headers/

It is available on the CloudFront Console and the APIs. I hope the CloudFormation also supports it.

Other Details

No response

ueokande commented 2 years ago

ResponseHeadersPolicyId is now available. Thank you.

GrahamCampbell commented 2 years ago

@zjinmei While this appears in the docs, it doesn't actually work on us-east-1 (as of this time yesterday). My document is rejected with error #/DistributionConfig/DefaultCacheBehavior: extraneous key [ResponseHeadersPolicyId] is not permitted.

GrahamCampbell commented 2 years ago

cc @ueokande

GrahamCampbell commented 2 years ago

Tried it again just now. Same issue.

GrahamCampbell commented 2 years ago

Any news here? Excited to use this, but am blocked on this.

homie-du commented 2 years ago

I am experiencing the same issue when I use serverless framework.

serverless.yml

CF:
  Type: AWS::CloudFront::Distribution
  Properties:
    DistributionConfig:
      DefaultCacheBehavior:
        AllowedMethods:
          - DELETE
          - GET
          - HEAD
          - OPTIONS
          - PATCH
          - POST
          - PUT
        ResponseHeadersPolicyId: a323da2a-065c-43c9-a263-289cf629c834

result

An error occurred: CF - Properties validation failed for resource CF with message:
#/DistributionConfig/DefaultCacheBehavior: extraneous key [responseHeadersPolicyId] is not permitted.

GrahamCampbell commented 2 years ago

This appears to be fixed now. :)

peterwoodworth commented 2 years ago

It seems this isn't present in all regions yet. I've confirmed it's not present in af-south-1 - see here