You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resource should allow settings the SupportLevel for an Account within the organization through a support ticket.
This because it is currently not possible to automate this process. org-formation, but also ADF use this mechanism to automate setting support level on new member-accounts.
Type: Community::Support::SupportLevelProperties:
SupportLevel: 'developer'| 'business' | 'enterprise'AccountId: String # \d{12}CCEmailAddresses: List<String> # list of emailaddresses need to be included on the support case.
Type must be deployed to master account, where the support case will be created as follows:
The Support API is only supported on AWS Accounts that have business or enterprise support enabled. Resource will expect to fail if the support level is less.
constcreateCaseRequest: CreateCaseRequest={subject: `Enable ${resource.supportLevel} Support for account: ${accountId}`,communicationBody: `Hi AWS,Please enable ${resource.supportLevel} on account ${accountId}.This case was created automatically - please resolve when done.Thank you! `,serviceCode: 'customer-account',categoryCode: 'other-account-issues',severityCode: 'low',issueType: 'customer-service',ccEmailAddresses: [resource.rootEmail],};
Resource should allow settings the SupportLevel for an Account within the organization through a support ticket.
This because it is currently not possible to automate this process. org-formation, but also ADF use this mechanism to automate setting support level on new member-accounts.
Type must be deployed to master account, where the support case will be created as follows:
The Support API is only supported on AWS Accounts that have business or enterprise support enabled. Resource will expect to fail if the support level is less.
Intended use using org-formation syntax:
The text was updated successfully, but these errors were encountered: