Difference between revisions of "AWS S3 VPC Flow Log Access"
Line 39: | Line 39: | ||
} | } | ||
'''2.''' Generate an Access Key ID and password and add them to your AWS CLI configuration (see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html). | '''2.''' Generate an Access Key ID and password and add them to your AWS CLI configuration (see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html). | ||
+ | |||
'''3.''' Run the following commands from the CLI, to test your configuration: | '''3.''' Run the following commands from the CLI, to test your configuration: | ||
Revision as of 17:22, 25 August 2022
Observer Gigaflow uses the Amazon Web Services (AWS) Command Line Interface (CLI) tools to access AWS services. You can install the latest version of the CLI tools for AWS system from https://aws.amazon.com/cli/.
Note: The CLI tools must be configured with the same user used to run Gigaflow for it to be able to access the configuration profile. For Linux, you can use the "su" command to choose the correct user and then run the AWS CLI commands. |
After installation, perform the following steps:
1. Add a role to your AWS instance with the following permissions:
- S3 List/Read/Download
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:Get*", "s3:List*", "s3-object-lambda:Get*", "s3-object-lambda:List*" ], "Resource": "*" } ] }
- EC2 List/Read/Describe
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "ec2:Describe*", "Resource": "*" } ] }
2. Generate an Access Key ID and password and add them to your AWS CLI configuration (see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html).
3. Run the following commands from the CLI, to test your configuration:
aws ec2 describe-instances aws s3 ls s3:// aws ec2 describe-flow-logs