aws-bluage-l3-workshop-efs-bk error while connecting EC2

The error you're encountering while trying to connect your EC2 instance to the Elastic File System (EFS) in the AWS BluAge L3 workshop could be related to IAM roles and instance profiles. Here are a few steps you can try to resolve this issue:

1. Verify that you have correctly created the IAM role "aws-bluage-l3-workshop-efs-role" as specified in the workshop instructions.

2. Ensure that the IAM instance profile is properly associated with your EC2 instance. Sometimes, there can be a glitch where the IAM instance profile doesn't get created automatically when you create an IAM role through the console.

3. If the IAM instance profile doesn't appear in the dropdown when creating or modifying your EC2 instance, you may need to create it manually using the AWS CLI. You can do this with the following commands:

   aws iam create-instance-profile --instance-profile-name aws-bluage-l3-workshop-efs-role aws iam add-role-to-instance-profile --role-name aws-bluage-l3-workshop-efs-role --instance-profile-name aws-bluage-l3-workshop-efs-role

4. After creating the instance profile, make sure to attach it to your EC2 instance.

5. If you've made any changes, you may need to restart your EC2 instance for the new permissions to take effect.

6. Double-check that your security groups and network ACLs allow the necessary traffic between your EC2 instance and the EFS.

If the issue persists after trying these steps, you may need to review the workshop documentation for any specific instructions related to EFS setup, or reach out to the workshop support for further assistance.
Sources
Blu Age L3 - IAM instance profile doesn't appear while creating EC2 | AWS re:Post