Jay Raval

Thanks for the confirmation @MAN-Sendance. Could you perform a quick test on a non-production app? Follow these steps: 1. Connect a domain (using a third-party DNS provider) to an Amplify...

Hi @MAN-Sendance, just following up on my previous [comment](https://github.com/aws-amplify/amplify-backend/issues/1568#issuecomment-2237388628), did you get a chance to review and test it?

@MAN-Sendance thanks for sharing the results they are really helpful. Which third party DNS provider/registrar are you using?

@MAN-Sendance We apologize if the previous response came across as accusatory, that was certainly not our intention. We appreciate you taking the time to share your observations and highlight a...

👋 We have added this scenario to our custom domain troubleshooting guide here: https://docs.aws.amazon.com/amplify/latest/userguide/troubleshooting-custom-domains.html#multilevel-domain-is-stuck-in-the-pending-verification-state.

Hi @pjoe 👋 , thanks for raising this with us. To test the configuration of secrets with functions, I followed these steps: 1. Created a new Gen 2 backend using...

@pjoe thanks for sharing the screenshot. To ensure I understand correctly, I'd like to confirm that the `sharedPath` value shown is for a sandbox deployment, and not when using the...

Closing the thread since we cannot reproduce the outlined issue and the `sharedPath` value for the secret is expected in case of a sandbox deployment.

> Another issue: Openning custom headers on an application is not possible  > > then, trying to navigate to all apps is not working. It changes only the url,...

@TenetMax @dorutiuga Can you share your Amplify app id on which you are observing the custom headers issue?