-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Create AWS Data Sync Instance #5175
Comments
requires defined architecture before planning |
Meeting scheduled for 29/08/24 to discuss scope and technical architecture for this work |
I have the service account credentials from Gwion and have put them into 1Password |
To be discussed at refinement. |
Reached out to @ministryofjustice/modernisation-platform about adding their shared platform VPC into our ingestion account |
Have agreed with @ministryofjustice/modernisation-platform that this isn't a problem, we can add shared VPC, will inspect environment code in modernisation-platform and modernisation-platform-environments |
shared VPC added to ingestion account, however upon further reading Data Sync does not support shared VPCs |
Plan is to create VPCs using existing, soon to be retired, never connected to MoJ TGW, ranges from MP |
VPC build-out in progress, EC2 instance build-out also in progress. However the DataSync registration is not programatic, the DataSync server needs to be accessible from whatever machine is running Terraform/registering manually in the console. This is problematic because
Do I open the endpoint to GitHub Actions? GlobalProtect? Do I add userdata to install SSM agent and write the activation key to Secrets Manager? I don't even know if the activation key is held on disk or if I'd to run a command... |
10/10/24 update:
|
16/10/24 update:
TODO:
|
Currently blocked by ministryofjustice/modernisation-platform#8275 |
Requested support from mod platform to help unblock this ticket |
NVVS/LAN&Wifi team have given me access to https://github.com/ministryofjustice/deployment-tgw, so I'm not as blocked as last week 🙏 |
Moving back to blocked pending information on connecting to DOM1 from AWS |
🎉 I am able to connect to DOM1 from my debugging instance! 🎉 |
Reached out to ATOS because I can't access one of the locations |
Have reached out to @gwionap for clarification on source data |
Updated locations received from @gwionap, will continue. |
Have created a task but is failing... I can't explore this location with smbclient from the debug instance either
have escalated to @gwionap |
A more verbose output from smbclient
Seeing the following in VPC flow logs
So maybe its the routing back from ATOS? |
SMB traffic is being dropped at the Palo Altos 💀 |
@bagg3rs has raised a demand with Tech Services |
Update from Demand here |
Things are happening in TS, just slowly. |
Blocked again, potential permissions issue on file server... |
Raised with ATOS using original request |
ATOS have asked us to raise a new request but we got around that by going through Networks Our DataSync user was added to a new group and once we switched to testing with I initiated a run yesterday, it detected 800k~ files but errored after 120k~ |
Spoken to @gwionap and the suggestion is to scope to a specific repository |
Source scoped as advised by @gwionap, schedule added for 2300 on Wednesday so will run tonight |
scheduled run failed, a variety of errors which I cannot via screenshot, but are:
|
I've triggered a new task with changes to reporting and verification ministryofjustice/modernisation-platform-environments@fdd8c9e |
Still failed, but did transfer some data. Pausing until new year, we have a catch up with OPG. |
Awaiting list of Excel databases to fetch |
Describe the feature request.
Describe the context.
We embarked on this originally earlier in the year, where the request came in for a datasync instance that would allow OPG to move various pieces of unstructured/semi-structured data (PDFs, Documents etc.) into the Analytical Platform, so that they could be accessed directly from the AP without having to download files from a fileshare and manually reupload them. This would allow the data to be automatically replicated to our account from the fileshare, meaning analysts would be able to natively access all their files. This was for a good while pending the creation of a service account from ATOS, but said account has been created.
Work required:
We need to create an AWS Datasync Instance, and set it up to connect to/authenticate with the fileshare, using the service account provided by ATOS
Definition of done
The text was updated successfully, but these errors were encountered: