- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
It looks like you may be having issues with missing credentials. If you have your access key and secret access key you can import them temporarily using the following command below and replacing the example values with your respect values that correspond to your account:
$ export AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
$ export AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
$ export AWS_DEFAULT_REGION=us-west-2
Setting the environment variable changes the value used until the end of your shell session, or until you set the variable to a different value. You can make the variables persistent across future sessions by setting them in your shell's startup script.
You can also permanently configure your accounts credentials so it can help you avoid credential issues in the future by running the aws config command in the doc listed below:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html
- First verify if EC2 instance where you are mounting EFS have permission to access EFS. If you have role attached to EC2, attach permission to that role. Otherwise create new role with permission and attached role to EC2 instance.
- make sure Security group of EFS allows access to EC2 Security group.
- If above two requirement are there, follow : https://docs.aws.amazon.com/efs/latest/ug/wt1-test.html
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
Can you please elaborate on the first point. I do not understand what you mean by role attached to EC2 and permission attached to role. I am pretty new to AWS.