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 5 Next »

12 September 2018



Learn more and try it for free in: Bamboo

On this page:

Highlights

Use the new AWS Systems Manager (SSM) Parameter task to manage secrets and configuration data

You can now use the AWS Systems Manager Parameter task to get, put, and delete a parameter managed by the AWS Systems Manager Parameter Store, which provides a centralized store to manage your configuration data, whether plain-text data such as database strings or secrets such as passwords:

This allows you to separate your secrets and configuration data from your code. Parameters can be tagged and organized into hierarchies, helping you manage parameters more easily. For example, you can use the same parameter name, "db-string", with a different hierarchical path, "dev/db-string” or “prod/db-string", to store different values. Systems Manager is integrated with AWS Key Management Service (KMS), allowing you to automatically encrypt the data you store. You can also control user and resource access to parameters using AWS Identity and Access Management (IAM). Parameters can be referenced through other AWS services, such as Amazon Elastic Container ServiceAWS Lambda, and AWS CloudFormation.

Integration with AWS Secrets Manager

Update AWS Step Functions state machines

You can now also update state machines with the AWS Step Functions State Machine task, which already enables you to create, start, stop, and delete AWS Step Functions state machines:

AWS Step Functions makes it easy to coordinate the components of distributed applications and microservices using visual workflows. Building applications from individual components that each perform a discrete function lets you scale and change applications quickly. Step Functions is a reliable way to coordinate components and step through the functions of your application.

Use Amazon SQS as AWS Lambda event source

You can now use Amazon SQS as an event source with the AWS Lambda Event Source Mapping task – refer to the resp. introductory blog post for more details:

Use Docker volumes and private registry authentication with Amazon ECS

Resolved issues

Release 2.16.1

2018-09-19

This release addresses the following issues:

  • Bugs
    • TAWS-1610 – Update Identity Federation for AWS dependency from 2.10.0 to 2.10.1

Release 2.16.0

2018-09-12

This release addresses the following issues:

  • Stories
    • TAWS-1155 – As a user, I want a task to put/get/delete a Systems Manager (SSM) parameter so that I can use remote configuration
    • TAWS-1400 – As a user, I want a Step Functions State Machine task action to update state machines
  • Improvements
    • TAWS-1146 – Add support for timestamp starting position to Lambda event source mapping
    • TAWS-1383 – Refactor Utoolity in-product messaging towards 'apps' and lowercase product names
    • TAWS-1545 – Add support for SQS as Lambda event source
    • TAWS-1547 – Surface support for additional Step Functions region ap-south-1
    • TAWS-1561 – Integrate ECS support for private registry authentication
    • TAWS-1591 – Integrate ECS support for Docker volumes and volume plugins
  • Bugs
    • TAWS-1566 (UAA-350) – Log name of non existing region variable to ease analyzing configuration issues
    • TAWS-1570– Update available Elastic Beanstalk solution stacks (as per 2018-07-30)
    • TAWS-1571 – Update available Elastic Beanstalk solution stacks (as per 2018-08-15)
    • TAWS-1575 – Update available Elastic Beanstalk solution stacks (as per 2018-08-20)
  • Tasks
    • TAWS-968 – Drop support for Bamboo 5.10
    • TAWS-1446 – Drop support for Bamboo 5.11
    • TAWS-1526 – Drop support for Bamboo 5.12
    • TAWS-1565 – Drop support for Bamboo 5.13

  • No labels