Difference between revisions of "AWS S3 VPC Flow Log Access"
From Observer GigaFlow Support | VIAVI Solutions Inc.
Line 10: | Line 10: | ||
After installation, perform the following steps: | After installation, perform the following steps: | ||
# Add a role to your AWS instance with the following permissions: | # 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": "*" | ||
+ | : } | ||
+ | : ] | ||
+ | : } | ||
# 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). | # 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). | ||
# Numbered list item | # Numbered list item | ||
Line 15: | Line 42: | ||
# Numbered list item | # Numbered list item | ||
# Numbered list item | # Numbered list item | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 16:54, 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:
- 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": "*"
- }
- ]
- }
- 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).
- Numbered list item
- Numbered list item
- Numbered list item
- Numbered list item