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
To-be:
The overall goal is to find an elegant way to provide test/prod environments to the PaimonGanyu's architecture.
Have two different AWS accounts per test/prod environment.
The Mappings area isn't currently in use. Review and find some points that mapping data can replace.
Consider using Lambda alias to provide test/prod environments for the workflows in the paimonganyu stack. Two siloed accounts will separate the environments.
The text was updated successfully, but these errors were encountered:
I acquired a new domain name for PaimonGanyu: paimon.studio. Its name was considered for future business.
New AWS Account for Test Environment
PaimonGanyu is manged by two AWS accounts per environment(test/prod).
Test environment manger - paimonganyu-test:pgtest
Production environment manager - jbinchoo-aws:pgprod
Third-Level Domain for Test Environment in the New Account
The new account paimonganyu-test created a Route 53 Hosted Zone - test.paimon.studio. It manages DNS records for instances in the test environment.
To resolve (*.)test.paimon.studio domain names, jbinchoo-aws created an NS record within its paimon.studio hosted zone, which will propagate DNS requests to the name servers that paimonganyu-test account has.
Mappings and Conditions with CFN templates
Parameters:
Env:
Type: StringDefault: testAllowedValues:
- test
- prodDescription: The enviroment type of this deployment.UseALB:
Type: StringDefault: 'False'AllowedValues:
- 'True'
- 'False'Description: Whether to create an ALB. If Env=prod, an ALB is always created.Conditions:
CreateProd: !Equals [!Ref Env, prod]CreateALB: !Or [Condition: CreateProd, !Equals [!Ref UseALB, 'True']]Mappings:
EnvMap:
HostedZone:
prod: paimon.studio.test: test.paimon.studio.ApiDomain:
prod: skill.paimon.studiotest: skill.test.paimon.studioRegionEnvMap:
ap-northeast-2:
prod: SeoulProdtest: SeoulTestap-northeast-1:
prod: TokyoProdtest: TokyoTestCACert:
SeoulProd: arn:aws:acm:ap-northeast-2:305992497901:certificate/9023abac-1279-4647-8056-ec5be058af4cSeoulTest: arn:aws:acm:ap-northeast-2:254804608366:certificate/3ee23337-94cb-47ba-9ce4-b91c0b71ac1bTokyoProd: arn:aws:acm:ap-northeast-1:305992497901:certificate/eb2ba354-e8c3-49ec-836d-5003be9c0da7
CFN Template Locations
CFN templates for paimonganyu and paimonganyu-skill stacks exist inside their own gradle project's root directory.
Gradle Tasks Cares SAM Build & Deploy
Gradle tasks take responsibility to execute sam build & deploy CLI commands.
To-be:
The overall goal is to find an elegant way to provide test/prod environments to the PaimonGanyu's architecture.
Consider using Lambda alias to provide test/prod environments for the workflows in theTwo siloed accounts will separate the environments.paimonganyu
stack.The text was updated successfully, but these errors were encountered: