Hi, We are using Stingray at AWS using the standard Riverbed AMI's. We also have a VPC at Amazon were we host our backends. I have set up two Traffic Managers. Each has a VPC Elastic IP and can handle traffic for any of our backends. They are clustered and share their config fine. The last step to get fully fault tolerant is to assign them to a Traffic IP Group. When you try to create a Traffic IP Group via the admin console it only allows you to choose a EC2 Elastic IP. When you do this the Traffic IP Group doesn't work as that IP isn't managed by either Traffic Manager, they have their own VPC Elastic IP's. I can work around this by manually editing the config for the Traffic IP Group to use one of the VPC Elastic IP. However all traffic then only goes to the Traffic Manager that manages that IP and if that Traffic Manager is stopped the other Traffic Manager fails to take ownership of the elastic IP. The following error is given: Failed to release EC2 Elastic IP from use: This Elastic IP is not associated with this account. Is it possible to use a Traffic IP Group within an AWS VPC? Is seems I can get really close but it doesn't seem to cater for the difference between VPC Elastic IP's and EC2 Elastic IP's. Thanks, Paul.
... View more
