Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Date

Authors

Philip Wilsdon (Unlicensed) John Simmons (Deactivated)

Status

Resolved

Summary

After AWS migration, numbers are in Reval are not the same.

Impact

https://hee-tis.atlassian.net/browse/TISNEW-5495

Root Cause(s)

  • AWS Migration - Whitelisting IPs with GMC

  • AWS Migration - authentication details - using old transform account

Trigger

  • AWS migration

Resolution

  • Requested GMC to whitelist IPs

  • workaround - scheduled job running everyday

Detection

  • Reported on Teams

Timeline

  • - 08:10

  • - 08:30 started to look into it

  • - 08:43 AM - email sent to GMC requesting whitelisting IPs

  • - 09:00 AM - started a data copy from azure to AWS to check PoC

  • - 11:30 AM - Completed PoC and wrote script to do the daily copy until the new IP’s are whitelisted

  • - 08:30 AM - missing data, suspected that another process interupted the sync, rerun the job and all is well.

  • - 10:45 AM - changed script run times.

  • - 3:30 pm - Phil rang the GMC to chase messages sent to the ISServiceManager@gmc-uk.org 

Action Items

Action Items

Owner

whitelist IPs

John Simmons (Deactivated)

Disable temp sync after whitelisting

John Simmons (Deactivated)

Lessons Learned

  • No labels