Open
Description
Fortunately AWS has finally started to offer an IP ranges API, see AWS Public IP Address Ranges Now Available in JSON Form - they are expected to change several times per week, so we need to decide whether to either automate the integration or drop the respectively outdated ranges within missingcloud.
- While at it, integration of
eu-central-1
should also be handled ideally.
This project's goal has been to make missing cloud-related data available in a format that you can use programmatically, which is now the case for most of the listed stuff, though some gaps remain.
@garnaat - can you judge/recommend the most reasonable way forward from here:
- maintain missingcloud as is and automate IP ranges integration
- maintain missingcloud as is and remove IP ranges integration in favor of the readily available AWS IP Address Ranges
- decommission missingcloud in favor of the readily available AWS IP Address Ranges, plus somehow reusing the substantially improved 'missing data' generation meanwhile facilitated in boto/botocore (presumably from AWS internal docs/APIs) for the non IP address aspects (e.g. /botocore/data/aws/ec2/2014-06-15.api.json)
- ❗ this would still lack EC2 instance type details like memory/storage/CPU I think, which could be partially scraped from the official listing though for example
Metadata
Metadata
Assignees
Labels
No labels