Channels
#aws
Title
# aws
p
polite-napkin-90098
05/06/2022, 9:04 PMI'm getting an error when trying to make an Access Point for an EFS drive.
The error is
Copy code
aws-native:efs:AccessPoint (TestinfluxAP):
error: operation CREATE failed with "InvalidRequest": Invalid request Copy code
const accessPoint = new awsnative.efs.AccessPoint(`${nam}influxAP`, {
fileSystemId: efs.id,
rootDirectory: {
path: "influx",
creationInfo: {
ownerGid: "0",
ownerUid: "0",
permissions: "700",
},
},
}); Copy code
const efs = new awsnative.efs.FileSystem(`${nam}-influx-pvc`, {
encrypted: true,
fileSystemTags: [
{
key: "Name",
value: `${nam}-influx-pvc`,
},
],
});w
witty-candle-66007
05/09/2022, 4:36 PMUnless there’s a specific reason to use the aws-native provider, I would be inclined to use the aws-classic provider (https://www.pulumi.com/registry/packages/aws/api-docs/efs/) since aws-native is in preview at this time and so you may be hitting a bug.
If there is a reason to stick with aws-native, try
creating the access point without the
creationInfo Copy code
fileSystemId: efs.id.apply(id => id),p
polite-napkin-90098
05/09/2022, 4:38 PMI discovered my bug. The path: needs to start with a slash e.g.
/influxinfluxI am using both the classic and native providers. Maybe I should switch to all classic until native is 1.x but I feel like native is the future and thus have been using it where it seems to work well. I created the underlying EFS drive with native so making the AP that way seem to make sense.
w
witty-candle-66007
05/09/2022, 4:42 PMI was mostly making sure you were aware of the classic provider just in case it helped. And in this case it looks like it was a typo and not a bug in the provider. So, it definitely makes sense to keep with the native provider.
👍 1
3 Views