create_replication_group
¶
create_replication_group(
*,
config_overrides: Optional[ElastiCacheClientConfig] = None,
replication_group_id: Optional[String] = None,
replication_group_description: Optional[String] = None,
global_replication_group_id: Optional[String] = None,
primary_cluster_id: Optional[String] = None,
automatic_failover_enabled: Optional[BooleanOptional] = None,
multi_az_enabled: Optional[BooleanOptional] = None,
num_cache_clusters: Optional[IntegerOptional] = None,
preferred_cache_cluster_a_zs: Optional[AvailabilityZonesList] = None,
num_node_groups: Optional[IntegerOptional] = None,
replicas_per_node_group: Optional[IntegerOptional] = None,
node_group_configuration: Optional[NodeGroupConfigurationList] = None,
cache_node_type: Optional[String] = None,
engine: Optional[String] = None,
engine_version: Optional[String] = None,
cache_parameter_group_name: Optional[String] = None,
cache_subnet_group_name: Optional[String] = None,
cache_security_group_names: Optional[CacheSecurityGroupNameList] = None,
security_group_ids: Optional[SecurityGroupIdsList] = None,
tags: Optional[TagList] = None,
snapshot_arns: Optional[SnapshotArnsList] = None,
snapshot_name: Optional[String] = None,
preferred_maintenance_window: Optional[String] = None,
port: Optional[IntegerOptional] = None,
notification_topic_arn: Optional[String] = None,
auto_minor_version_upgrade: Optional[BooleanOptional] = None,
snapshot_retention_limit: Optional[IntegerOptional] = None,
snapshot_window: Optional[String] = None,
auth_token: Optional[String] = None,
transit_encryption_enabled: Optional[BooleanOptional] = None,
at_rest_encryption_enabled: Optional[BooleanOptional] = None,
kms_key_id: Optional[String] = None,
user_group_ids: Optional[UserGroupIdListInput] = None,
log_delivery_configurations: Optional[LogDeliveryConfigurationRequestList] = None,
data_tiering_enabled: Optional[BooleanOptional] = None,
network_type: Optional[NetworkType] = None,
ip_discovery: Optional[IpDiscovery] = None,
transit_encryption_mode: Optional[TransitEncryptionMode] = None,
cluster_mode: Optional[ClusterMode] = None,
serverless_cache_snapshot_name: Optional[String] = None,
durability: Optional[Durability] = None,
) -> CreateReplicationGroupResult
Creates a Valkey or Redis OSS (cluster mode disabled) or a Valkey or Redis OSS (cluster mode enabled) replication group.
This API can be used to create a standalone regional replication group or a secondary replication group associated with a Global datastore.
A Valkey or Redis OSS (cluster mode disabled) replication group is a collection of nodes, where one of the nodes is a read/write primary and the others are read-only replicas. Writes to the primary are asynchronously propagated to the replicas.
A Valkey or Redis OSS cluster-mode enabled cluster is comprised of from 1 to 90 shards (API/CLI: node groups). Each shard has a primary node and up to 5 read-only replica nodes. The configuration can range from 90 shards and 0 replicas to 15 shards and 5 replicas, which is the maximum number or replicas allowed.
The node or shard limit can be increased to a maximum of 500 per cluster if the Valkey or Redis OSS engine version is 5.0.6 or higher. For example, you can choose to configure a 500 node cluster that ranges between 83 shards (one primary and 5 replicas per shard) and 500 shards (single primary and no replicas). Make sure there are enough available IP addresses to accommodate the increase. Common pitfalls include the subnets in the subnet group have too small a CIDR range or the subnets are shared and heavily used by other clusters. For more information, see Creating a Subnet Group. For versions below 5.0.6, the limit is 250 per cluster.
To request a limit increase, see Amazon Service Limits and choose the limit type Nodes per cluster per instance type.
When a Valkey or Redis OSS (cluster mode disabled) replication group has been successfully created, you can add one or more read replicas to it, up to a total of 5 read replicas. If you need to increase or decrease the number of node groups (console: shards), you can use scaling. For more information, see Scaling self-designed clusters in the ElastiCache User Guide.
This operation is valid for Valkey and Redis OSS only.
Parameters:
-
replication_group_id(Optional[String], default:None) –The replication group identifier. This parameter is stored as a lowercase string.
Constraints:
-
A name must contain from 1 to 40 alphanumeric characters or hyphens.
-
The first character must be a letter.
-
A name cannot end with a hyphen or contain two consecutive hyphens.
-
-
replication_group_description(Optional[String], default:None) –A user-created description for the replication group.
-
global_replication_group_id(Optional[String], default:None) –The name of the Global datastore
-
primary_cluster_id(Optional[String], default:None) –The identifier of the cluster that serves as the primary for this replication group. This cluster must already exist and have a status of
available.This parameter is not required if
NumCacheClusters,NumNodeGroups, orReplicasPerNodeGroupis specified. -
automatic_failover_enabled(Optional[BooleanOptional], default:None) –Specifies whether a read-only replica is automatically promoted to read/write primary if the existing primary fails.
AutomaticFailoverEnabledmust be enabled for Valkey or Redis OSS (cluster mode enabled) replication groups.Default: false
-
multi_az_enabled(Optional[BooleanOptional], default:None) –A flag indicating if you have Multi-AZ enabled to enhance fault tolerance. For more information, see Minimizing Downtime: Multi-AZ.
-
num_cache_clusters(Optional[IntegerOptional], default:None) –The number of clusters this replication group initially has.
This parameter is not used if there is more than one node group (shard). You should use
ReplicasPerNodeGroupinstead.If
AutomaticFailoverEnabledistrue, the value of this parameter must be at least 2. IfAutomaticFailoverEnabledisfalseyou can omit this parameter (it will default to 1), or you can explicitly set it to a value between 2 and 6.The maximum permitted value for
NumCacheClustersis 6 (1 primary plus 5 replicas). -
preferred_cache_cluster_a_zs(Optional[AvailabilityZonesList], default:None) –A list of EC2 Availability Zones in which the replication group's clusters are created. The order of the Availability Zones in the list is the order in which clusters are allocated. The primary cluster is created in the first AZ in the list.
This parameter is not used if there is more than one node group (shard). You should use
NodeGroupConfigurationinstead.If you are creating your replication group in an Amazon VPC (recommended), you can only locate clusters in Availability Zones associated with the subnets in the selected subnet group.
The number of Availability Zones listed must equal the value of
NumCacheClusters.Default: system chosen Availability Zones.
-
num_node_groups(Optional[IntegerOptional], default:None) –An optional parameter that specifies the number of node groups (shards) for this Valkey or Redis OSS (cluster mode enabled) replication group. For Valkey or Redis OSS (cluster mode disabled) either omit this parameter or set it to 1.
Default: 1
-
replicas_per_node_group(Optional[IntegerOptional], default:None) –An optional parameter that specifies the number of replica nodes in each node group (shard). Valid values are 0 to 5.
-
node_group_configuration(Optional[NodeGroupConfigurationList], default:None) –A list of node group (shard) configuration options. Each node group (shard) configuration has the following members:
PrimaryAvailabilityZone,ReplicaAvailabilityZones,ReplicaCount, andSlots.If you're creating a Valkey or Redis OSS (cluster mode disabled) or a Valkey or Redis OSS (cluster mode enabled) replication group, you can use this parameter to individually configure each node group (shard), or you can omit this parameter. However, it is required when seeding a Valkey or Redis OSS (cluster mode enabled) cluster from a S3 rdb file. You must configure each node group (shard) using this parameter because you must specify the slots for each node group.
-
cache_node_type(Optional[String], default:None) –The compute and memory capacity of the nodes in the node group (shard).
The following node types are supported by ElastiCache. Generally speaking, the current generation types provide more memory and computational power at lower cost when compared to their equivalent previous generation counterparts.
-
General purpose:
-
Current generation:
M7g node types:
cache.m7g.large,cache.m7g.xlarge,cache.m7g.2xlarge,cache.m7g.4xlarge,cache.m7g.8xlarge,cache.m7g.12xlarge,cache.m7g.16xlargeFor region availability, see Supported Node Types
M6g node types (available only for Redis OSS engine version 5.0.6 onward and for Memcached engine version 1.5.16 onward):
cache.m6g.large,cache.m6g.xlarge,cache.m6g.2xlarge,cache.m6g.4xlarge,cache.m6g.8xlarge,cache.m6g.12xlarge,cache.m6g.16xlargeM5 node types:
cache.m5.large,cache.m5.xlarge,cache.m5.2xlarge,cache.m5.4xlarge,cache.m5.12xlarge,cache.m5.24xlargeM4 node types:
cache.m4.large,cache.m4.xlarge,cache.m4.2xlarge,cache.m4.4xlarge,cache.m4.10xlargeT4g node types (available only for Redis OSS engine version 5.0.6 onward and Memcached engine version 1.5.16 onward):
cache.t4g.micro,cache.t4g.small,cache.t4g.mediumT3 node types:
cache.t3.micro,cache.t3.small,cache.t3.mediumT2 node types:
cache.t2.micro,cache.t2.small,cache.t2.medium -
Previous generation: (not recommended. Existing clusters are still supported but creation of new clusters is not supported for these types.)
T1 node types:
cache.t1.microM1 node types:
cache.m1.small,cache.m1.medium,cache.m1.large,cache.m1.xlargeM3 node types:
cache.m3.medium,cache.m3.large,cache.m3.xlarge,cache.m3.2xlarge
-
-
Compute optimized:
-
Previous generation: (not recommended. Existing clusters are still supported but creation of new clusters is not supported for these types.)
C1 node types:
cache.c1.xlarge
-
-
Memory optimized:
-
Current generation:
R7g node types:
cache.r7g.large,cache.r7g.xlarge,cache.r7g.2xlarge,cache.r7g.4xlarge,cache.r7g.8xlarge,cache.r7g.12xlarge,cache.r7g.16xlargeFor region availability, see Supported Node Types
R6g node types (available only for Redis OSS engine version 5.0.6 onward and for Memcached engine version 1.5.16 onward):
cache.r6g.large,cache.r6g.xlarge,cache.r6g.2xlarge,cache.r6g.4xlarge,cache.r6g.8xlarge,cache.r6g.12xlarge,cache.r6g.16xlargeR5 node types:
cache.r5.large,cache.r5.xlarge,cache.r5.2xlarge,cache.r5.4xlarge,cache.r5.12xlarge,cache.r5.24xlargeR4 node types:
cache.r4.large,cache.r4.xlarge,cache.r4.2xlarge,cache.r4.4xlarge,cache.r4.8xlarge,cache.r4.16xlarge -
Previous generation: (not recommended. Existing clusters are still supported but creation of new clusters is not supported for these types.)
M2 node types:
cache.m2.xlarge,cache.m2.2xlarge,cache.m2.4xlargeR3 node types:
cache.r3.large,cache.r3.xlarge,cache.r3.2xlarge,cache.r3.4xlarge,cache.r3.8xlarge
-
Additional node type info
-
All current generation instance types are created in Amazon VPC by default.
-
Valkey or Redis OSS append-only files (AOF) are not supported for T1 or T2 instances.
-
Valkey or Redis OSS Multi-AZ with automatic failover is not supported on T1 instances.
-
The configuration variables
appendonlyandappendfsyncare not supported on Valkey, or on Redis OSS version 2.8.22 and later.
-
-
engine(Optional[String], default:None) –The name of the cache engine to be used for the clusters in this replication group. The value must be set to
valkeyorredis. -
engine_version(Optional[String], default:None) –The version number of the cache engine to be used for the clusters in this replication group. To view the supported cache engine versions, use the
DescribeCacheEngineVersionsoperation.Important: You can upgrade to a newer engine version (see Selecting a Cache Engine and Version) in the ElastiCache User Guide, but you cannot downgrade to an earlier engine version. If you want to use an earlier engine version, you must delete the existing cluster or replication group and create it anew with the earlier engine version.
-
cache_parameter_group_name(Optional[String], default:None) –The name of the parameter group to associate with this replication group. If this argument is omitted, the default cache parameter group for the specified engine is used.
If you are running Valkey or Redis OSS version 3.2.4 or later, only one node group (shard), and want to use a default parameter group, we recommend that you specify the parameter group by name.
-
To create a Valkey or Redis OSS (cluster mode disabled) replication group, use
CacheParameterGroupName=default.redis3.2. -
To create a Valkey or Redis OSS (cluster mode enabled) replication group, use
CacheParameterGroupName=default.redis3.2.cluster.on.
-
-
cache_subnet_group_name(Optional[String], default:None) –The name of the cache subnet group to be used for the replication group.
If you're going to launch your cluster in an Amazon VPC, you need to create a subnet group before you start creating a cluster. For more information, see Subnets and Subnet Groups.
-
cache_security_group_names(Optional[CacheSecurityGroupNameList], default:None) –A list of cache security group names to associate with this replication group.
-
security_group_ids(Optional[SecurityGroupIdsList], default:None) –One or more Amazon VPC security groups associated with this replication group.
Use this parameter only when you are creating a replication group in an Amazon Virtual Private Cloud (Amazon VPC).
-
tags(Optional[TagList], default:None) –A list of tags to be added to this resource. Tags are comma-separated key,value pairs (e.g. Key=
myKey, Value=myKeyValue. You can include multiple tags as shown following: Key=myKey, Value=myKeyValueKey=mySecondKey, Value=mySecondKeyValue. Tags on replication groups will be replicated to all nodes. -
snapshot_arns(Optional[SnapshotArnsList], default:None) –A list of Amazon Resource Names (ARN) that uniquely identify the Valkey or Redis OSS RDB snapshot files stored in Amazon S3. The snapshot files are used to populate the new replication group. The Amazon S3 object name in the ARN cannot contain any commas. The new replication group will have the number of node groups (console: shards) specified by the parameter NumNodeGroups or the number of node groups configured by NodeGroupConfiguration regardless of the number of ARNs specified here.
Example of an Amazon S3 ARN:
arn:aws:s3:::my_bucket/snapshot1.rdb -
snapshot_name(Optional[String], default:None) –The name of a snapshot from which to restore data into the new replication group. The snapshot status changes to
restoringwhile the new replication group is being created. -
preferred_maintenance_window(Optional[String], default:None) –Specifies the weekly time range during which maintenance on the cluster is performed. It is specified as a range in the format ddd:hh24:mi-ddd:hh24:mi (24H Clock UTC). The minimum maintenance window is a 60 minute period.
Valid values for
dddare:-
sun -
mon -
tue -
wed -
thu -
fri -
sat
Example:
sun:23:00-mon:01:30 -
-
port(Optional[IntegerOptional], default:None) –The port number on which each member of the replication group accepts connections.
-
notification_topic_arn(Optional[String], default:None) –The Amazon Resource Name (ARN) of the Amazon Simple Notification Service (SNS) topic to which notifications are sent.
The Amazon SNS topic owner must be the same as the cluster owner.
-
auto_minor_version_upgrade(Optional[BooleanOptional], default:None) –If you are running Valkey 7.2 and above or Redis OSS engine version 6.0 and above, set this parameter to yes to opt-in to the next auto minor version upgrade campaign. This parameter is disabled for previous versions.
-
snapshot_retention_limit(Optional[IntegerOptional], default:None) –The number of days for which ElastiCache retains automatic snapshots before deleting them. For example, if you set
SnapshotRetentionLimitto 5, a snapshot that was taken today is retained for 5 days before being deleted.Default: 0 (i.e., automatic backups are disabled for this cluster).
-
snapshot_window(Optional[String], default:None) –The daily time range (in UTC) during which ElastiCache begins taking a daily snapshot of your node group (shard).
Example:
05:00-09:00If you do not specify this parameter, ElastiCache automatically chooses an appropriate time range.
-
auth_token(Optional[String], default:None) –Reserved parameter. The password used to access a password protected server.
AuthTokencan be specified only on replication groups whereTransitEncryptionEnabledistrue.For HIPAA compliance, you must specify
TransitEncryptionEnabledastrue, anAuthToken, and aCacheSubnetGroup.Password constraints:
-
Must be only printable ASCII characters.
-
Must be at least 16 characters and no more than 128 characters in length.
-
The only permitted printable special characters are !, &, #, $, ^, <, >, and -. Other printable special characters cannot be used in the AUTH token.
For more information, see AUTH password at http://redis.io/commands/AUTH.
-
-
transit_encryption_enabled(Optional[BooleanOptional], default:None) –A flag that enables in-transit encryption when set to
true.This parameter is valid only if the
Engineparameter isredis, theEngineVersionparameter is3.2.6,4.xor later, and the cluster is being created in an Amazon VPC.If you enable in-transit encryption, you must also specify a value for
CacheSubnetGroup.Required: Only available when creating a replication group in an Amazon VPC using Redis OSS version
3.2.6,4.xor later.Default:
falseFor HIPAA compliance, you must specify
TransitEncryptionEnabledastrue, anAuthToken, and aCacheSubnetGroup. -
at_rest_encryption_enabled(Optional[BooleanOptional], default:None) –A flag that enables encryption at-rest on the replication group when set to
true. In some cases, encryption at-rest may be enabled even when this value is false. UseStorageEncryptionTypeto view the effective encryption state of a cluster.You cannot modify the value of
AtRestEncryptionEnabledafter the replication group is created.Default:
truewhen using Valkey,falsewhen using Redis OSS -
kms_key_id(Optional[String], default:None) –The ID of the KMS key used to encrypt the disk in the cluster.
-
user_group_ids(Optional[UserGroupIdListInput], default:None) –The user group to associate with the replication group.
-
log_delivery_configurations(Optional[LogDeliveryConfigurationRequestList], default:None) –Specifies the destination, format and type of the logs.
-
data_tiering_enabled(Optional[BooleanOptional], default:None) –Enables data tiering. Data tiering is only supported for replication groups using the r6gd node type. This parameter must be set to true when using r6gd nodes. For more information, see Data tiering.
-
network_type(Optional[NetworkType], default:None) –Must be either
ipv4|ipv6|dual_stack. IPv6 is supported for workloads using Valkey 7.2 and above, Redis OSS engine version 6.2 to 7.1 and Memcached engine version 1.6.6 and above on all instances built on the Nitro system. -
ip_discovery(Optional[IpDiscovery], default:None) –The network type you choose when creating a replication group, either
ipv4|ipv6. IPv6 is supported for workloads using Valkey 7.2 and above, Redis OSS engine version 6.2 to 7.1 or Memcached engine version 1.6.6 and above on all instances built on the Nitro system. -
transit_encryption_mode(Optional[TransitEncryptionMode], default:None) –A setting that allows you to migrate your clients to use in-transit encryption, with no downtime.
When setting
TransitEncryptionEnabledtotrue, you can set yourTransitEncryptionModetopreferredin the same request, to allow both encrypted and unencrypted connections at the same time. Once you migrate all your Valkey or Redis OSS clients to use encrypted connections you can modify the value torequiredto allow encrypted connections only.Setting
TransitEncryptionModetorequiredis a two-step process that requires you to first set theTransitEncryptionModetopreferred, after that you can setTransitEncryptionModetorequired.This process will not trigger the replacement of the replication group.
-
cluster_mode(Optional[ClusterMode], default:None) –Enabled or Disabled. To modify cluster mode from Disabled to Enabled, you must first set the cluster mode to Compatible. Compatible mode allows your Valkey or Redis OSS clients to connect using both cluster mode enabled and cluster mode disabled. After you migrate all Valkey or Redis OSS clients to use cluster mode enabled, you can then complete cluster mode configuration and set the cluster mode to Enabled.
-
serverless_cache_snapshot_name(Optional[String], default:None) –The name of the snapshot used to create a replication group. Available for Valkey, Redis OSS only.
-
durability(Optional[Durability], default:None) –Specifies the durability setting for the replication group. When set to
default, the service determines the effective durability based on the engine version, cluster mode, and other parameters. The resolved setting is reflected in theEffectiveDurabilityproperty of the replication group. For more information, see Durability.
Raises:
-
CacheClusterNotFoundFault–The requested cluster ID does not refer to an existing cluster.
-
CacheParameterGroupNotFoundFault–The requested cache parameter group name does not refer to an existing cache parameter group.
-
CacheSecurityGroupNotFoundFault–The requested cache security group name does not refer to an existing cache security group.
-
CacheSubnetGroupNotFoundFault–The requested cache subnet group name does not refer to an existing cache subnet group.
-
ClusterQuotaForCustomerExceededFault–The request cannot be processed because it would exceed the allowed number of clusters per customer.
-
GlobalReplicationGroupNotFoundFault–The Global datastore does not exist
-
InsufficientCacheClusterCapacityFault–The requested cache node type is not available in the specified Availability Zone. For more information, see InsufficientCacheClusterCapacity in the ElastiCache User Guide.
-
InvalidCacheClusterStateFault–The requested cluster is not in the
availablestate. -
InvalidGlobalReplicationGroupStateFault–The Global datastore is not available or in primary-only state.
-
InvalidParameterCombinationException–Two or more incompatible parameters were specified.
-
InvalidParameterValueException–The value for a parameter is invalid.
-
InvalidUserGroupStateFault–The user group is not in an active state.
-
InvalidVPCNetworkStateFault–The VPC network is in an invalid state.
-
NodeGroupsPerReplicationGroupQuotaExceededFault–The request cannot be processed because it would exceed the maximum allowed number of node groups (shards) in a single replication group. The default maximum is 90
-
NodeQuotaForClusterExceededFault–The request cannot be processed because it would exceed the allowed number of cache nodes in a single cluster.
-
NodeQuotaForCustomerExceededFault–The request cannot be processed because it would exceed the allowed number of cache nodes per customer.
-
ReplicationGroupAlreadyExistsFault–The specified replication group already exists.
-
TagQuotaPerResourceExceeded–The request cannot be processed because it would cause the resource to have more than the allowed number of tags. The maximum number of tags permitted on a resource is 50.
-
UserGroupNotFoundFault–The user group was not found or does not exist
-
UnknownServiceError–The service returned an error code this client does not model.
Examples:
CreateCacheReplicationGroup Creates a Redis replication group with 3 nodes.
>>> client.create_replication_group(replication_group_id='my-redis-rg', replication_group_description='A Redis replication group.', automatic_failover_enabled=True, num_cache_clusters=3, cache_node_type='cache.m3.medium', engine='redis', engine_version='2.8.24', snapshot_retention_limit=30)
CreateReplicationGroup
Creates a Redis (cluster mode enabled) replication group with two shards. One shard has one read replica node and the other shard has two read replicas.
>>> client.create_replication_group(replication_group_id='clustered-redis-rg', replication_group_description='A multi-sharded replication group', num_node_groups=2, node_group_configuration=[{'Slots': '0-8999', 'PrimaryAvailabilityZone': 'us-east-1c', 'ReplicaCount': 1, 'ReplicaAvailabilityZones': ['us-east-1b']}, {'Slots': '9000-16383', 'PrimaryAvailabilityZone': 'us-east-1a', 'ReplicaCount': 2, 'ReplicaAvailabilityZones': ['us-east-1a', 'us-east-1c']}], cache_node_type='cache.m3.medium', engine='redis', engine_version='3.2.4', cache_parameter_group_name='default.redis3.2.cluster.on', auto_minor_version_upgrade=True, snapshot_retention_limit=8)
Source code in docs_src/capo_elasticache/_services/elasti_cache.py
1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 | |