2020-02-19 12:12:28 -08:00
|
|
|
---
|
|
|
|
|
title: "Auditing Your Organization's Infrastructure as Code Activity"
|
2020-02-19 14:56:26 -06:00
|
|
|
date: "2020-02-20"
|
2020-02-19 12:12:28 -08:00
|
|
|
meta_desc: "Pulumi now supports Audit Logs. Learn how to audit your organization's infrastructure as code activity"
|
|
|
|
|
meta_image: "auditlogs.png"
|
|
|
|
|
authors: ["sean-holung"]
|
Filter blog tags to Top 40, and add back some metadata (#350)
* Only show the top 40 blog tags
In https://github.com/pulumi/pulumi-hugo/pull/215, I had suggested
that instead of physically deleting tags we didn't want to show, we
compute it algorithmically, by only showing the "Top N" tags. This
commit introduces said functionality.
This has a few advantages:
* Preserves old metadata (the authors added the tags because they
felt they were meaningful and captured information about the posts).
* Enables us to surface those tags differently in the future (who
knows, maybe someday we'll want to run a "spinnaker" campaign).
* Notably, also keeps the tag index pages, which Google has indexed.
* Enables us to add a "View More ..." link at the bottom of the
page if folks want to see the entire list.
* Perhaps most importantly, protects against future bloat. For
example, since this tag cleanup happened, we have added top-level
tags for "aliases", "app-runner", "iam", "open-source", and
"refactoring", each of which has only a single post.
I chose 40 as the N in Top N, because that's how many we show today.
I could see an argument for filtering this based on post count
instead (e.g., only those with >3 posts).
* Add back some tags
Now that we filter out unpopular tags, we can add back some of the
ones previously removed.
2021-06-21 17:31:35 -07:00
|
|
|
tags: ["features", "pulumi-enterprise", "audit-logs"]
|
2020-02-19 12:12:28 -08:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
We are excited to announce the release of Audit Logs on
|
|
|
|
|
[Pulumi](https://app.pulumi.com) for Enterprise organizations.
|
|
|
|
|
Audit logs enable you to track the activity of users within an
|
|
|
|
|
organization. They attempt to answer what a user did, when
|
|
|
|
|
they did it and where. They help answer these questions
|
|
|
|
|
by recording user actions.
|
|
|
|
|
|
|
|
|
|
Pulumi's audit logs allow you to account for the activity your
|
|
|
|
|
users are taking within your organization. These logs are available to
|
|
|
|
|
organizations with an Enterprise level subscription. The logs are immutable and
|
|
|
|
|
and record all user actions. Auditing makes the activity
|
|
|
|
|
of members in an organization attributable.
|
|
|
|
|
The logs capture the UNIX timestamp of the event, the user
|
|
|
|
|
who invoked the action, the event that took place, and the source IP
|
|
|
|
|
of the call the user made.
|
|
|
|
|
|
|
|
|
|
## Using Pulumi Audit Logs
|
|
|
|
|
|
|
|
|
|
Audit logs are available to organizations with an Enterprise level subscription
|
|
|
|
|
only. If you are an organization administrator, you can view your organization's audit logs,
|
|
|
|
|
by selecting your organization from the organization drop down. Then click on the settings tab.
|
|
|
|
|
On the left nav-bar you should see a tab called Audit Logs. Clicking here will allow you to view
|
|
|
|
|
the most recent audit logs for your organization.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This will show the most recent events in decending order. You can
|
|
|
|
|
also filter logs by a particular user by clicking on the user's avatar. Doing so will
|
|
|
|
|
filter out the events performed by the user you selected.
|
|
|
|
|
|
|
|
|
|
We are excited to make this feature available to our users.
|
|
|
|
|
Get started with audit logs on [Pulumi](https://app.pulumi.com) today.
|
