Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUGFIX deploy scripts don't work : Updates for README.md, devteam2-frame/template.yaml #9

Open
murffious opened this issue Sep 24, 2023 · 0 comments

Comments

@murffious
Copy link

  • REPRO
    ISSUE - Follow the README.md exactly and it won't for various reasons
    modifications to make in order to make it work:
    a. line 86 step "6. Docker Install" also make sure to start the docker daemon, needed for phase 2
    b. OPTIONAL: line 93 step 7 Bootstrap - for ease of use change region to your preferred region
    for ex: change all the region references starting with devteam2-frame/config/shared.ts, there are about 15 references update
    all at the same time for ease in find and replace to match your default AWS profile
    c. RDS Service Role Policy (aws managed) created manually - without this it won't work - ** line 175 approx. has an item 9. about configuring services. ... yada yada BUT it could be spelled out here since this is what maybe it refers to
    - AmazonRDSServiceRolePolicy
    SEE - https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAM.ServiceLinkedRoles.html
    - https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonRDSServiceRolePolicy.html
    - https://stackoverflow.com/questions/52079383/awsrdsdbinstance-is-not-being-created-from-cloudformation
    - I added this permission to my user but maybe just the ServiceRolePolicy{ "Version": "2012-10-17", "Statement": [ { "Action": "iam:CreateServiceLinkedRole", "Effect": "Allow", "Resource": "arn:aws:iam::*:role/aws-service-role/rds.amazonaws.com/AWSServiceRoleForRDS", "Condition": { "StringLike": { "iam:AWSServiceName": "rds.amazonaws.com" } } } ] }
    d. In phase 2 - see devteam2-frame/template.yaml there are some issues with references to some other user
    - Line 542 /Users/jinstar/Desktop/workspace/demogo2/devteam2-frame/cdk.out/asset.86bd4f1d4ddd4818dee0a1da35b87e02da59bf2dbb8176e3c2550eeeb354e25e
    - it needs to reference the LOCAL user and the cdk output number for the asset who runs this code not jinstar's path though he is super.
    - so /Users/jinstar/Desktop/workspace/demogo2/
    - and the asset.86bd4f1d4ddd4818dee0a1da35b87e02da59bf2dbb8176e3c2550eeeb354e25e part should be the number you have in the cdkout after running the bootstrap or whenever its created.
    - I updated line 618 as well aws:asset:path: for the path to the custom aws-cdk-lib

NOTE: it seems there are notes in issues about NODE 18 and since it yells at your big red warning that node 16 is not supported much though it does still work see aws/aws-cdk#23682

code version - main branch updated 4 months ago from what github said as of this issue creation Sep 23 2023
SETUP/ENV:
OS: Apple M1 Pro, 13.0.1 (22A400)
VScode latest
nvm to manage/load node 16.16 [node v16.16.0 (npm v8.11.0)]
cdk --version 2.97.0 (build d7cf3be)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant