Comments

• 

  almost 2 years ago by mpiala | Reply

  slides from the AWS workshop: https://mysuse.sharepoint.com/:b:/s/suse-it-infra/EYUbSRf1y5NqAq9Owjh6cQB0ESOJnJRzx83P5d2EzTMA?e=j8miG1

×
Edit Comment 7457
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
slides from the AWS workshop: https://mysuse.sharepoint.com/:b:/s/suse-it-infra/EYUb_SRf1y5NqAq9Owjh6cQB0ESOJnJRzx8_3P5d2EzTMA?e=j8miG1
 
×
Reply to mpiala
slides from the AWS workshop: https://mysuse.sharepoint.com/:b:/s/suse-it-infra/EYUbSRf1y5NqAq9Owjh6cQB0ESOJnJRzx83P5d2EzTMA?e=j8miG1
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 2 years ago by mpiala | Reply

  and recording of the workshop: Gen AI with AWS-20231106_130308-Meeting Recording.mp4

×
Edit Comment 7520
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
and recording of the workshop: [Gen AI with AWS-20231106_130308-Meeting Recording.mp4](https://mysuse.sharepoint.com/:v:/s/suse-it-infra/EWQV5p5Cp_VDsnKD5sm7XhkBhvhcwwXG_9eAuwRQkABLPg?e=fSN5ec&nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZyIsInJlZmVycmFsQXBwUGxhdGZvcm0iOiJXZWIiLCJyZWZlcnJhbE1vZGUiOiJ2aWV3In19)
 
×
Reply to mpiala
and recording of the workshop: Gen AI with AWS-20231106_130308-Meeting Recording.mp4
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  almost 2 years ago by vadim | Reply

  @mpiala now that we all have some hands on experience with bedrock I suggest that you create a few workgroup sessions for tomorrow / Thursday and invite contributors. I'd split the work into three workstreams:

  1. Create infrastructure / pipelines that would deploy the project in a reproducible way
  2. Create a crawler that would parse the source data and populate a vector database (probably a lambda that can be triggered by cloudwatch)
  3. Create a backend that would query the vector DB, run inference and integrate with slack

  For vector DB we can use something off the shelf, like pinecone.io - later we can move it to Athena or something else.

×
Edit Comment 7532
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
[@mpiala](/users/mpiala) now that we all have some hands on experience with bedrock I suggest that you create a few workgroup sessions for tomorrow / Thursday and invite contributors. I'd split the work into three workstreams: 1. Create infrastructure / pipelines that would deploy the project in a reproducible way 2. Create a crawler that would parse the source data and populate a vector database (probably a lambda that can be triggered by cloudwatch) 3. Create a backend that would query the vector DB, run inference and integrate with slack For vector DB we can use something off the shelf, like pinecone.io - later we can move it to Athena or something else.
 
×
Reply to vadim
@mpiala now that we all have some hands on experience with bedrock I suggest that you create a few workgroup sessions for tomorrow / Thursday and invite contributors. I'd split the work into three workstreams:
1. Create infrastructure / pipelines that would deploy the project in a reproducible way
2. Create a crawler that would parse the source data and populate a vector database (probably a lambda that can be triggered by cloudwatch)
3. Create a backend that would query the vector DB, run inference and integrate with slack
For vector DB we can use something off the shelf, like pinecone.io - later we can move it to Athena or something else.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview