You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have removed any sensitive information from my code snippets and submission.
Amplify Hosting feature
Frontend builds
Is your feature request related to a problem? Please describe:
We're hosting our React front-end application using AWS Amplify. We use a custom (sub)domain, which resolves and works from the browser.
However we noticed that the subdomain has DNSSEC issues and it seems impossible for us to solve this. We do not manage the cloudfront distribution that is being created by Amplify and cannot change anything for this domain.
Describe how you'd like this feature to work
We would like to see a way to solve the DNSSEC issues
The text was updated successfully, but these errors were encountered:
This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Before opening, please confirm:
Amplify Hosting feature
Frontend builds
Is your feature request related to a problem? Please describe:
We're hosting our React front-end application using AWS Amplify. We use a custom (sub)domain, which resolves and works from the browser.
However we noticed that the subdomain has DNSSEC issues and it seems impossible for us to solve this. We do not manage the cloudfront distribution that is being created by Amplify and cannot change anything for this domain.
![image](https://private-user-images.githubusercontent.com/2428956/299967987-12cc9439-76a9-44e4-b2b6-f252336bad18.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTgxMDU2OTgsIm5iZiI6MTcxODEwNTM5OCwicGF0aCI6Ii8yNDI4OTU2LzI5OTk2Nzk4Ny0xMmNjOTQzOS03NmE5LTQ0ZTQtYjJiNi1mMjUyMzM2YmFkMTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDYxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA2MTFUMTEyOTU4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjJjZDUzOGNiNzU1NjczMzUwOGY0MjYyZjFlZTJkMDZmZmU5NmM4YmFhZTRkZDNhODk0ZTkyZjZlYWVmM2Y1OSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.FHoEPmUNsrxxXQSObh3ITvJuIPL5fWXMnkyPVqQ2MpU)
Describe how you'd like this feature to work
We would like to see a way to solve the DNSSEC issues
The text was updated successfully, but these errors were encountered: