clients/client-route53profiles/README.md
AWS SDK for JavaScript Route53Profiles Client for Node.js, Browser and React Native.
<p> With Amazon Route 53 Profiles you can share Route 53 configurations with VPCs and AWS accounts </p>To install this package, use the CLI of your favorite package manager:
npm install @aws-sdk/client-route53profilesyarn add @aws-sdk/client-route53profilespnpm add @aws-sdk/client-route53profilesThe AWS SDK is modulized by clients and commands.
To send a request, you only need to import the Route53ProfilesClient and
the commands you need, for example ListProfilesCommand:
// ES5 example
const { Route53ProfilesClient, ListProfilesCommand } = require("@aws-sdk/client-route53profiles");
// ES6+ example
import { Route53ProfilesClient, ListProfilesCommand } from "@aws-sdk/client-route53profiles";
To send a request:
send operation on the client, providing the command object as input.const client = new Route53ProfilesClient({ region: "REGION" });
const params = { /** input parameters */ };
const command = new ListProfilesCommand(params);
We recommend using the await operator to wait for the promise returned by send operation as follows:
// async/await.
try {
const data = await client.send(command);
// process data.
} catch (error) {
// error handling.
} finally {
// finally.
}
You can also use Promise chaining.
client
.send(command)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
})
.finally(() => {
// finally.
});
The aggregated client class is exported from the same package, but without the "Client" suffix.
Route53Profiles extends Route53ProfilesClient and additionally supports all operations, waiters, and paginators as methods.
This style may be familiar to you from the AWS SDK for JavaScript v2.
If you are bundling the AWS SDK, we recommend using only the bare-bones client (Route53ProfilesClient).
More details are in the blog post on
modular packages in AWS SDK for JavaScript.
import { Route53Profiles } from "@aws-sdk/client-route53profiles";
const client = new Route53Profiles({ region: "REGION" });
// async/await.
try {
const data = await client.listProfiles(params);
// process data.
} catch (error) {
// error handling.
}
// Promises.
client
.listProfiles(params)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
});
// callbacks (not recommended).
client.listProfiles(params, (err, data) => {
// process err and data.
});
When the service returns an exception, the error will include the exception information, as well as response metadata (e.g. request id).
try {
const data = await client.send(command);
// process data.
} catch (error) {
const { requestId, cfId, extendedRequestId } = error.$metadata;
console.log({ requestId, cfId, extendedRequestId });
/**
* The keys within exceptions are also parsed.
* You can access them by specifying exception names:
* if (error.name === 'SomeServiceException') {
* const value = error.specialKeyInException;
* }
*/
}
See also docs/ERROR_HANDLING.
Please use these community resources for getting help. We use GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.
aws-sdk-js
on AWS Developer Blog.aws-sdk-js.To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.
This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-route53profiles package is updated.
To contribute to client you can check our generate clients scripts.
This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.
Command API Reference / Input / Output
</details> <details> <summary> AssociateResourceToProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> CreateProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> DeleteProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> DisassociateProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> DisassociateResourceFromProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> GetProfile </summary>Command API Reference / Input / Output
</details> <details> <summary> GetProfileAssociation </summary>Command API Reference / Input / Output
</details> <details> <summary> GetProfileResourceAssociation </summary>Command API Reference / Input / Output
</details> <details> <summary> ListProfileAssociations </summary>Command API Reference / Input / Output
</details> <details> <summary> ListProfileResourceAssociations </summary>Command API Reference / Input / Output
</details> <details> <summary> ListProfiles </summary>Command API Reference / Input / Output
</details> <details> <summary> ListTagsForResource </summary>Command API Reference / Input / Output
</details> <details> <summary> TagResource </summary>Command API Reference / Input / Output
</details> <details> <summary> UntagResource </summary> </details> <details> <summary> UpdateProfileResourceAssociation </summary> </details>