There is no ability to share the current buffer(s) for context, no tool support. This seems like a checkbox release. You’re better off using CodeCompanion with Amazon Bedrock, which includes the added benefit of sovereignty.
Most big players in the LLM field are getting their training data by at-least shady, if not illegal measures.
And if they don't care about laws on one side, why should anyone believe that they care on the other?
Amazon already uses their customers privat data to train models [1].
[1] https://www.ftc.gov/business-guidance/blog/2023/06/hey-alexa...
And yes, it’s literally written in their documentation.
https://aws.amazon.com/q/developer/faqs/#topic-1
“ For users who access Amazon Q Developer with the Pro Tier, your content is not used for service improvement, or to train any underlying foundation models (FMs). Unless explicitly opted out, content from Amazon Q Developer Free Tier might also be used to enhance and improve the quality of FMs. Your content will not be used if you use the opt-out mechanism described in the documentation. For more information, see Sharing your data with AWS.”
So while restating the obvious in these cases is very good, it's also good to point out when.
“ “For users who access Amazon Q Developer with the Pro Tier, your content is not used for service improvement, or to train any underlying foundation models (FMs). Unless explicitly opted out, content from Amazon Q Developer Free Tier might also be used to enhance and improve the quality of FMs. Your content will not be used if you use the opt-out mechanism described in the documentation. For more information, see Sharing your data with AWS.”
I do not consider Amazon a company that lies about this type of stuff?
It’s like Amazon’s Chime to everyone else’s Zoom. It works, but unless you have no other option it’s not clear why I’d choose to use it.
Think back to when they (MSOFT) were putting out tools like TypeScript, WSL, and VS Code. It looks like Amazon is doing something similar now, building cool tech for developers without plastering the AWS brand all over it.
> After installation, authenticate through IAM Identity Center or AWS Builder ID.