AWS Network Firewall integration

[taylor-swanson]

What does this PR do?

This PR adds a new integration for AWS Network Firewall.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

How to test this PR locally

cd packages/aws
elastic-package test pipeline

Related issues

Relates #1204

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-12-13T19:38:19.718+0000

• Duration: 27 min 1 sec

• Commit: 6d7ba48

Test stats 🧪

Test	Results
Failed	0
Passed	315
Skipped	0
Total	315

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[andrewkroh]

Nice dashboards

[andrewkroh]

We should get the integrations team to review as well since they own the package.

[kaiyan-sheng]

Hi @taylor-swanson , this looks great!! One small thing: on the dashboard, could you edit the visualization title so [Logs AWS] and [Metrics AWS] don't show? [Logs AWS] and [Metrics AWS] should still be a part of the visualization title but just not displayed on the dashboard. Thanks!

[taylor-swanson]

Hi @taylor-swanson , this looks great!! One small thing: on the dashboard, could you edit the visualization title so [Logs AWS] and [Metrics AWS] don't show? [Logs AWS] and [Metrics AWS] should still be a part of the visualization title but just not displayed on the dashboard. Thanks!

I can certainly do that!

[taylor-swanson]

The visualizations have been updated to not include [Logs AWS] or [Metrics AWS] (on the dashboard itself). I also split the custom action packets from the rest of the packet metrics. If a customer didn't set up custom actions, this actually broke the graph (one of the vertical axes was missing).

I can also collect new/updated screenshots, but I may hold off on that until any other issues are addressed. It's a bit cumbersome to get data to show up on the dashboards as I have to push live traffic through AWS.

[kaiyan-sheng]

Looks good to me!

[jamiehynds]

@kaiyan-sheng anything stopping us from pushing this integration to production, or is there a need to wait until the next stack release?

[kaiyan-sheng]

@jamiehynds Nothing is stopping us from pushing this to production 🙂 We just haven't done a package promotion in a while for AWS. Let me run the promote command right now.

[jamiehynds]

Thanks @kaiyan-sheng! On a related note, I created this issue to discuss automation of package promotion if you want to chime in: elastic/elastic-package#642

Once AWS Network Firewall is promoted, I'll get it added to the integrations page on the website and on the docs site too.