The user timeline is being used by AWS Tokio region using dynamicodb.
The original table has the following specifications:
There are two reasons for replication:
Detailed tasks for replication are as follows:
I have referred to the AWS document below.
http://docs.aws.amazon.com/ko_kr/amazondynamodb/latest/developerguide/Streams.CrossRegionRepl.Walkthrough.Step2.html
The problem is using cloud information
If you run elastic beanstalk and ECS automatically, create a replication group, and proceed with the copy,
After about 1 day, the ECS container will be dead.
The error code is BOOTSTAP_FAILED.
Documents related to the corresponding error code are as follows:
http://docs.aws.amazon.com/ja_jp/amazondynamodb/latest/developerguide/Streams.CrossRegionRepl.Troubleshooting.html
If this error occurs, you are asked to change the setting from cloud information to update stack and restart it, but only the same result will come out.
However, the part that is suspicious is
There is only one cluster assigned to the service of the ECS and it does not increase.
The CPU&memory setting defined in task is fixed even if the instance type created by ECS is changed.
That's about it's like this.
We tried to force these settings to change, but the results were always the same.
Currently, it is not the update stack of cloud information
The console that creates the replication group removes the group and creates it again, but I don't know if it's being processed properly.
Masters, please give us some advice.
aws dynamodb nosql
I was also curious, so I posted a question on a place called AWS Korean User Group. There was an answer like this.
I think it's in the technical document in Korean. You can find it by searching for a replication group (BOOTSTRAP_FAILED) stuck during creation. There is more detail in the Note section, and it says that the instance type should be adjusted according to the partition.
Isn't it because Seoul Region hasn't supported ECS yet?
I hope you can use it as a reference.
a self-answer Leave it for record.
It's similar to the above error, but it's separate There seems to be a bug as the template in the CloudFormation Stack is updated.
What I inquired about was that BOOTSTRAP_FAILED status appeared after about a day
BOOTSTRAP_FAILED appears as soon as it starts.
This is when the beanstalk application created by CloudFormation is activated
Send specific status values to CloudFormation where you floated
An error occurs because you do not have the privilege ListStackResources.
In this case, you can find the appropriate IAM role and grant the cloud information:ListStackResources privilege.
© 2024 OneMinuteCode. All rights reserved.