|
Jul
16 |
|
asked | how to access amazon secret manager from nginx.conf for react.js google search indexing |
|
Jul
16 |
|
comment |
Backend JavaScript file EmailJS send error nevermind this was the right path to fix. thanks |
|
Jul
16 |
|
accepted | Backend JavaScript file EmailJS send error |
|
Jul
16 |
|
comment |
Backend JavaScript file EmailJS send error Editing my code to use const SMTPClient = await import("emailjs"); inside the route, but still resulting in an error message send email err: TypeError: SMTPClient is not a constructor
|
|
Jul
15 |
|
asked | Backend JavaScript file EmailJS send error |
|
Jul
7 |
|
awarded | Notable Question |
|
Jul
7 |
|
accepted | How to use AWS Secret Manger in JavaScript file hosted on ECS container |
|
Jul
7 |
|
asked | How to view Docker /var/log files in AWS? |
|
Jul
6 |
|
comment |
How to use AWS Secret Manger in JavaScript file hosted on ECS container I checked and added the SecretReadWrite permission to my IAM role, but am still getting the error Error getting aws secret: CredentialsProviderError: Could not load credentials from any providers I updated my question with images for all the aws groups / proof
|
|
Jul
6 |
|
revised |
How to use AWS Secret Manger in JavaScript file hosted on ECS container added 263 characters in body |
|
Jul
6 |
|
revised |
How to use AWS Secret Manger in JavaScript file hosted on ECS container added 408 characters in body; edited title |
|
Jul
6 |
|
comment |
How to use AWS Secret Manger in JavaScript file hosted on ECS container I've added an S3 read only ami role to my container service, but am still getting the same error. |
|
Jul
6 |
|
comment |
How to use AWS Secret Manger in JavaScript file hosted on ECS container I see, my code gets hosted in an ec2 container so i need to find out how to sign in / authenticate in javascript from inside my container |
|
Jul
5 |
|
asked | How to use AWS Secret Manger in JavaScript file hosted on ECS container |
|
Jul
5 |
|
comment |
node server not accessible in docker container on aws It works! Thanks, In total I had to debug and make sure the node server was running first, than I could debug the ports, and finally adjust this slash so the routing works too |
|
Jul
5 |
|
accepted | node server not accessible in docker container on aws |
|
Jul
3 |
|
revised |
node server not accessible in docker container on aws added 1279 characters in body; edited title |
|
Jul
3 |
|
comment |
node server not accessible in docker container on aws re-wrote my question again, now ive gotten this working when building and running the docker image / container locally, but still not yet working when pushed to aws. |
|
Jul
3 |
|
revised |
node server not accessible in docker container on aws added 1279 characters in body; edited title |
|
Jul
3 |
|
revised |
node server not accessible in docker container on aws added 1114 characters in body |