handle_update_notification pulls account_id from CID instead of AccountId

[bsweeney-gingerio]

mdr_control_tower_automation/src/register/ct_al_register.py

Lines 244 to 250 in d043f38

	account_id = sns_event['ResourceProperties']['CID']
	deployments_client = al_session.client('deployments')
	deployment = get_deployment(
	deployments_client,
	auth['ALCID'],
	account_id
	)

In the code above, account_id = sns_event['ResourceProperties']['CID'] causes the get_deployment function to check the deployment status of the Alert Logic customer ID, rather than the status of the target AWS account ID, which is found in sns_event['ResourceProperties']['AccountId']. This means that the check will always return None, indicating that there is no deployment in the account, which could result in double-deployment if the register Lambda function is ever run more than once on the same target account.

-        account_id = sns_event['ResourceProperties']['CID']
+        account_id = sns_event['ResourceProperties']['AccountId']