Ayyappu MK

Install nvm using the commands below: curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.34.0/install.sh | bash source ~/.nvm/nvm.sh Usage: nvm install <version>       Download and install a <version> nvm use <version>           Modify PATH to use <version> nvm ls                      List versions nvm ls-remote               To list available versions

Run the following commands in the console from inside the EC2 instance: curl http://169.254.169.254/latest/meta-data/public-ipv4 curl http://169.254.169.254/latest/meta-data/local-ipv4

The Secrets Manager can rotate the secrets using a Lambda function. It can't do that on its own. You can create the secret-rotating Lambda function from console. If you're configuring the secret rotation via CLI or Terraform etc., a Lambda function like this can be used.

Try to find answers for the questions below: 1. Is secret rotation needed? 2. Is cross-account secret sharing required? If any one/both of them are 'yes', choose Secrets Manager to store the secrets. Else, Systems Manager Parameter Store.

I created a private subnet. I created an ECR repo with Private visibility and pushed an image into it. Then, I created an ECS Cluster. I added a Task Definition with No Task Role and a Task Execution Role (ecs-tasks.amazonaws.com can assuem this role), with AmazonECSTaskExecutionRolePolicy permission policy. The container in the task definition has private repository authentication enabled. Then, I created a task as follows: aws ecs run-task --task-definition <task-definition-name> --cluster <ecs-cluster-name> --network-configuration '{"awsvpcConfiguration": {"subnets":["<subnet-id>"], "securityGroups": ["<sg-id>"], "assignPublicIp": "DISABLED" }}' --count 1 --launch-type FARGATE The task did not start and stopped with the following error: ERROR: ResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to retrieve ecr registry au...