CDK construct to apply common tags to constructs

To apply the common set of tags for a s3 bucket:

import { applyTags, SecurityClassification, BackupSchedule } from '@linzjs/cdk-tags';

const bucket = new Bucket(this, 'ImageryArchive');

applyTags(bucket, {
  application: 'basemaps',
  environment: 'prod',
  group: 'li',
  classification: SecurityClassification.Unclassified,
  data: { isMaster: true, isPublic: true, role: 'archive' },
  impact: 'moderate',
  backup: {
    retention: 365,
    schedule: BackupSchedule.WEEKLY,
    multiRegionCopy: true,
  },
  log_streaming: {
    filter_pattern: 'ERROR' // pattern syntax - https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/FilterAndPatternSyntax.html
  }
});

Set backup.multiRegionCopy: true to declare the the backups have to be available in second region. (tag applied: linz.backup.multiRegionCopy, default: false).

Set backup.multiAccountCopy: true to declare that the backups have to be available in a logically air-gapped (LAG) vault shared by the central audit account. Backups stored in the LAG vault cannot be deleted prior to the completion of the retention period, hence the retention period will be capped to 30 days.

To apply the common set of tags for multiple constructs:

import { applyTags, SecurityClassification, TagsBase } from '@linzjs/cdk-tags';

const commonTags: TagsBase = {
  application: 'basemaps',
  environment: 'prod',
  group: 'li',
  classification: SecurityClassification.Unclassified,
  data: { isMaster: true, isPublic: true, role: 'archive' },
  impact: 'moderate',
};

const bucket1 = new Bucket(this, 'ImageryArchive');
const bucket2 = new Bucket(this, 'AnotherImageryArchive');

applyTags(bucket1, commonTags);
applyTags(bucket2, commonTags);

Responder teams are used to route alerts to the correct team in OpsGenie. The responder team name must match the team name in OpsGenie. Only prod ops team members can create, rename or remove responder teams in OpsGenie.

Contact the prod ops team in slack at #team-step-prod-ops to create a new team in OpsGenie. Once this team is created, add a new responder team to src/responder-teams.ts file with the new team name. These two names must match to ensure New Relic alerts are sent to the correct team.

Warning Consult the prodOps team regarding renaming a responder team. It is strongly recommended to never rename responder team names as this results in the teams having to apply the new responderTeam value to all their cdk stacks. When renaming a responder team, contact the prod ops team in slack at #team-step-prod-ops once the name as been updated, update src/responder-teams.ts to match the new name. And ensure you update the responderTeam in your applyTags() function across all stack the team owns.

When removing a responder team, contact the prod ops team in slack at #team-step-prod-ops once the team has been removed, remove the team from src/responder-teams.ts file. And ensure you remove the responderTeam from your applyTags() function.