Closed SimonPPledger closed 1 month ago
This issue is stale because it has been open 90 days with no activity.
For public IP addresses we can get these via the MOJ AWS organisation-security
account through VPC IPAM (https://eu-west-2.console.aws.amazon.com/ipam/home?region=eu-west-2#PublicIpInsights).
For private IP addresses we would need to create and associate the relevant address pools in IPAM.
Here's a google doc that lists the info we already collect and also some ideas for more info to collect https://docs.google.com/document/d/1a7Q10SCiCGsxesWjOBC48sWa-3bzQWZ6/edit?usp=drive_link&ouid=106224495850523773839&rtpof=true&sd=true
The main takeaway for me is that we already have a lot of data but it is dispersed in multiple areas so some work could be done to aggregate the information if we want to simplify the process for a user to get access to it.
I presented this to the team today (6/8/24) - next steps are @SimonPPledger will review the info provided and suggest which actions to take forward as a priority. Any follow-up stories can be drafted as a result of this.
We discussed the outcomes of this spike and I'm happy that it's been completed.
User Story
As the modernisation product manager I need to have information about what is running on the modernisation platform. This enables us to respond in a timely manner to questions we get - eg what account do these IP relate to - but also so we know which members might be impacted by issues. This ticket is to look at the best way of doing this, including what information we need to capture - eg which environment (eg prod or non-prod) contact details, accounts, etc
Time boxed spike - 3 days
Value / Purpose
We can respond quickly to questions about the modernisation platform
Useful Contacts
No response
Additional Information
No response
Proposal / Unknowns
No response
Definition of Done