Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Current »

Tasks for AWS adds several Amazon Web Services (AWS) related tasks to deploy and operate AWS resources on demand. Administering the app comprises regular app maintenance as well as AWS integration and resource management.

On this page:

Related pages:

Administration

Maintaining the app

The following topics are applicable to regular app maintenance:

Managing AWS resources

The following topics are applicable to AWS resource management:

Configuring advanced scenarios

The following topics are applicable to advanced scenarios only:

  • Page:
    Configuring an Outbound HTTP(S) Proxy — If your Atlassian product instance is running behind a firewall, the app will reuse the proxy configuration from the Atlassian host application.
  • Page:
    Enabling Labs Features — Labs features are giving you a sneak preview of new features coming in future releases of Tasks for AWS. You can enable/disable each feature individually at any time.
  • Page:
    Configuring the AWS Client — The AWS API is eventually consistent only and also exhibits a customer specific dynamic throttling policy, both of which require respective retry logic to be in place. Accordingly the facilitated AWS SDK for Java features an exponential backoff strategy already, but its default retry number of 2-3 (accumulating to a retry window of up to ~4 seconds) has proven to be too low for the use case at hand. The values are configurable accordingly, with an increased default retry number of 7 (accumulating to a retry window of up to ~1 minute).

How-to Articles

Frequently Asked Questions (FAQ)

Atlassian account required

Due to a regression within Questions for Confluence Cloud, you need to log in with your Atlassian ID (or sign up for a new account) to access these automatically curated FAQs (refer to UAA-312 for the background).

  • No labels