-
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
Eliminate long-lived IAM access keys. #1895
Comments
|
This was referenced Mar 14, 2024
Created a PR to remove Fog from specialist-publisher: alphagov/specialist-publisher#2575 |
I think dependency of Fog has also been removed from content-data-admin: alphagov/content-data-admin#1377 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A few GOV.UK applications are still using long-lived IAM creds (
AKIA...
access keys) to authenticate to AWS services such as S3. This dates all the way back to when GOV.UK was hosted outside AWS in colo facilities. We shouldn't be using these any more.We've already dealt with most of the easy cases. The remaining ones are probably just the few apps that use Fog. Fog rolls its own when it comes to authenticating to AWS and doesn't work well with the more modern authentication methods like instance profile and IRSA.
alphagov/content-data-admin#1377 and alphagov/support-api#911 are examples of replacing Fog with the standard AWS client library.
We can then use instance profile creds or IRSA for these apps and get rid of the long-lived keys and the secrets that store them.
The text was updated successfully, but these errors were encountered: