Account Contacts

Every Campus Cloud account has contacts that receive critical notifications — security findings, billing alerts, and service health events. Setting these correctly is one of the first things you should do after account creation.

Use Functional Email Addresses

Use functional email addresses

Avoid setting contacts to a personal email address. When people change roles or leave UCSB, contacts with personal addresses stop working. Use a department or team email (e.g., mylab-cloud@ucsb.edu) that can be managed by multiple people.

Why Contacts Matter

Cloud providers send important notifications to your contacts:

Security — alerts from security monitoring tools (GuardDuty, Defender for Cloud, Security Command Center), abuse reports, and potential account compromise notifications.
Operations — service health events, scheduled maintenance, and infrastructure incidents that affect your resources.
Billing — budget threshold alerts and billing issue notifications.

Missing or stale contacts mean your team may not hear about a security incident or an unexpected billing spike in time to respond.

Provider-Specific Setup

Each provider has a different way to configure contacts. Follow the guide for your provider:

AWS First Steps — Set Account Contacts — Alternate contacts (Security, Operations, Billing) in the AWS Account Settings page. See the AWS documentation on alternate contacts for details on what each contact type receives.
Azure First Steps — Set Subscription Contacts — Defender email notifications, budget alert recipients, and Service Health alert rules. See the Azure notification settings documentation for Defender for Cloud email configuration.
GCP First Steps — Set Project Contacts — Essential Contacts for Security, Technical, and Billing notification categories. See the GCP Essential Contacts documentation for details on notification categories.

Contacting the Cloud Team

For account-level contact changes you cannot make yourself, open a ServiceNow ticket.