-
Notifications
You must be signed in to change notification settings - Fork 0
/
contentspec.yaml
74 lines (60 loc) · 2.52 KB
/
contentspec.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
version: 2.0
defaultLocaleCode: en-US
localeCodes:
- en-US
awsAccountConfig:
accountSources:
- WorkshopStudio
regionConfiguration:
deployableRegions:
required:
- ap-northeast-1
minAccessibleRegions: 1
maxAccessibleRegions: 3
accessibleRegions:
required:
- ap-northeast-1
- us-east-1
- us-west-1
serviceLinkedRoles:
- appsync.amazonaws.com
participantRole:
managedPolicies:
- "arn:aws:iam::aws:policy/IAMReadOnlyAccess"
- "arn:aws:iam::aws:policy/ReadOnlyAccess"
- "arn:aws:iam::aws:policy/AmazonOpenSearchServiceFullAccess"
- "arn:aws:iam::aws:policy/AWSLambda_FullAccess"
- "arn:aws:iam::aws:policy/AmazonS3FullAccess"
- "arn:aws:iam::aws:policy/AWSCloud9User"
- "arn:aws:iam::aws:policy/AmazonEventBridgeFullAccess"
#s3 bucket, Cloud9, Lambda, OpenSearch?? IAM
iamPolicies:
- static/iam_policy.json
trustedPrincipals:
# List of AWS service principals
service:
- ec2.amazonaws.com
- lambda.amazonaws.com
ec2KeyPair: false
infrastructure:
# A list of CloudFormation templates that are present in the content's repository.
# These CloudFormation templates will be used by Workshop Studio's provisioning process and will be deployed to AWS accounts.
# Note: The order of CloudFormation templates defined here will be the same order that Workshop Studio will deploy them to
# the AWS accounts. Make sure the CloudFormation templates are in the correct order if some depend on others.
cloudformationTemplates:
# The template's location relative to the root of the content's repo.
# Note: Templates must be located in the `static/` directory
- templateLocation: static/aws-solace-workshop.yaml
# Friendly name for the corresponding cloudformation template.
label: EC2 Stack
# [OPTIONAL] List of parameters defined within the corresponding stack alongside
# the value that should be used for them. Any CloudFormation parameter that does not
# have a default value should be defined here with a default value.
parameters:
# Workshop Studio supports "Magic Variables" in the `defaultValue` of CloudFormation Template parameters
- templateParameter: ParticipantRoleArn
defaultValue: "{{.ParticipantRoleArn}}"
- templateParameter: AssetsBucketName
defaultValue: "{{.AssetsBucketName}}"
- templateParameter: AssetsBucketPrefix
defaultValue: "{{.AssetsBucketPrefix}}"