Remote actions and conditions with Amazon Web Services – automate your DevOps workflows from Jira Service Management and Jira
Remote actions and conditions with Amazon Web Services – automate your DevOps workflows from Jira Service Management and Jira
Remote actions and conditions with Amazon Web Services – automate your DevOps workflows from Jira Service Management and Jira
Automate remote systems from workflows & rules
Implement remote actions and conditions with AWS
Integrate third-party services with polyglot code
Run remote actions from Jira post functions & Jira Service Management rules to notify and automate remote systems via workflow transitions and automation rules. Inject contextual entity variables into the payload.
Publish SNS messages or Put EventBridge events to notify users (email/SMS) or trigger other services (SSM/SQS/...). Invoke Lambda functions for serverless logic. Start Step Functions executions for distributed workflows.
Use languages such as C#, Go (Golang), Java, Node.js (JavaScript), Python to run serverless code with AWS Lambda and integrate services like Twilio, PagerDuty & OpsGenie, Statuspage & Status.io, Slack & Microsoft Teams.
More details
Automation with AWS provides remote actions and conditions via Amazon Web Services so that you can notify and automate all the things from Jira Service Management automation rules and Jira workflows.
Integrations:
- Automate with AWS post function – extend Jira workflow post functions
- Automate with AWS then action – extend Jira Service Management automation rules
Remote actions:
- Invoke Lambda Function – integrate serverless business logic
- Publish SNS Message – send notifications via email, SMS, HTTPS
- Put EventBridge/CloudWatch Events – route events to other AWS services
- Put Systems Manager Parameter – persist secrets and configuration data
- Send SQS message – decouple distributed microservices
- Start Step Functions Execution – coordinate distributed workflows
- Start Systems Manager Automation Execution – manage AWS resources
Use cases:
- Notify users via mobile push, email, SMS
- Approve workflow transitions
- Trigger automation and alerts via HTTPS, SQS
- Provision IT resources
- And many more ...
Reviews for cloud
(0)Sign in to write a reviewThere are no reviews yet. Be the first to review this app.
Reviews for server
(0)Sign in to write a reviewThere are no reviews yet. Be the first to review this app.
Reviews for Data Center
(0)Sign in to write a reviewThere are no reviews yet. Be the first to review this app.
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$280 | 50 users$560 | 100 users$840 | 250 users$1,800 | 500 & upAdditional pricing details |
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Management (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Management, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
This app does not have a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.
However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Utoolity provides support for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.9.0 • Jira Server 8.0.0 - 8.16.0 • Released 2020-11-30
Summary
Adds SSM parameter action; adds IAM role for EC2/ECS credentials provider
Details
See the Automation with AWS 1.9 Release Notes for details – noteworthy changes:
- Evaluate remote conditions – use the Get Systems Manager Parameter action to …
- … conditionally run Jira Service Management automation rules with the Automate with AWS if condition
- … control Jira workflow transitions with the Automate with AWS workflow condition and Automate with AWS workflow validator
- Provide AWS security credentials via an IAM role for EC2/ECS – opt-in via a feature flag and gain convenience and flexibility by providing AWS security credentials via your Amazon EC2 instance or Amazon ECS and AWS Fargate tasks
- AAWS-739 – As a user, I want to get a Systems Manager (SSM) parameter so that I can check remote conditions
- AAWS-759 – Drop support for Jira 7.9
- AAWS-764 – Drop support for Jira 7.10
- AAWS-802 – Drop support for Jira 7.11
- AAWS-805 – Drop support for Jira 7.12
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Automation with AWS (Jira) via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Automation with AWS (Jira). You're prompted to log into MyAtlassian. Automation with AWS (Jira) begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Automation with AWS (Jira) versions compatible with your instance, you can look through our version history page.
Similar apps
