-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploying CFT in Tel Aviv (il-central-1) fails #53
Comments
Hi @mikeoleary, I created issue EC-526 for this, but cannot start work on it yet because our account also needs access to that region (it's been requested). That said, for the first error you should have been able to get around it by providing an AMI for the bigIpCustomImageId parameter since looking up the AMI by name is the only thing GetLayerVersion is used for. The second error is from runtime init. The validator for the secret ARN doesn't include any il regions and the one for simple secret name doesn't support uppercase. There are two options to work around this until we can fix:
|
@mikeshimkus, big thank you as always. I have asked customer to try this and also to subscribe to this issue. |
bigIpCustomImageId: we used these AMIs--ami-084b3f263e7cff637 / ami-0e38f7892a301a8ca Leave the secret ID parameter empty so that the template creates a new secret with a random value: yes we tried in call @mikeoleary Then use that non-ARN value for the bigIpSecretArn input. : need assistance here |
@shiv-dasari The options are either leave the secret ID empty or use non-ARN value for bigIpSecretArn (the latter assumes you have already created the secret). We are going to release an update to F5 BIG-IP Runtime Init that should fix the issue with using the existing secret. I will post here when it's available. |
Hi @shiv-dasari, for the secret ARN issue, please try updating the bigIpRuntimeInitPackageUrl parameter to https://cdn.f5.com/product/cloudsolutions/f5-bigip-runtime-init/v2.0.3/dist/f5-bigip-runtime-init-2.0.3-1.gz.run and then redeploy. |
@mikeshimkus ---we are seeing this error- |
We don not have visibility/access to this account |
For the GetLayerVersion error, you will either need to use the AMI ID for bigIpCustomImageId, or grant the required permissions to arn:aws:lambda:il-central-1:770693421928:layer:Klayers-p312-requests:3 in your IAM policy (the latter is only required when using the AMI lookup function, which should be bypassed if you provide bigIpCustomImageId. |
@mikeshimkus --Thank you { AdministratorAccess | AWS managed - job function I think it should be allowed on 770693421928: this account. |
@mikeshimkus and @mikeoleary -- We were using this Image ID- in our last / even I checked again same error. |
@shiv-dasari Looks like your IAM policy needs to allow lambda:GetLayerVersion Example:
|
@mikeoleary --Need your assistance, can we connect on Monday. Please let me know. |
@shiv-dasari - ok will email you. |
@mikeshimkusWe were able to add the Function stack to our S3 and run it, but we are still encountering this issue with the last stack (VM the building phase). 2024-07-16 20:03:18 UTC+0530 | ill-f5-stack-BigIpInstance02-1KORPCAEL3P6Q | CREATE_FAILED | The following resource(s) failed to create: [Bigip3NicInstance]. -- | -- | -- | -- 2024-07-16 20:03:18 UTC+0530 | Bigip3NicInstance | CREATE_FAILED | Failed to receive 1 resource signal(s) within the specified duration |
AWSTemplateFormatVersion: '2010-09-09' |
I am using this parent stack in AWS Israel region And I added Function stack template into our S3 , then after we were able to ran with out any issue but still failing. |
@shiv-dasari Do you have ssh access to the BIG-IP(s)? If yes can you share the content of /var/log/cloud/startup-script.log? |
@mikeoleary --I have sent the requested below logs over email. /var/log/cloud/bigipruntimeinit.log /config/cloud/runtime-init.conf |
@mikeshimkus , please find for the /var/log/cloud/startup-script.log Uploading putty.log… |
Describe the bug
It appears that we cannot deploy the CFT in region il-central-1. Can we get support for this?
Expected behavior
CFT to deploy new stack will work.
Current behavior
Customer cannot deploy into Tel Aviv region (il-central-1). He gets the following error when trying the template for a Failover pair into a NEW VPC:
Resource handler returned message: "User: arn:aws:sts::xxxxxxxxxxxx:assumed-role/xxx/[email protected] is not authorized to perform: lambda:GetLayerVersion on resource: arn:aws:lambda:il-central-1:xxxxxxxxxxxx:layer:Klayers-p312-requests:3 because no resource-based policy allows the lambda:GetLayerVersion action (Service: Lambda, Status Code: 403, Request ID: xxx)" (RequestToken: xxx, HandlerErrorCode: AccessDenied)
Customer says he was able to get around this by creating a bucket specifically for himself and copying our templates into it. However, after that, he got a new error:
2024-07-01T12:08:56.958Z [9032]: error: AWS Cloud Client secret id arn:aws:secretsmanager:il-central-1:xxxxxxxxx:secret:xxxxxf5-bigIpSecret-xxxxxx is the wrong format
However, we double-checked this secret and it is in the correct format. (Secret itself is a string of letters and numbers without illegal special characters. IAM role allows permissions to secret).
Steps to reproduce
Deploy CFT into il-central-1
Note I cannot test in this region (il-central-f5) with my F5 account. I am unable to replicate customer's problem because of this.
The text was updated successfully, but these errors were encountered: