- 最新
- 投票最多
- 评论最多
The bluesam database connection is provided into application definition using AWS Secret Manager.
Instructions page: https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/go-live/prepare/local
Create carddemo-application.json from template provided below
- Replace [bucket name] by your bucket name (somthing like aws-bluage-l3-workshop-bucket)
- Replace [arn bluesam rds db] by aws-bluage-l3-workshop-carddemo-bluesam secret ARN
- Replace [redis endpoint] by aws-bluage-l3-workshop-redis endpoint
Solution page: https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/solution/go-live/prepare/local
Pay attention to the warning message in case you followed the video solution
Database ARN copied into application definition is wrong The video shows that primary database ARN is copied to application definition file instead of bluesam database ARN.
Hello,
To help you get your CardDemo app up and running on M2, I have included a link below to our documentation. This guide contains detailed steps for configuring your app effectively:
[+] https://docs.aws.amazon.com/m2/latest/userguide/reply-compare-walkthrough.html
Feel free to refer to this documentation for all the information you need.
Thank you.
This is the instruction to set up the Cardemo app in anEC2 instance.
For the workshop, we have to use the M2 Environment.
M2 Environment by default supports M2 type instances,
I did ererything like the video now and the log shows the same error: BLUESAM is disabled: Don't use connect when bluesam is disabled
What can I do now?
You probably have a application definition configuration issue on bluesam database.
To configure bluesam database for Mainframe Modernization deployment, you need to
- Add a PrivateLink to your VPC for Secrets Manager service
- Create a secret for bluesam database:
- Get the secret ARN and copy it into the application definition
- Create an application on Mainframe Modernization service using the application definition
If all previous steps are correctly done, when the server starts, you have the some Bluesam log messages in the log from cloud watch (between Launching Script Control Tower... and Expected "runners" to be set)
Please provide more information about the context: Is it a local deployment, Mainframe Modernization deployment, Blu Age on EC2 deployment, Blu Age on Fargate deployment, etc. ? What is your bluesam configuration from YML files, application definition file, etc ?