1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
You would need to add the accessPointId
field within the efsVolumeConfiguration
object.
{
"name": "tmp-files",
"efsVolumeConfiguration": {
"fileSystemId": "fs-0de0326ae8f3dd0b6",
"transitEncryption": "ENABLED",
"authorizationConfig": {
"iam": "ENABLED"
},
"accessPointId": "your-access-point-id-here"
}
}
Regarding your side question about a complete taskdef.json
reference guide, AWS provides detailed documentation on the taskDefinition
JSON structure in the official documentation. Please check out this link: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/example_task_definitions.html
respondido hace un mes
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
The documentation is not a reference, only a list of examples.
anyway, My problem is I have NOT a static accessPointId, becausae it's create at 'runtime' from cloud formation before cloud pipeline is started.
So here I need to NOT hardcode an accessPointId.
This problem rises becase file systems has not guid/uid , but AccessPoint has them. So we need an accessPoint to access a custom path on file system and then mount on a running ECS using right permissions and ownership