Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be able to get Amplify project DNSSEC compliant #3906

Open
3 tasks done
wouterlemcke opened this issue Jan 26, 2024 · 5 comments
Open
3 tasks done

Be able to get Amplify project DNSSEC compliant #3906

wouterlemcke opened this issue Jan 26, 2024 · 5 comments
Labels
feature-request New feature or request

Comments

@wouterlemcke
Copy link

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

Describe how you'd like this feature to work

We would like to see a way to solve the DNSSEC issues

@wouterlemcke wouterlemcke added the feature-request New feature or request label Jan 26, 2024
Copy link

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!

@mauerbac
Copy link
Member

Ack'ing this. Just shared with the team.

@mauerbac mauerbac reopened this Jan 26, 2024
Copy link

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.

@wouterlemcke
Copy link
Author

Any updates on this?

@wouterlemcke
Copy link
Author

wouterlemcke commented May 28, 2024

@mauerbac We would really like to get this fixed. Any ETA on when we could expect a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants