@ahmad7110 thanks for the insight! I’m not wholly familiar with the ELB technology, so this may require some further research on our side. Additionally, there may be some specific configuration aspects to your site that may be contributing to the issue.
The key is ensuring your canonical, original page is accessible to search engines. In the source code of the page, there should be a clear link to the AMP version of the site.
So on your canonical page: https://7yatak.net/%D8%A7%D9%81%D9%84%D8%A7%D9%85-%D9%83%D9%8A%D9%81%D9%8A%D9%86-%D9%87%D8%A7%D8%B1%D8%AA-%D9%88-%D8%AF%D9%88%D9%8A%D9%86-%D8%AC%D9%88%D9%86%D8%B3%D9%88%D9%86-%D8%A8%D8%A8%D8%B7%D9%88%D9%84%D8%A9-%D9%85/
The source code should have this reference to the AMP page as it currently does now:
<link rel="amphtml" href="https://7yatak.net/%D8%A7%D9%81%D9%84%D8%A7%D9%85-%D9%83%D9%8A%D9%81%D9%8A%D9%86-%D9%87%D8%A7%D8%B1%D8%AA-%D9%88-%D8%AF%D9%88%D9%8A%D9%86-%D8%AC%D9%88%D9%86%D8%B3%D9%88%D9%86-%D8%A8%D8%A8%D8%B7%D9%88%D9%84%D8%A9-%D9%85/?amp">
Previously, the canonical/ original page had AMP HTML in the source code which is incorrect.
Since you are using a paired serving method through Transitional mode correct non-AMP and AMP versions need to be accessible.
Based on your configuration at Cloudfront, are there options that alters the source code or could potentially serve a cached AMP version on the original page (perhaps Cloudfront support can also provide insight)?