Using an s3 link within a component is preventing component to be created properly in JCR. 

The double click on a folder/bucket makes also a strange reload of the background page.

You can find attached a light module EXTDAM-358-lm.zip decorating the mtk2 link component which you can use to reproduce the issue. Here are the steps:

• configure a workspace with S3 module and attached light module
• Start the instance
• Create a test page using mtk2 basic template
• Edit the test page, add a component in main area, choose link component, use a page link and select the test page for instance. Give it a title and save changes. (this step is just to really create a component and make the strange reload in background page more visible for next step)
• Add another component in main area, select s3 component and double click on a bucket. When double clicking on it, you can see a weird refresh in the background. Navigate into a folder containing an asset (still strange refresh on every double click), and choose an asset. Give it a title, save changes, and notice that the component is not added in the view. 
• Go in the JCR app, in test page of website workspace, you can see that page link nodes have been created in a component node, while s3 nodes resides at page root, and no component node got created. 

[EDIT on 20/05/2022 12:03]: I just updated the light module, adding a standalone s3 dam link field within the Link component form, to show that it doesn't relate to switchable field. You can also see that s3 link nodes are properly saved in JCR when used at page level. You can edit page properties of a basic page, a s3 link field is present there.