v1.1.2

If deploying v1.1.2 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.1.1 to v1.1.2, please read below

Due to an ongoing issue the CLOUDTRAIL_AUDIT_LOGS parameter is no longer optional but now a mandatory parameter that accepts the ARN of an existing Cloudtrail Lake event datastore.

If upgrading from v1.1.1 to v1.1.2, create a new Cloudtrail lake event datastore in the delegated admin account outside of TEAM and pass the ARN to the parameter.sh file as shown below:

CLOUDTRAIL_AUDIT_LOGS=arn:aws:cloudtrail:us-east-1:123456789101:eventdatastore/e646f20d-7959-4682-be84-6c5b8a37cf15

Warning
This change would delete the existing Cloudtrail lake event datastore created by TEAM as part of the Amplify deployment

Follow instructions in updating TEAM documentation for updating process

What's changed

Bug Fixes

• Fix - OU's not loading in Eligibility policy. see #235
• Fix - Only require approval if all eligibilities for a request require approval.
• Fix - Allow both acount and OU approvers

v1.1.1

If deploying v1.1.1 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.1.0 to v1.1.1, please read below

TEAM v1.1.1 introduces the use of custom domain instead of the default amplify generated domain name. To use a custom domain, ensure to update the parameters.sh in the deployment folder with UI_DOMAIN key and your custom domain name before running the ./update.sh script.

Follow instructions in updating TEAM documentation for updating process

What's changed

Feature enhancement

• This change introduces support custom domain instead of the default amplify generated domain name. see #32

v1.1.0

If deploying v1.1.0 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.0.0 - v1.0.6 to v1.1.0, please read below

You would have to reconfigure or update your notification source email address in the notification section of the TEAM settings page if you are using SES for email notification. See notification configuration

Follow instructions in updating TEAM documentation for updating process

What's changed

See #54 for more details

Feature enhancement

• This change introduces support for additional configuration options. Notifications are supported via Slack (#14), SNS (#20), and cross-account SES (#46). Users may also enable multiple notification services.
• The TEAM admin and auditor groups may also be changed after deployment. (#22)
• Hierarchichal view of OU structure during Eligibility and Approval policy configuration

v1.0.6

If deploying v1.0.6 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.0.0 - v1.0.5 to v1.0.6, please read below

Follow instructions in TEAM updating documentation for updating process

What's changed

See #62

Feature enhancement

With this change, users can be selective about the amount of logging they enable as part of their TEAM deployment. The CLOUDTRAIL_AUDIT_LOGS key is added to parameters.sh. The options are:

• read_write - record read and write events
• read - record only read events
• write - record only write events
• none - disable event logging

Depending on an organisation's regulatory and governance requirements, this can help to significantly reduce the cost of deploying the TEAM solution.

Documentation

• Deployment
• Cost considerations
• Security consideration

v1.0.5

If deploying v1.0.5 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.0.0 - v1.0.4 to v1.0.5, please read below

Follow instructions in TEAM updating documentation for updating process

What's changed

Feature enhancement

Ability to add custom tags to Amplify created resources by adding a TAGS key to the parameters.sh file - see #29

v1.0.4

If deploying v1.0.4 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.0.0 - v1.0.3 to v1.0.4, please read below

Follow instructions in TEAM updating documentation for updating process

What's changed

Bug fix - Issue with the latest version of pipenv(2023.6.26) which is used by the Amplify build pipeline to package the backend python lambda functions. Updated Amplify buildspec to use the most recent stable version of pipenv(2023.6.12). see #21

v1.0.3

If deploying v1.0.3 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.0.0..v1.0.2 to v1.0.3, please read below

Follow instructions in TEAM updating documentation for updating process

What's changed

Bug fix - Pagination error when fetching groups or permissions from IAM Identity center - See #16

v1.0.2

If deploying v1.0.2 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.0.0..v1.0.1 to v1.0.2, please read below

Follow instructions in TEAM updating documentation for updating process

What's changed

Bug fix - Admin/ eligibility policy route not working if no permission set is assigned or configured for the organization management account. See #12
Dependency - Updated amplify version.
Bug fix - updated deployment scripts. See #9 and #10

v1.0.1

If deploying v1.0.1 directly to your environment

Follow instructions in TEAM deployment documentation for deployment process

If upgrading from v1.0.0 to v1.0.1, please read below

Follow instructions in TEAM updating documentation for updating process

What's changed

Bug fix - If you disable Ticked ID as as a mandatory field, Eligibility and Approvers cannot be defined. There appears a green banner saying the operation was successful, but the eligibility and/or approver is not saved and the corresponding DynamoDB tables are not populated.