Oracle Cloud VCN Flow Logs via Cloud Object Storage Setup
Console Steps
Create User Group
- Using the search bar type "identity" and click "Groups" under Services to be brought to the configuration page.
- Click "Create Group"
- Fill in the name and description. You can optionally add your desired tags.
Create Access Policy
- Using the search bar type "identity" and click "Groups" under Services to be brought to the configuration page.
- Click "Create Policy"
- Fill in the name and description. You can optionally add your desired tags under advanced.
- Choose the compartment to limit the policy to.
- Next to Policy Builder click "Customize"
- Fill in the following policies. Replace groupname with the group we created. Replace region with the region the object storage being used is in. Tenancy can be replaced with a stricter scope such as a compartment.
allow group <groupname> to read object-family in tenancy
allow group <groupname> to read virtual-network-family in tenancy
allow group <groupname> to read instance-family in tenancy
allow service objectstorage-<region> to manage object-family in tenancy
Create User
- Using the search bar type "identity" and click "Users" under Services to be brought to the configuration page.
- Click "Create User"
- Fill in the name and description.
- You can optionally add an email address and your desired tags under advanced.
- Click on the user you just created and click "Add User to Group" then select the group we created. Click "Add"
- In the User Information tab click "copy" next to "OCID". Make note of this as it will be used in the Netography portal.
Create Flow Logs
You can enable flow logs for a given subnet, which means traffic is logged for all the existing and future VNICs in that subnet. Each flow log record contains information about traffic for a single VNIC. After flow logs are enabled for a subnet, a batch of flow logs for each VNIC is collected in one-minute capture windows. It takes under eight minutes to process a batch, after which the flow logs are available for viewing.
- Using the search bar type "virtual" and click "Virtual Cloud Networks" under Services to be brought to the configuration page.
- Select the subnet you wish to turn flow logs on.
- Click the toggle under "Enable Log"
- Select the proper compartment
- Select your log group or click "Create New Group"
- Enter the desired log name
- Leave retention period default
- Check "Enable Legacy Archival Logs"
- Click "Enable Log"
Create Service Connector
- Go to the Logging section and select the Service Connectors option
- Click Create Service Connector
- Populate details for Connector name and the description.
- Click Create.
Setup Object Lifecycle
To reduce the amount of flow logs in object storage you can configure an object lifecycle to expire objects after a number of days.
- In the bucket you just created click "Lifecycle Policy Rules"
- Enter a name for your policy
- Ensure "Objects" is the target.
- Select "Delete" for Lifecycle Action
- Enter your desired days after which the objects expire.
- Ensure state is enabled
Obtain Tenancy OCID
-
Click on your profile icon in the upper right.
-
Click on Tenancy.
-
Under Tenancy Information click copy next to OCID.
Netography Portal Steps
Navigate to Traffic Sources, and click "Add Traffic Source", then select Oracle COS
Configuration
The following fields are specific to the Oracle COS configuration.
Field | Required | Description | Example |
---|---|---|---|
Region | yes | Location of the flow source | us-sanjose-1 |
Bucket | yes | The COS bucket name | |
Prefix | Optional folder prefix |
Authentication
The following fields are necessary for the integration to authenticate with Oracle COS.
Account Name | yes | The account name to use for this stream |
---|---|---|
User OCID | yes | Oracle assigns each user a unique ID called an Oracle Cloud ID (OCID) |
Tenancy OCID | yes | Every Oracle Cloud Infrastructure resource has an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID) |
To complete the authentication setup, you will need to obtain the public key and fingerprint that will be generated automatically after the form is submitted. Once the integration is created in the Netography Portal, return to edit the Flow Source that was just created.
Make note of the public key and fingerprint. This information will be used in the post configuration step within COS.
Console Steps (Continued)
This step uses the public key generated after configuring the Cloud Provider in the Netography Portal.
Add API Key to User
-
Click "API Keys" and Add Public Key
-
Select paste public keys and paste the public key.
-
You should now see a fingerprint and it should match the fingerprint for the public key.
Updated 3 months ago