Instructions for mandatory SaaS integration config updates: AWS, Airbrake, Bitbucket, Pagerduty

Why do I need to update the configuration of my integrations?

We have updated several Datadog integrations to take advantage of new authorization APIs that our partners have rolled out. In order to use these updated integrations, you will need to update the configuration of these integrations.

The old versions of these integrations will continue to be supported for users with paid Datadog accounts until April 30, 2017.  Please update your integrations before then.

Can I roll the update right now?

AWS, Airbrake, Bitbucket and Pagerduty: yes, you can already update the configuration of these integrations.

How to update the configuration of my integrations?

First, check the integration configuration page. To access that page:

  1. Log into Datadog
  2. Select “Integrations” from the side bar menu
  3. Type the name of the integration in the search text box ("AWS" or "Airbrake" or "Bitbucket" etc.)
  4. Open the tile that bears the name of the given integration
  5. Click the “Configuration” tab

The information displayed there will indicate whether the integration needs a configuration update or not.

See details for each integration below:

Amazon Web Services

  1. If any AWS accounts are set up using Access Keys, you will need to update your AWS integration.
  2. If all of your AWS accounts are using Role Delegation, you do not need to update your AWS integration.

Note: Datadog does not support Role Delegation for AWS GovCloud or AWS China. Datadog will continue to support Access Keys for accounts in AWS GovCloud or AWS China. For all other accounts, only Role Delegation will be supported.

To update your AWS Integration, see https://help.datadoghq.com/hc/en-us/articles/210376966-Revoking-AWS-keys-and-enabling-Role-Delegation-for-the-Datadog-AWS-Integration

Airbrake

If the "Configuration" tab contains the following text, this means you will need to update your Airbrake integration:

WARNING: the method is deprecated and you are seeing this only because the integration was already configured at the time we switched to webhooks.

To improve security, first remove all your tokens by uninstalling this integration, then configure Airbrake to send events via webhooks following the instructions above.

If you do not see this warning, you do not need to update the Airbrake integration.

To update your Airbrake integration:

  1. Uninstall the integration by clicking the “Uninstall Integration” button
  2. Follow the instructions for “Setting up Airbrake Integration using webhooks”

Bitbucket

If the "Configuration" tab contains the following text this means you will need to update your Bitbucket integration:

Warning Your version of this integration is deprecated. Please note that if you enable webhooks on your repositories, you might get duplicate events. To upgrade, simply select 'Uninstall Integration', and install the Bitbucket integration again. You'll be required to re-enter your repo configurations.

If you do not see this warning, you do not need to update the Bitbucket integration. 

To update your Bitbucket integration:

  1. Uninstall the integration by clicking the “Uninstall Integration” button
  2. Follow the instructions for Creating Webhooks at https://confluence.atlassian.com/bitbucket/manage-webhooks-735643732.html . You will find the webhook url on the “Configuration” tab of the Bitbucket tile in Datadog.

Pagerduty 

If the "Configuration" tab contains the following text this means you will need to update your PagerDuty integration:

WARNING: Prior versions of this integration required a username and password to fetch PagerDuty Incidents. We now require a PagerDuty API Token. (To provide limited access to Datadog, we recommend creating a separate read-only API token, and providing it below.)

If you do not see this warning, you do not need to update the PagerDuty integration.

To update your PagerDuty integration:

  1. At the bottom of the tab, enter a PagerDuty API token and click “Update Integration” 
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk