Hi, Brandon! 👋 Our re:Post community of experts are always keen on sharing their knowledge when it comes to heavy-tech matters like this. 🤓 You're welcome to reach out to them, here: go.aws/aws-repost. 👈 Alternatively, check out this article for ways you can get tech help with your resources: go.aws/tech-support. 🧐 ^RF
Hi! Thanks for the video. When using this architecture with multiple tables is the best practice to have: 1 DMS migration task, 1 Kinesis data stream & 1 Glue streaming job per table? Or is there a way to process multiple tables at a time?
That's a great question, Matias! I've reached out to our Support team to ask, on your behalf. While we await their response, you can reach out to our community of experts in re:Post, who also may be able to help with this: go.aws/aws-repost. ^KR
What will be the best practice for using multiple tables in the stream ? Also do we need to keep the streaming glue job running all the time ?
When setting up Kinesis as a Target endpoint, do we not need to create a VPC Endpoint?
Hi, Brandon! 👋 Our re:Post community of experts are always keen on sharing their knowledge when it comes to heavy-tech matters like this. 🤓 You're welcome to reach out to them, here: go.aws/aws-repost. 👈 Alternatively, check out this article for ways you can get tech help with your resources: go.aws/tech-support. 🧐 ^RF
Hi! Thanks for the video. When using this architecture with multiple tables is the best practice to have: 1 DMS migration task, 1 Kinesis data stream & 1 Glue streaming job per table? Or is there a way to process multiple tables at a time?
That's a great question, Matias! I've reached out to our Support team to ask, on your behalf. While we await their response, you can reach out to our community of experts in re:Post, who also may be able to help with this: go.aws/aws-repost. ^KR