[ad_1]
Should you’re operating a Fargate job and it’s not capable of learn secrets and techniques from AWS Secret Supervisor, there are some things you’ll be able to verify:
-
Confirm that the Fargate job has the proper IAM permissions to entry the key. You want to grant the duty the secretsmanager:GetSecretValue permission for the precise secret that it must entry. You are able to do this by including the mandatory permission to the duty execution position, or by making a separate IAM position and attaching it to the duty.
-
Verify that the key title and ARN are appropriate. You may 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 job. Secrets and techniques are regional sources and may solely be accessed from throughout the similar area.
-
Verify the VPC configuration of your Fargate job. In case your job is operating in a VPC with a personal subnet, you could have to configure VPC endpoints for Secrets and techniques Supervisor to permit the duty to entry the service.
-
Verify the community configuration of your Fargate job. In case your job is operating in a personal subnet and must entry the web to achieve the Secrets and techniques Supervisor service, you could have to configure NAT gateways or proxies.
-
Confirm that the setting variables or container definitions in your job definition are arrange accurately. Be sure that the key is referenced utilizing the proper syntax, similar to
${secretsmanager:my-secret:secret-string:password}.
If none of those steps assist to resolve the difficulty, you could have to allow extra logging and debugging to establish the basis reason for the issue.
[ad_2]
