Description of problem:
When accessing AWS we would like to use a VPN with a custom endpoint URL.
Version-Release number of selected component (if applicable):
Could you please provide a bit more detailed info, how this custom endpoint should look like and how it would be configured in the application?
We use several aws services and their endpoints are constructed via the region.
e.g. we use sns, ec2, sqs etc
Would you provide a custom endpoint for each service?
Or a pattern?
And how would a region come into play?
Would you configure the endpoint on a appliance basis or per provider/manager?
There is an :endpoint parameter that can be passed in when connecting to an AWS service, see:
Can you dig into this a bit and see what sort of solution you can come up with. Let me know if you need more clarity around the requirements.
One option would be to control this through config/settings.yml the same way we control proxy settings.
However, that would be a global setting, and it sounds like we need to do this on a per-provider basis. We could still do it through config/settings.yml but the users would have to match their provider name and enter that themselves. So it would be something like:
From there we modify connect (or raw_connect) to use that setting.
Otherwise we'll need to create a new column in ext_management_system (or overload an existing one that isn't being used by our Amazon provider) and use that, along with a UI change, to allow users to set an endpoint.
Verified in 18.104.22.168. I added endpoint to VPC and then was able to add cloud provider from appliance from same region with that VPC endpoint.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.