-
Notifications
You must be signed in to change notification settings - Fork 15
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
AWS sdk is not accepting parameters as mentioned in the document #814
Comments
Hi @shubham-sp444 - thanks for reaching out. In order for me to understand the issue better, can you share your code calling the operation? I wasn't able to reproduce using the code with params below. Please note that var params = {
endpointName: 'vpcEndpoint',
subnetIds: [
'subnetID',
],
workgroupName: 'testWorkGroup',
}; Looking forward to hear back, |
Hello @aBurmeseDev, the const params = { Also please note that the I've added all the permissions ( granted the permissions for all VPC in my account to access the Customer AWS account ), I can see a Thanks for the reply, let me know if more details are required. |
Hey @shubham-sp444 , Thanks for the response, as long as you are using the aws-sdk-js-v3, you have to follow the input param rules. 'resourceOwner' should not be put as a input parameter here. Could you please delete the 'resourceOwner' and try again? |
This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing. |
Hello,
I need the 'resourceOwner' property to be passed.
As the redshift belongs to another AWS account and I want an endpoint to
access the redshift cross account.
…On Mon, 2 Sept, 2024, 5:44 am github-actions[bot], ***@***.***> wrote:
This issue has not received a response in 1 week. If you still think there
is a problem, please leave a comment to avoid the issue from automatically
closing.
—
Reply to this email directly, view it on GitHub
<#814>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6VHDKSIN422VWRK7G65U3ZUOUVXAVCNFSM6AAAAABM62Q4NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRTGU2TONJVGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Appreciate your response. As previously mentioned, |
Hello,
Sorry for the wrong key value.
The parameter is "owner account"
https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_CreateEndpointAccess.html
Please check the API document , it mentions that it's a valid parameter.
The ownerAccount should be the value of the owner only, so in my case it's
required if I want to create an endpoint
…On Tue, 3 Sept, 2024, 12:59 pm John L., ***@***.***> wrote:
Appreciate your response. As previously mentioned, resourceOwner is
invalid parameter in service API. We, SDK team , don't have control over
service models and if this's something you'd like to be considered, we can
pass it along to service team on your behalf.
—
Reply to this email directly, view it on GitHub
<#814>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6VHDJYJHBQBK4ABGUHQWDZUVQNXAVCNFSM6AAAAABM62Q4NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRVG44TIMRWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Please share your complete minimal code with response logs and also note that Lambda runtime for Node 16 was deprecated on Jun 12, 2024. Upgrade your runtime and retry.
|
It's an optional field, but when I try without this field I get an error of
401 because the owner of the resource i.e. Redshift is in a different
account, but the endpoint needs to be created in my account for cross
access.
That's the reason I need to define this parameter
…On Thu, 5 Sept, 2024, 11:54 pm John L., ***@***.***> wrote:
Please share your complete minimal code with response logs and also note
that Lambda runtime for Node 16 was deprecated
<https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtimes-deprecated>
on Jun 12, 2024. Upgrade your runtime and retry.
ownerAccount is also optional, try making a call without it for
troubleshooting purpose.
—
Reply to this email directly, view it on GitHub
<#814>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6VHDJURWXIONVBEKLN3A3ZVCOVLAVCNFSM6AAAAABM62Q4NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSGM3TQMJUGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Can you share your minimal code and response output so that we can further help and investigate? The output with |
Hello,
The error with ownerAccount is Unexpected key 'ownerAccount' found in
params.
The API I'm using mentions that one can pass this property:
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/RedshiftServerless.html#createEndpointAccess-property
I needed to enable private access, but the owner account is different
account so I need to pass this parameter, otherwise it picks up my account
by default if not passed.
Below is the link you can follow regarding the setup, but to create
endpoint via API is not possible due to API validation issues.
https://aws.amazon.com/blogs/big-data/enable-private-access-to-amazon-redshift-from-your-client-applications-in-another-vpc/
…On Fri, 6 Sept, 2024, 11:05 am John L., ***@***.***> wrote:
Can you share your minimal code and response output so that we can further
help and investigate? The output with ownerAccount param and one without
it. Thanks!
—
Reply to this email directly, view it on GitHub
<#814>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH6VHDPBQK2FJEBRSNAN7ATZVE5K5AVCNFSM6AAAAABM62Q4NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZTGI3DOMBVGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Since the error comes from service API and need insights from Redshift, I'm going to reach out on your behalf and transfer this to our cross-sdk repo. We would still need your minimal repro code with both success and failed outputs. |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Describe the bug
I'm using this SDK. https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/RedshiftServerless.html#createEndpointAccess-property
to create the VPC endpoint, but i get an error saying
Unexpected key 'ownerAccount' found in params
, this is not working locally as well as calling from the lambda.I've checked with the types and the property
ownerAccount
is not mentioned in the types as well.I've used node 14 and 16 both , and currently running on MacOS Ventura 13.4 with Apple M1 Pro chip ( for local ).
Please have a look and help me with this issue. thanks
Expected Behavior
It should accept the property as mentioned in the AWS document.
Current Behavior
Reproduction Steps
Try to create an endpoint for the redshift serverless cluster using this SDK: https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/RedshiftServerless.html#createEndpointAccess-property
Possible Solution
No response
Additional Information/Context
No response
SDK version used
v2 sdk version
Environment details (OS name and version, etc.)
I've used node 14 and 16 both , and currently running on MacOS Ventura 13.4 with Apple M1 Pro chip ( for local ).
The text was updated successfully, but these errors were encountered: