I'm setting up a Zabbix server in AWS using the Zabbix container on an AWS ECS cluster. It works, but "AWS by HTTP" can not reach monitoring.us-east-1.........
I tracked the problem down, and it's due the fact that an AWS ECS Service/Task that is configured to use awsvpc network mode can not have a public IPv4 address. And I an not using a NAT gateway. I assign public IPv4 addresses to the few (very few) instances that need to access the Internet. And use IPv6 to access AWS resources. To use IPv6 to access AWS services required a different URL, specifically "....api.aws" instead of ".....amazonapi.com". Digging to the AWS by HTTP scripts I see that they use "....amazonapi.com".
Can AWS by HTTP be updated to support IPv6? I.e. change "....amazonapi.com" to "....api.aws"?
I tracked the problem down, and it's due the fact that an AWS ECS Service/Task that is configured to use awsvpc network mode can not have a public IPv4 address. And I an not using a NAT gateway. I assign public IPv4 addresses to the few (very few) instances that need to access the Internet. And use IPv6 to access AWS resources. To use IPv6 to access AWS services required a different URL, specifically "....api.aws" instead of ".....amazonapi.com". Digging to the AWS by HTTP scripts I see that they use "....amazonapi.com".
Can AWS by HTTP be updated to support IPv6? I.e. change "....amazonapi.com" to "....api.aws"?