-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error when deploying with CDK #20
Comments
I updated those packages, and it went well. I have checked the available versions of RDS in AWS, and everything is perfect.
A couple of parameters are marked as deprecated, as an additional comment. The question I have is how can I test this in AWS (i.e. the code in production)? If you can help me how to do it. |
Hi Damianlluch! We are happy that this repository is useful to you! We're here to support you as you move forward with bringing it to production. It seems like we've hit a snag regarding the availability of Aurora PostgreSQL version 13.6. The error message you're encountering reads:
This indicates that the specified version of Aurora PostgreSQL isn't currently accessible. It's possible that this is due to your region's settings. To verify the available engines in your region, you can use the following command. Just make sure to replace "us-east-2" with your correct region:
I hope this helps clarify the situation for you. Feel free to reach out if you have any other questions or run into further issues. We're here to assist! |
Note, we are using aurora serverless v2. If this helps you, here is a configuration used by a client of ours with a database using instances (no serverless)
|
Hi, I was able to fix it by updating the dependencies. How can I test the API in AWS ? or see the Swagger itself ? Thanks |
Upon reviewing the code again, I noticed an error in the infrastructure code in the applications layer, where only the users service is being served at the root, excluding Swagger and Auth declarations. We have a production version with these issues resolved. We'll make the necessary corrections and update the boilerplate. Additionally, we'll update packages like AWS Signer to the latest AWS SDK version and address other minor details identified. ETA: I hope to bring updates tomorrow. |
Perfect, great, thank you |
Include these corrections in the refactoring for version 0.1.0, which has been completed and is under review, tomorrow we will start a review process with @lhgrigio @junior-anzolin |
We have released v0.1.0, containing the fix for this issue. |
Perfect, I'll try it and let you know. |
Hi! fail with cdk synth
|
First I ran |
My bad Damian, I didn't add the rds certificate file, in a few minutes @junior-anzolin will fix. |
The change is already on repository, @douglasgc can you please review the Pull Request #22? |
Thank you @junior-anzolin. merged. |
Same error
with On local, it seems that I had no problems, at least NestJS starts fine. |
cp: cannot stat ‘/asset-input/src/common/config/certs/rds-ca-2019-root.pem’: No such file or directory I looked for this expression in the code and couldn't find it. Are you sure you pull the master and run:
|
We don't have documentation on this yet. However, in the infrastructure section, we don't use the .env file; it's only for the application environment (backend). In the infrastructure section, environment variables are defined in the code. This was our initial decision, and while we're considering improvements for future versions, it currently serves its purpose well. Therefore, you need to update the following files with your account information: infra/index.ts In the file '/infra/constructs/lambda-nestjs-function/constants.ts', we have the backend environment settings running on the lambda server. You should also update this file. However, please note that the database settings are already configured automatically; you don't need to add them. |
I have just seen the files, and they are parameters that are a bit confusing, I think the best (opinion) is that they take out as much as possible, because if not, you have to go investigating where each parameter goes, what it is for, there are too many. |
We agree with you, and it is also very important to explain each of the parameters and improve our documentation. In addition to improving the organization and where these settings. We also recorded a video here explaining the repository and how to deploy it, but we will still review and edit it for posting. |
The project, if they simplify it as much as possible, looks very good. I have tried several options and it is the best. It can have a good reach |
Let me know when you have something? I'm interested for a project I'm starting, and I've already done something with CDK. But your project is very good for me to have a base. |
What should I fill in here besides the AWS account and the zone? Where do I get the other parameters from?
|
And what should I change in this file? Thanks!
|
Hello @damianlluch, we are very happy with your feedback and how it can be useful for you. It has been very useful for our projects here at Atlas. Our vision is that in fact this repository must still be polished, in order to allow the user to select what they want to use and configure through a CLI, and also to advance in the simplification and complete documentation of it (of all decisions and details) . We are also thinking about creating a discord or something like that to facilitate communication and debugging for our community and we are also thinking about creating a consultancy model for our sponsors. |
To start this repository on AWS, you need to have a Hosted Zone on Route53 on AWS, this is important because we generate all the necessary certificates and publish the records on the domain, as well as link all the APIs in a subdomain.domain.com.
|
You just need to worry about this part: export const DEFAULT_NESTJS_LAMBDA_ENVIRONMENT = {
},
} Most of these variables are from the NestJS standard itself. You can deploy without changing anything, just the SESSIONS_TABLE_NAME field, it must always be in the format {applicationName}-{environment (development or production)}-sessions please ignore or remove the Change the BACKEND_DOMAIN to the same as your apiDomainName, 'api.' + $domainname The rest you can only update if you want, but we recommend that you update APP_NAME and AUTH_JWT_SECRET. |
Sure, it's a bit confusing to me. Why do you have to play Route53 in this instance? I've deployed other projects with CDK, and that's something I do after the fact. |
I get the backend URL when I deploy the API Gateway. Why is it necessary in configuration a value that is obtained when deploying the API Gateway? |
I understand the decision to make route53 records later manually, after all some projects don't have a domain initially, but I really see a lot of value in creating SSL certificates for https as part of this repository, it really makes things a lot easier. (and in the future the user will be able to select whether or not) |
This can really be improved, and also SESSIONS_TABLE_NAME. I'll work on it. |
Hi guys, I was trying to test with your project and I am getting this error.
The text was updated successfully, but these errors were encountered: