Hi,
I've already created a QuickSight account with a VPC connection setting to Redshift and got connected successfully.
I removed the QuickSight account and re-created an account with Managed Microsoft Active Directory authentication method. Then I cannot connect to Redshift when creating a data soure with a timeout error.
The VPC setting is the same as when without Active Directory.
- the same subnet id
- the same security group id
- DNS resolver is blank
How should I change the VPN setting or anything to get successfully connected with Redshift?
Thanks,
AWS 공식업데이트됨 9달 전
Hello, do you mean VPC configuration ? in the question there is a mix of references to VPN and VPC , I guess it should all refer to VPC but if you could clarify it would be helpful.
Another question is : do you have Active Directory integration with Redshift as well or are you using Redshift internal users? Thank you
Hi Flag, Thanks for your reaction. VPC configration! I fixed my mistakes in the question.
I use Redshift without Active Directory, with just Redshift users, which is actually an admin only... In other words, I want to configure the env like below. Active Dicrectory(in VPC) <-a-> Quick Sight <-b-> Redshift(in VPC) a: Login QuickSight with AD users. b: Login Redshift with a static admin user. I think we need a VPC configuration in b. Without Active Directory, I set configuration of b and there's no problem. But with AD, the same configuration doesn't work and no info to fix it...
Thank you, Michihiro