Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Revised/Expanded structure and meta information.
Section
Column
width64%

Identity Federation for AWS is

mainly

a

system integration and API

foundational Amazon Web Services integration add-on, which exposes resources via a REST API

- all

- this is the developer's guide to the Identity Federation for AWS REST API for developers who want to:

  • integrate Atlassian product's with AWS based DevOps scenarios
  • develop add-ons that enhance an Atlassian product's functionality by means of integrating AWS backed services
Column
width32%
Panel
bgColor#eeeeee

On this page:

Table of Contents

Getting started

 

The Identity Federation for AWS REST API is based on open standards, so you can use any web development language or command line tool capable of generating an HTTP request to access the API, e.g. the popular cURL (a CLI tool for transferring data with URL syntax) or the highly recommended HTTPie (a CLI, cURL-like tool for humans). All resources can be used like the regular JIRA REST API (or Stash REST API

...

, see info below):

 

Tip
titleREST API Browser

The easiest way to explore and experiment with the Identity Federation for AWS API is by means of the Atlassian REST API Browser, simply select the Identity Federation for AWS resources.

Include Page
_ARADGComplianceNote
_ARADGComplianceNote

Structure of the REST URIs

The Identity Federation for AWS REST API provides access to resources (data entities) via URI paths. To use the REST API, your application will make an HTTP request and parse the response. The Identity Federation for AWS REST API uses JSON as its communication format, and the standard HTTP methods like GET, PUT, POST and DELETE. URIs for Identity Federation for AWS REST API resources are keyed by the add-on namespace and have the following structure:

 

title
Code Block
/jira
http://host:port/context/rest/identity-federation-aws/1.0
Tip

REST API

...

The easiest way to explore the API is by means of the Atlassian REST API Browser, simply select the Identity Federation for AWS resources.

Column
width32%
Panel
bgColor#eeeeee

On this page:

Table of Contents

...

resources (Identity Federation)

This is the reference of all resources relevant to this add-ons actual functionality as a as a token vendor for Identity Federation - please see the REST API resources (complete reference) if you intent to include this add-on into administrative automation scenarios (e.g. for scripting).

ResourceURI templatemethodsdescriptionpermissionscomments
Connectors    (plus) This is the main resource to interact with currently in order to retrieve temporary AWS credentials.
 

/connectors

GETGet all AWS connectors.Configurable 
 /connectors/{id}GETGet an AWS connector identified by its id.Configurable.
 /connectors/{id}/credentialsGETGet the temporary security credentials via an AWS connector identified by its id.Configurable(lightbulb) This is the main resource to use for calling AWS Services in turn.

REST API resources (complete reference)

This is the complete reference of all resources available. You usually won't interact with most of these outside of administrative automation scenarios (e.g. for scripting) - please see the REST API resources (Identity Federation) for this add-ons actual functionality first.

ResourceURI templatemethodsdescriptionpermissionscomments
Accounts    (warning) You usually won't interact with accounts via the API currently, please see the Connectors resource instead!
 /accountsGET|POSTGet all accounts (IAM users).Administrator 
 /accounts/{id}GET|DELETE|PUTGet an account (IAM user) identified by its id.Administrator 
Connectors    (plus) This is the main resource to interact with currently in order to retrieve temporary AWS credentials.
 

/connectors

GETGet all AWS connectors.Configurable(info) You only need GET for the intended usage as a token vendor, but POST will be added in a subsequent release regardless.
 /connectors/{id}GETGet an AWS connector identified by its id.Configurable(info) You only need GET for the intended usage as a token vendor, but DELETE|PUT will be added in a subsequent release regardless.
 /connectors/{id}/credentialsGETGet the temporary security credentials via an AWS connector identified by its id.Configurable(plus) (lightbulb) This is the main resource to use for calling AWS Services in turn.

...