rstrahan
commented
5 months ago Hi @SakthiPriyanka - thanks for logging this feature request.
I'm not sure (yet) what's involved in adding support for web sockets. I will add it to our backlog to investigate.
In the meantime can you please provide more details on what is required to be compliant and to make it work in your environment? For example you mention VPC pairing (peering) as a problem, but it's not clear if/how this maps to your request for web socket support. Also it's not clear if there are additional requirements related to VPCs, authentication, or anything else.
Can I also suggest that perhaps a faster path to success for you is to find an internal developer or hire an external developer/partner with experience building and deploying such web socket based slack apps for your environment, and have them fork our repo and adapt it to your needs - they can work closely with your slack admin team to ensure it will comply? We provide this is an open source project with MIT-0 license, so customers have 'carte blanche' to quickly customize and adapt it as needed to fit specific organizational environments.
We are unable to use the default architecture as we want to use in client's slack app. Please change the code to provide option to specify a custom VPC and enable socket mode feature in the code base.