วีดีโอ

Edit: no, it's not part of free tier. See q business pricing: aws.amazon.com/de/q/business/pricing/

To my knowledge that's not currently possible with Q. The way the LLM is trained seems to be more suited for an question - answer structure rather than the sort of task - solution type approach that OpenAI seems to aim at with ChatGPT. Also I haven't had great success with few-shot approaches using Q. You could however try Amazon Bedrock which includes the foundational models used by Q and many others! See here: th-cam.com/video/repAdkSfi2U/w-d-xo.html Glad you enjoyed the video :)

Hi @ramyashreeg1738, as of now there is unfortunately no direct API access for Q. However there is for Amazon Bedrock which Q is based on -- maybe this video will help: th-cam.com/video/repAdkSfi2U/w-d-xo.html

Great advice!

Amazon Q only has access to what you give to it. This can be company internal manuals or documents -- or public information you obtained elsewhere. So if you have that information available as raw data and can feed it to Q then yes, otherwise unfortunately no.

Web sitenizde hangi Bedrock özelliğini istersiniz? Eğer baştan sona bir sohbet robotu yapmak istiyorsanız, Amazon Q'daki videomu deneyebilirsiniz: th-cam.com/video/iJogoP2qAvU/w-d-xo.htmlsi=j9KtY6DJxf9UbTc0

Hi Pierre, thanks for your comment. To my knowledge Keycloak supports SAML so this should be possible. My suggestion would be to follow a guide to setup via SAML like this : scandiweb.com/blog/sign-in-to-amazon-aws-using-saml-protocol-and-keycloak-as-identity-provider/ And then follow the SAML related parts from one of the Q docs, like this one: docs.aws.amazon.com/amazonq/latest/business-use-dg/idp-okta.html

I'll be making a video about this in detail -- in the mean time you can try this: docs.aws.amazon.com/amazonq/latest/business-use-dg/rds-my-sql-connector.html

Hi Mark, thanks for your comment! What you are looking for is probably better covered by using Amazon Bedrock itself and embedding it into you website (maybe this helps th-cam.com/video/repAdkSfi2U/w-d-xo.html ) Q uses Bedrock under the hood and this can be used via API to direct questions and answers to your website. It is my understanding that AWS intends Q to be more of an in-house solution than a public one. If you look at the Amazon Q button on the AWS help page for instance: it also requires sign-up. Amazon Q or "QBusiness" as it's called internally is still in preview, so they might open it up at some point in the future.

@@Flowprodev-yp1tg Thanks for the additional information. I went through this video and set up two users and gave them permissions to the Q App but when I log in and verify with MFA I'm just getting a Permission Needed: 403 Forbidden error page. Is there any other IAM Permissions required for the user accounts in order to access it?

One note, I don't see "User Provisioning" when I'm in Amazon Q, I only see applications, this may be why I'm running into issues.

@@MarkMcAllister83 The User Provisioning option was removed by AWS so you can ignore that step. Regarding the 403 error -- this happened to me too sometimes and it went away after a few minutes/reloads. If you followed all the other steps then it should fix itself. If not, check out this page: docs.aws.amazon.com/amazonq/latest/business-use-dg/idp-troubleshooting.html

@@MarkMcAllister83I had same issue. I eventually opened in a different browser (chrome) and it started working!

That was referring to the 'user provisioning' step. However AWS has removed that since. So you should be good just ignoring that. Let me know if you run into any trouble.

@@Flowprodev-yp1tg First of all thank you very much for such a resource on Q deployment and also for replying to my query. 1)I have replicated all your steps and created one. 2)The web version is working but for the user after logging it shows you do not have any application. 3)Can I get u r email ID and share a snap.

That's great to hear! I believe AWS has removed that option entirely. Could you try just skipping that step and let me know if it works?

It looks like In order to deploy I need to set up the idp and provide that information to Q. I can then deploy but then I am prompted for a username as you demonstrate in your video which is then the blocker. I can atleast preview the experience which is helpful

The user needs to be added to the idp (without the now removed user provisioning). You should then be able to login with that information and setup 2nd factor auth etc. Feel free to share some details how and where exactly you are stuck. Does the system not recognize the user credentials?

It should work without deploying, I haven't tested it though. For security reasons I strongly recommend you do deploy, otherwise you have to be logged in with your AWS account to use it. Also the deployment itself is free

I dont think that is the correct link for the sitemaps :(

@@user-xo5fm1kv1i Thanks for catching that - here is the correct link: seocrawl.com/en/how-to-find-a-sitemap/

It's mostly that a company will use Q on internal documents -- so this could be the knowledge base with all the documents they have about a certain project. If then a new member joins the project they can ask Q all kinds of questions about the project, specifications, etc. It's very powerful not only for new project members but also saves a lot of time organizing and gathering information about what was decided or discussed in the past. I'll see if I can show a demo of one but most of the times clients do it with confidential information unfortunately.

What App where you connecting? Common problems include your account not being able to send audit logs (for instance Jira needs an Enterprise account) or faulty security settings. If you are sure that the app you are connecting support audit logs on your account I would suggest redoing the AppFabric connection from the start - maybe you have a typo 👻 Good luck 👍

@@Flowprodev-yp1tg okta app

I have set it up for multiple clients with exactly these steps; never ran into problem. If you want, DM me on LinkedIn and we can have a quick look. Have you checked the permission settings on Okta?

​@@Flowprodev-yp1tg Finally got it. Thanks. Previously The problem is rate limit and permission issues.

I added two folders for the lambdas in the github repo. Don't forget to run "pip install -r requirements.txt --target ." and zip. (In the future the included boto3 package included in lambda might get updated and this step will no longer be necessary)

@@Flowprodev-yp1tg thanks for your help! Is possible to include the code for "callCreateSessionLamda()" in your repo?

If your terraform takes input parameters the AWS Console should give you a text box to fill them in when you launch the product. However this is sometimes buggy I found. If you use the AWS CLI you can pass them in as -provisioning-parameter like this: [ { "Key": "string", "Value": "string" } ... ] see here awscli.amazonaws.com/v2/documentation/api/latest/reference/servicecatalog/provision-product.html