[ad_1]
In the event you’re working a Fargate process and it’s not capable of learn secrets and techniques from AWS Secret Supervisor, there are some things you may test:
-
Confirm that the Fargate process has the right IAM permissions to entry the key. You could grant the duty the secretsmanager:GetSecretValue permission for the precise secret that it must entry. You are able to do this by including the required permission to the duty execution position, or by making a separate IAM position and attaching it to the duty.
-
Test that the key title and ARN are right. You possibly can affirm this by checking the key title and ARN within the AWS Secret Supervisor console or by utilizing the AWS CLI.
-
Ensure that the key is in the identical area because the Fargate process. Secrets and techniques are regional assets and might solely be accessed from inside the similar area.
-
Test the VPC configuration of your Fargate process. In case your process is working in a VPC with a personal subnet, chances are you’ll have to configure VPC endpoints for Secrets and techniques Supervisor to permit the duty to entry the service.
-
Test the community configuration of your Fargate process. In case your process is working in a personal subnet and must entry the web to succeed in the Secrets and techniques Supervisor service, chances are you’ll have to configure NAT gateways or proxies.
-
Confirm that the setting variables or container definitions in your process definition are arrange appropriately. Make sure that the key is referenced utilizing the right syntax, resembling
${secretsmanager:my-secret:secret-string:password}.
If none of those steps assist to resolve the difficulty, chances are you’ll have to allow further logging and debugging to determine the basis explanation for the issue.
[ad_2]
