Complete S3 storage deployment and IAM policy configuration for Grafana backups#24
Open
leoleiden wants to merge 1 commit into
Open
Complete S3 storage deployment and IAM policy configuration for Grafana backups#24leoleiden wants to merge 1 commit into
leoleiden wants to merge 1 commit into
Conversation
Author
|
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Successfully deployed an AWS S3 bucket and configured the necessary IAM bucket policies to allow secure, credential-less access from the existing Grafana EC2 instance. All automated tests passed successfully.
Modifications & Troubleshooting
mate-grafana-backups-760583) for storing Grafana backups. Implemented anaws_s3_bucket_policyusing anaws_iam_policy_documentto grants3:ListBucket,s3:GetObject, ands3:PutObjectpermissions explicitly to the Grafana IAM role (grafana-role) created in the previous task.Connection timed outerror when attempting to SSH into the EC2 instance for testing. Diagnosed this as a firewall restriction and resolved it by updating the instance's Security Group inbound rules to explicitly allow SSH (Port 22) traffic.Result
Successfully SSH'd into the instance and verified the IAM permissions natively. Downloaded a test video via
wgetand securely uploaded it to the S3 bucket usingaws s3 cpwithout requiring explicit AWS credentials, proving the instance profile and bucket policies are working perfectly. The screenshot demonstrating the successful upload is included in the repository.