Working with Amazon S3 on Outposts endpoints
To route requests to an Amazon S3 on Outposts access point, you must create and configure an S3 on Outposts endpoint. In order to create an endpoint, you will need an active connection with your service link to your Outposts home region. Each virtual private cloud (VPC) on your Outpost can have one associated endpoint. For more information about endpoint quotas, see S3 on Outposts network requirements. You must create an endpoint to be able to access your Outposts buckets and perform object operations. For more information, see Endpoints.
After you create an endpoint, you can use the ‘Status’ field, to understand the state of the endpoint. If your Outposts is offline, it will return a CREATE_FAILED. You can check your service link connection, delete the endpoint, and retry the create operation after your connection has resumed. For a list of additional error codes, see below. For more information, see Endpoints.
| API | Status | Failed Reason Error Code | Message - Failed Reason |
|---|---|---|---|
CreateEndpoint |
Create_Failed |
OutpostNotReachable |
Endpoint could not be created as the service link connection to your Outposts home Region is down. Check your connection, delete the endpoint, and try again. |
CreateEndpoint |
Create_Failed |
InternalError |
Endpoint could not be created due to Internal Error. Please delete the endpoint and create again. |
DeleteEndpoint |
Delete_Failed |
OutpostNotReachable |
Endpoint could not be deleted as the service link connection to your Outposts home Region is down. Check your connection and please try again. |
DeleteEndpoint |
Delete_Failed |
InternalError |
Endpoint could not be deleted due to Internal Error. Please try again. |
For more information about working with buckets on S3 on Outposts, see Working with S3 on Outposts buckets.
The following sections describe how to create and manage endpoints for S3 on Outposts.