mda590
Missing regions
https://github.com/mda590/cloudping.co/pull/18, https://github.com/mda590/cloudping.co/pull/29
https://github.com/mda590/cloudping.co/issues/3, https://github.com/mda590/cloudping.co/issues/7, https://github.com/mda590/cloudping.co/issues/26, https://github.com/mda590/cloudping.co/issues/28
us-gov-east-1
us-gov-west-1
cn-north-1
cn-northwest-1
~~ap-northeast-3~~
~~eu-west-3~~
~~eu-north-1~~
~~ap-east-1~~
~~me-south-1~~
All public regions have been added as of the launch of the new version of cloudping.
My hesitation with adding non-public regions up until this point (us-gov-east-1, us-gov-west-1, cn-north-1, cn-northwest-1, ap-northeast-3) is that I can only deploy this on one side. Thinking about this more, it would still be good data to have and I will work on getting this added.
If anyone has ideas for how I can deploy Lambda functions into any of the above non-public regions, I would love to figure that out so we can get complete bi-directional ping data.
All public regions have been added as of the launch of the new version of cloudping.
My hesitation with adding non-public regions up until this point (us-gov-east-1, us-gov-west-1, cn-north-1, cn-northwest-1, ap-northeast-3) is that I can only deploy this on one side. Thinking about this more, it would still be good data to have and I will work on getting this added.
If anyone has ideas for how I can deploy Lambda functions into any of the above non-public regions, I would love to figure that out so we can get complete bi-directional ping data.
Doesn't CDK or CF Template do it?
AWS upgrade ap-northeast-3 Osaka region from local to public standard on 2021/3/1, and Lambda is capable on this region https://aws.amazon.com/blogs/aws/aws-asia-pacific-osaka-region-now-open-to-all-with-three-azs-more-services/
I think it's time to enable Osaka(ap-northeast-3) in cloudping website
@mda590 https://aws.amazon.com/blogs/aws/now-open-aws-asia-pacific-jakarta-region/