2 Answers
- Newest
- Most votes
- Most comments
0
I'd normally encourage you to raise a support case here; but as you point out you have no paid support.
Depending on the criticality of this issue I would consider paying for support in order to get assistance with this - from here (re:Post) there's not a lot that we can do with this issue; we're all volunteers and we have no visibility into user identity; accounts; services; etc.
0
As a step forward, I've reported this as an error in the Cloudfront documentation, since this error should be documented.
answered 2 years ago
Relevant content
- Accepted Answerasked 2 years ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thanks. Paying to access support to report a bug to AWS staff seems sub-optimal...
Is it a bug? Don't know. Could be. Might not be. Could be some other cause. Without knowing the account number, request identifiers, times, dates and all that other information there's no way to say. Hence my encouragement to engage with the support team.