[mdaniel]

Congratulations on the launch!

Because the href is `text-decoration:none`, this page appears to be blank: https://www.movinglake.com/docs/security/ only by hovering over "Data Privacy" does one realize it's a sub-page

I would guess in general the docs need some TLC, since https://www.movinglake.com/docs/destinations/http/ doesn't help me know what knobs I have influence over, as best I can tell "page 2" is the same as page 1 (https://www.movinglake.com/docs/destinations/page/2/), and for sure please do not require static AWS credentials (https://www.movinglake.com/docs/destinations/s3/) -- we actually have a Service Control Policy that outright bans the use of `iam:CreateAccessKey` across our entire AWS Org. Also, the "IAM view" is missing its protocol, causing the browser to think that the link is https://www.movinglake.com/docs/destinations/s3/console.aws....

[aleandros]

Thanks a lot for the feedback. You are absolutely right regarding the AWS credentials. We aim to fix it as soon as possible. And thanks a lot for pointing out the problems in the documentation. We we'll work on them ASAP!

[codeaken]

What are the other option(s) for AWS credentials which would be more secure in this scenario?

[aleandros]

The target account would need to allow explicit access to our account via an AWS policy. See the docs: https://aws.amazon.com/premiumsupport/knowledge-center/cross...

This is actually the approach we take for connecting to Google Services.

[mdaniel]

sts:AssumeRole or its friend sts:AssumeRoleWithWebIdentity