So this means that elb cannot be taken over

I had a good theory, created a engine to do it, invested a good time in that, lost 700$ in AWS costs with multiple accounts.
By my calculations it would need 27 years to match with an valid ELB.

Good luck.

I had a good theory, created a engine to do it, invested a good time in that, lost 700$ in AWS costs with multiple accounts.
By my calculations it would need 27 years to match with an valid ELB.

Good luck.

as I tought, elb can't been taken over. ec2 ip address on the other hand tho seem more interesting

I had a good theory, created a engine to do it, invested a good time in that, lost 700$ in AWS costs with multiple accounts.
By my calculations it would need 27 years to match with an valid ELB.
Good luck.

as I tought, elb can't been taken over. ec2 ip address on the other hand tho seem more interesting

Probably, never tried.

I had a good theory, created a engine to do it, invested a good time in that, lost 700$ in AWS costs with multiple accounts.
By my calculations it would need 27 years to match with an valid ELB.
Good luck.

as I tought, elb can't been taken over. ec2 ip address on the other hand tho seem more interesting

Probably, never tried.

It was fixed recently. You will only get a set of 4 to 5 IPs when you associate and release the IPs. Before you could iterate until receiving the wanted IP.

I went down the ec2 IP route a year or two back. I created a script that went through all their IP ranges in about 2 weeks. I found that it eventually it started giving me the same IPs again without giving me any that were available for possible takeover. I guess they have some long lease time on them preventing takeover.

Hey is this elb.amazonaws.com is vulnerable to takeover hah?? please